astro
astro copied to clipboard
fix(deps): update dependency husky to v9
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| husky | ^8.0.3 -> ^9.0.0 |
Release Notes
typicode/husky (husky)
v9.1.7
What's Changed
New Contributors
Full Changelog: https://github.com/typicode/husky/compare/v9.1.6...v9.1.7
v9.1.6
What's Changed
New Contributors
- @OlegKipchatov made their first contribution in #1495
- @Byron2016 made their first contribution in #1499
- @dexmlee made their first contribution in #1519
Full Changelog: https://github.com/typicode/husky/compare/v9.1.5...v9.1.6
v9.1.5
What's Changed
- fixes #1494, support
pre-merge-commithook by @RainMeoCat in #1497
New Contributors
- @RainMeoCat made their first contribution in #1497
Full Changelog: https://github.com/typicode/husky/compare/v9.1.4...v9.1.5
v9.1.4
- Improve deprecation notice
v9.1.3
- fix: better handle space in
PATH
v9.1.2
Show a message instead of automatically removing deprecated code.
This only concerns projects that still have the following code in their hooks:
- #!/usr/bin/env sh # <- This is deprecated, remove it
- . "$(dirname -- "$0")/_/husky.sh" # <- This is deprecated, remove it
### Rest of your hook code
Hooks with these lines will fail in v10.0.0
v9.1.1
Super saiyan ~~god~~ dog! It's over 9.0.0!
What's new
You can now run package commands directly, no need for npx or equivalents.
It makes writing hooks more intuitive and is also slightly faster 🐺⚡️
### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster
A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.
### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again
For more advanced use cases, see lint-staged.
Fixes
bunx husky initcommand- Workaround for some hooks implementation on Windows
Deprecations
#!/usr/bin/env shand. "$(dirname -- "$0")/_/husky.sh"are deprecated.huskycommand will automatically remove them, no action required.- If you're having code in
~/.huskyrcplease move it to.config/husky/init.sh
Support for these will be removed in v10.
Friendly reminder
If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.
I've seen some confusion about this on X, so just a heads-up!
Sponsoring
Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.
Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉
v9.1.0
v9.0.11
- chore: update
package-lock.jsonby @btea in #1383 - fix:
export HUSKY=0in init (fixes #1393) by @typicode in #1395
v9.0.10
v9.0.9
- refactor: rename files by @typicode in #1378
v9.0.8
- docs: update index.md by @khaledYS in #1369
- Fix tab detection on install command by @glensc in #1376
- refactor: reduce file size by @typicode in #1377
v9.0.7
- fix: typo and source
~/.huskyrccorrectly (compatibility with v8) - docs: fix example by @typicode in #1363
v9.0.6
- docs: add favicon by @rakleed in #1354
- chore: apply editorconfig to code only by @typicode in #1355
- docs: update install script to mjs and fix CI checks by @starnayuta in #1357
- Fix unbound variable by @typicode in #1359
v9.0.5
- docs: update path to startup files by @ManuelRauber in #1350
- fix: init error by @typicode in #1353
v9.0.4
- fix: init create dir before by @typicode in #1348
- refactor: simplify by @typicode in #1349
- fix: init not working on pnpm #1334 by @rozbo in #1347
v9.0.3
- docs: fix link by @typicode in #1340
- chore: fix links in issue template by @julien-f in #1341
- fix: add scripts field if not present by @chalkygames123 in #1338
- docs: changelog link by @typicode in #1343
- fix: insert final newline by @chalkygames123 in #1339
- fix: fix git hooks path on windows by @rozbo in #1346
v9.0.2
- fix: exit code by @gergelypap in #1336
- docs: typo by @chalkygames123 in #1337
v9.0.1
Kicking off the year with an exciting update!
Note: install using husky@latest to get the bug fixes that were released after.
Introducing husky init
v8
npm pkg set scripts.prepare="husky install"
npm run prepare
npx husky add .husky/pre-commit "npm test"
v9
Adding husky to a project is now easier than ever. It's just a single line that does the same as above. No need to read the docs to get started anymore.
npx husky init
Adding a New Hook
v8
npx husky add .husky/pre-commit "npm test"
git add --chmod=+x .husky/pre-commit # On Windows
v9
Adding a hook is as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command. For example, on Linux/macOS:
echo "npm test" > .husky/pre-commit
Further Size Reduction
v8 was already the most compact Git hooks manager at approximately 6kB.
v9 takes this a step further, reducing the size to just 3kB, likely making it the smallest devDependency in your toolkit.
To give you an idea of how small it is, the biggest file in the project is the MIT license 😄
More to Come
Additional features are in the pipeline for v9. Stay tuned :raised_hands:
Other Changes
- Enhanced security with CI and npm
--provenancefor safer publishing. - Added
$XDG_CONFIG_HOMEsupport. Move~/.huskyrcto~/.config/husky/init.shfor centralized configuration. - Fixed permission issue for Windows-created hooks; they no longer need to be executable.
- Removed
husky install. Usehuskyorhusky some/dirfor the same functionality (deprecation notice to be added). - Modified behavior when
.gitis missing; it now triggers a warning instead of failure. - Replaced
HUSKY_DEBUG=1withHUSKY=2for debugging. - Updated the Husky API for module usage.
- Transitioned to
ESMfor module usage. - Dropped support for Node 14 and 16.
- Revamped docs.
How to Migrate
v9 is backward compatible with v8, allowing you to freely upgrade and migrate your hooks later.
Here are the steps to migrate:
package.json
{
"scripts": {
- "prepare": "husky install"
+ "prepare": "husky"
}
}
.husky/pre-commit
- #!/usr/bin/env sh
- . "$(dirname -- "$0")/_/husky.sh"
npm test
Note: sh will be used to run hooks, even if a shebang is set.
If you were using husky as a module:
- const husky = require('husky')
- // ...
+ import husky from 'husky'
+ console.log(husky())
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.
Apply Sweep Rules to your PR?
- [ ] Apply: All new business logic should have corresponding unit tests.
- [ ] Apply: Refactor large functions to be more modular.
- [ ] Apply: Add docstrings to all functions and file headers.
Walkthrough
The change involves updating the version of the husky package in the package.json file from ^8.0.3 to ^9.0.0. This upgrade signifies a transition to a newer major version, which may introduce new features, improvements, or breaking changes. No other dependencies or configurations within the package.json file have been altered.
Changes
| File | Change Summary |
|---|---|
| package.json | Updated husky version from ^8.0.3 to ^9.0.0 |
Sequence Diagram(s)
sequenceDiagram
participant User
participant Husky
User->>Husky: Install husky@^9.0.0
Husky-->>User: Installation complete
Poem
🐰 In the garden where I hop and play,
A new husky version brightens my day!
With features anew, oh what a delight,
I'll dance through the code, all day and night!
So let’s celebrate, with a joyful cheer,
For updates like this bring us all near! 🌼
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?
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
@coderabbitaiin 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
@coderabbitaiin 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 using PR comments)
@coderabbitai pauseto pause the reviews on a PR.@coderabbitai resumeto resume the paused reviews.@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository.@coderabbitai full reviewto do a full review from scratch and review all the files again.@coderabbitai summaryto regenerate the summary of the PR.@coderabbitai resolveresolve all the CodeRabbit review comments.@coderabbitai configurationto show the current CodeRabbit configuration for the repository.@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
CodeRabbit Configuration File (.coderabbit.yaml)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yamlfile 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.