Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency husky to ^9.1.5 #771

Merged
merged 1 commit into from
Aug 22, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 20, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
husky ^9.1.4 -> ^9.1.5 age adoption passing confidence

Release Notes

typicode/husky (husky)

v9.1.5

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

  • Chores
    • Updated the husky package to version ^9.1.5, which includes minor improvements and bug fixes. No other dependencies or functionalities were affected.

Copy link

coderabbitai bot commented Aug 20, 2024

Walkthrough

The recent update involved a minor version change for the husky package in the package.json file, moving from version 9.1.4 to 9.1.5. This patch is expected to provide improvements or bug fixes while maintaining backward compatibility. No other dependencies were modified, and the overall structure and functionality of the project remain unchanged.

Changes

File Change Summary
package.json Updated husky from ^9.1.4 to ^9.1.5

Poem

🐇 In the garden, changes bloom,
A little patch, dispelling gloom.
Husky hops to version new,
Fixes here, and tweaks for you.
With joy we leap, our code in cheer,
A minor change, yet bright and clear! 🌼✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 007c50f and 71d75c3.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 71d75c3 and f91ee6b.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (1)
  • package.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • package.json

@antoinezanardi antoinezanardi merged commit 48068da into develop Aug 22, 2024
14 checks passed
@antoinezanardi antoinezanardi deleted the renovate/husky-9.x branch August 22, 2024 10:15
antoinezanardi pushed a commit that referenced this pull request Sep 3, 2024
## [1.30.0](v1.29.0...v1.30.0) (2024-09-03)

### 🚀 Features

* **cucumber:** skip screenshots in shards commands ([#804](#804)) ([92bcd9d](92bcd9d))
* **seo:** enhanced seo using appropriate module ([#801](#801)) ([0b01787](0b01787))

### 🐛 Bug Fixes

* **deps:** update dependency @primevue/themes to ^4.0.5 ([#780](#780)) ([77747cb](77747cb))
* **deps:** update dependency primevue to ^4.0.5 ([#781](#781)) ([6ecb367](6ecb367))

### 🧹 Chore

* **deps:** update antoinezanardi/werewolves-assistant-api docker tag to v1.35.2 ([#769](#769)) ([007c50f](007c50f))
* **deps:** update commitlint monorepo to ^19.4.1 ([#790](#790)) ([656b3eb](656b3eb))
* **deps:** update dependency @nuxt/image to ^1.8.0 ([#789](#789)) ([b822784](b822784))
* **deps:** update dependency @nuxtjs/sitemap to ^6.0.1 ([#803](#803)) ([6c77caa](6c77caa))
* **deps:** update dependency @pinia/nuxt to ^0.5.4 ([#773](#773)) ([c4e23c8](c4e23c8))
* **deps:** update dependency @primevue/nuxt-module to ^4.0.5 ([#779](#779)) ([e9e7c8f](e9e7c8f))
* **deps:** update dependency @stylistic/eslint-plugin to ^2.7.2 ([#793](#793)) ([3420cef](3420cef))
* **deps:** update dependency @types/eslint to ^9.6.1 ([#786](#786)) ([4e2e86e](4e2e86e))
* **deps:** update dependency @vueuse/core to ^11.0.3 ([#784](#784)) ([25e385f](25e385f))
* **deps:** update dependency @vueuse/nuxt to ^11.0.3 ([#785](#785)) ([b105a08](b105a08))
* **deps:** update dependency chart.js to ^4.4.4 ([#772](#772)) ([6334b4a](6334b4a))
* **deps:** update dependency eslint to ^9.9.1 ([#782](#782)) ([66947f1](66947f1))
* **deps:** update dependency eslint-import-resolver-typescript to ^3.6.3 ([#787](#787)) ([d68409b](d68409b))
* **deps:** update dependency eslint-plugin-import to ^2.30.0 ([#800](#800)) ([72fa0e2](72fa0e2))
* **deps:** update dependency eslint-plugin-vue to ^9.28.0 ([#799](#799)) ([fd0a014](fd0a014))
* **deps:** update dependency husky to ^9.1.5 ([#771](#771)) ([48068da](48068da))
* **deps:** update dependency lint-staged to ^15.2.10 ([#795](#795)) ([b1f021b](b1f021b))
* **deps:** update dependency msw to ^2.4.1 ([#791](#791)) ([8841a10](8841a10))
* **deps:** update dependency prettier-plugin-gherkin to ^3.1.0 ([#798](#798)) ([a022bfc](a022bfc))
* **deps:** update dependency tsx to ^4.19.0 ([#783](#783)) ([eed00f7](eed00f7))
* **deps:** update dependency type-fest to ^4.26.0 ([#792](#792)) ([b27780b](b27780b))
* **deps:** update dependency vue to ^3.5.0 ([#802](#802)) ([3f5a52f](3f5a52f))
* **deps:** update dependency vue-tsc to ^2.1.4 ([#794](#794)) ([d06bf42](d06bf42))
* **deps:** update dependency vue3-lottie to ^3.3.1 ([#796](#796)) ([77220f2](77220f2))
* **deps:** update node docker tag to v22.7.0 ([#778](#778)) ([58c11ca](58c11ca))
* **deps:** update node.js to >=20.17.0 ([#774](#774)) ([4cb7cac](4cb7cac))
* **deps:** update nuxtjs monorepo to ^3.13.0 ([#777](#777)) ([4349e7c](4349e7c))
* **deps:** update pnpm to v9.9.0 ([#776](#776)) ([67f0c62](67f0c62))
* **deps:** update typescript-eslint monorepo to ^8.3.0 ([#788](#788)) ([17538e5](17538e5))
* **deps:** update typescript-eslint monorepo to ^8.4.0 ([#797](#797)) ([ad62dd5](ad62dd5))
@antoinezanardi
Copy link
Owner

🎉 This PR is included in version 1.30.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant