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

Update test dependencies (major) #140

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 19, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
husky ^4.3.8 -> ^9.0.0 age adoption passing confidence
mocha (source) ^7.0.1 -> ^11.0.0 age adoption passing confidence
nock ^11.7.2 -> ^13.0.0 age adoption passing confidence
npm-run-all2 ^6.0.5 -> ^7.0.0 age adoption passing confidence
nyc (source) ^15.0.0 -> ^17.0.0 age adoption passing confidence
sinon (source) ^8.1.1 -> ^19.0.0 age adoption passing confidence

Release Notes

typicode/husky (husky)

v9.1.7

Compare Source

v9.1.6

Compare Source

v9.1.5

Compare Source

v9.1.4

Compare Source

v9.1.3

Compare Source

  • fix: better handle space in PATH

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

Super saiyan god dog! It's over 9.0.0!

There's a bug with this release which prevents the deprecation notice to appear and requires to remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" (which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.

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 init command
  • Workaround for some hooks implementation on Windows 🤷

Deprecations

  • Remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" from your hooks
  • Move your code from ~/.huskyrc to .config/husky/init.sh

Support for these will be removed in v10, notices have been added.

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.0.11

Compare Source

v9.0.10

Compare Source

v9.0.9

Compare Source

v9.0.8

Compare Source

v9.0.7

Compare Source

v9.0.6

Compare Source

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.0.1...v9.0.2

v9.0.1

Compare Source

Kicking off the year with an exciting update!

TLDR;

Improved user experience and a (even) smaller package size while packing in more features!

👋 By the Way

I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂

Introducing husky init

Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.

v8
npm pkg set scripts.prepare="husky install"
npm run prepare
npx husky add .husky/pre-commit "npm test"
v9
npx husky init

Adding a New Hook

Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command.

v8
npx husky add  .husky/pre-commit "npm test"
git add --chmod=+x .husky/pre-commit # On Windows
v9
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 🙌

Other Changes

  • Enhanced security with CI and npm --provenance for safer publishing.
  • Added $XDG_CONFIG_HOME support. Move ~/.huskyrc to ~/.config/husky/init.sh for centralized configuration.
  • Fixed permission issue for Windows-created hooks; they no longer need to be executable.
  • Removed husky install. Use husky or husky some/dir for the same functionality (deprecation notice to be added).
  • Modified behavior when .git is missing; it now triggers a warning instead of failure.
  • Replaced HUSKY_DEBUG=1 with HUSKY=2 for debugging.
  • Updated the Husky API for module usage.
  • Transitioned to ESM for 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.

package.json

{
  "scripts": {
-   "prepare": "husky install"
+   "prepare": "husky"
  }
}

.husky/pre-commit

- #!/usr/bin/env sh
- . "$(dirname -- "$0")/_/husky.sh"
npm test

v8.0.3

Compare Source

  • fix: add git not installed message #​1208

v8.0.2

Compare Source

  • docs: remove deprecated npm set-script

v8.0.1

Compare Source

  • fix: use POSIX equality operator

v8.0.0

Compare Source

What's Changed

Feats
Fixes
Docs
Chore

v7.0.4

Compare Source

No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.

v7.0.3

Compare Source

v7.0.2

Compare Source

Fix pre-commit hook in WebStorm (#​1023)

v7.0.1

Compare Source

  • Fix gracefully fail if Git command is not found #​1003 (same as in v6)

v7.0.0

Compare Source

  • Improve .husky/ directory structure. .husky/.gitignore is now unnecessary and can be removed.
  • Improve error output (shorter)
  • Update husky-init CLI
  • Update husky-4-to-7 CLI
  • Drop Node 10 support

Please help me develop and release OSS projects ❤️ on GitHub Sponsors or Open Collective. Thank you for your support!

v6.0.0

Compare Source

After being in early access for Open Source projects and Sponsors for a limited time, I'm happy to announce that husky 6 is MIT again and can be freely used in commercial projects! 🎉

Many thanks to the Open Source projects and Companies which have switched to/sponsored the new husky during this period!

OSS is my full-time job, please consider sponsoring the development of husky on GitHub sponsors or Open Collective. Thank you!

Breaking change

  • husky init has been moved to its own package (npx husky-init)

Added

  • Programmatically use husky: require('husky')
  • TypeScript definitions

Migrating from husky 4

Husky 6 contains breaking changes. If you're coming from v4, npm install husky@6 won't be enough.

Recommended: see husky-4-to-6 CLI to automatically migrate your config. There's also a dedicated section in the docs.

If you're curious why config has changed, you may be interested in reading:
https://blog.typicode.com/husky-git-hooks-javascript-config/

Also Husky 6 follows official npm and Yarn best practices regarding autoinstall. It's recommended to use prepare script instead (see usage in docs).

v5.2.0

Compare Source

  • Add set command to replace hooks (husky set .husky/pre-commit cmd)
  • Update add command to append command (husky add .husky/pre-commit cmd)
  • Improve error messages

v5.1.3

Compare Source

  • docs: add specific Yarn v2 install/uninstall instructions
  • cli: husky init will detect Yarn v2 and initialize accordingly

v5.1.2

Compare Source

  • docs: recommend prepare script instead of postinstall (#​890)
  • cli: husky init use prepare script (#​890)

v5.1.1

Compare Source

  • style(shell): add trailing newlines (#​870)
  • fix(init): update package.json postinstall

v5.1.0

Compare Source

  • Add husky init

v5.0.9

Compare Source

  • fix(install): do not fail if not inside a Git directory (closes #​851)

See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes

v5.0.8

Compare Source

v5.0.7

Compare Source

  • fix(shell): double quote params (#​824)

v5.0.6

Compare Source

  • Remove unused files

v5.0.5

Compare Source

  • Fix custom directory support #​827

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

👉 See https://typicode.github.io/husky for breaking changes and new installation instructions.

Note about the license

Husky 5 is released under The Parity Public License.

It doesn't affect you if you're using husky in an Open Source project or if you're a sponsor. You're free to use it as usual and I hope you'll enjoy this new release ❤️

If you're using husky in a commercial project, you may want to consider becoming a sponsor to support the project. You can also try it for 30 days.

This is only for a limited time, husky will be MIT again later.

Migrating

Important Husky v5 brings a lot of improvements but is also very different from v4. Git hooks won't work if you only upgrade husky dependency, existing config needs to be migrated too.

The best way to switch to v5 is to follow the new installation instructions and migrate existing hooks command using husky add.

mochajs/mocha (mocha)

v11.0.1

Compare Source

🌟 Features
📚 Documentation

v11.0.0

Compare Source

⚠ BREAKING CHANGES
  • adapt new engine range for Mocha 11 (#​5216)
🌟 Features
🩹 Fixes
📚 Documentation

v10.8.2

Compare Source

🩹 Fixes
📚 Documentation
  • indicate 'exports' interface does not work in browsers (#​5181) (14e640e)
🧹 Chores
  • fix docs builds by re-adding eleventy and ignoring gitignore again (#​5240) (881e3b0)
🤖 Automation

v10.8.1

Compare Source

🩹 Fixes

v10.8.0

Compare Source

🌟 Features
🩹 Fixes
📚 Documentation
🧹 Chores

v10.7.3

Compare Source

🩹 Fixes

v10.7.0

Compare Source

🎉 Enhancements

v10.6.1

Compare Source

🐛 Fixes

v10.6.0

Compare Source

🎉 Enhancements

v10.5.2

Compare Source

🐛 Fixes

v10.5.1

Compare Source

🐛 Fixes

v10.5.0

Compare Source

🎉 Enhancements
🐛 Fixes
🔩 Other

v10.4.0

Compare Source

🎉 Enhancements
🐛 Fixes
🔩 Other

v10.3.0

Compare Source

This is a stable release equivalent to 10.30.0-prerelease.

v10.2.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

v10.1.0

Compare Source

🎉 Enhancements

🔩 Other

v10.0.0

Compare Source

💥 Breaking Changes

🔩 Other

Also thanks to @​ea2305 and @​SukkaW for improvements to our documentation.

v9.2.2

Compare Source

🐛 Fixes

🔩 Other

v9.2.1

Compare Source

🐛 Fixes

v9.2.0

Compare Source

🎉 Enhancements

🔩 Other

v9.1.4

Compare Source

🐛 Fixes

🔩 Other

v9.1.3

Compare Source

🐛 Fixes

🔩 Other

v9.1.2

Compare Source

🐛 Fixes

🔩 Other

v9.1.1

Compare Source

🐛 Fixes

v9.1.0

Compare Source

🎉 Enhancements

v9.0.3

Compare Source

🐛 Fixes

v9.0.2

Compare Source

🐛 Fixes

🔩 Other

v9.0.1

Compare Source

🔩 Other

We added a separate browser bundle mocha-es2018.js in javascript ES2018, as we skipped the transpilation down to ES5. This is an experimental step towards freezing Mocha's support of IE11.

v9.0.0

Compare Source

💥 Breaking Changes

Mocha is going ESM-first! This means that it will now use ESM import(test_file) to load the test files, instead of the CommonJS require(test_file). This is not a problem, as import can also load most files that require does. In the rare cases where this fails, it will fallback to require(...). This ESM-first approach is the next step in Mocha's ESM migration, and allows ESM loaders to load and transform the test file.

🎉 Enhancements

🐛 Fixes

🔩 Other

v8.4.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

Also thanks to @​outsideris


Configuration

📅 Schedule: Branch creation - "* 5 */14 * *" in timezone Europe/Stockholm, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate renovate bot force-pushed the renovate/major-tests branch from ebddc53 to 520efc8 Compare August 5, 2022 10:43
@renovate renovate bot force-pushed the renovate/major-tests branch from 520efc8 to eb4c995 Compare March 27, 2023 22:48
@renovate renovate bot force-pushed the renovate/major-tests branch from eb4c995 to 6b7e139 Compare May 12, 2023 01:35
@renovate renovate bot force-pushed the renovate/major-tests branch from 6b7e139 to d8998d0 Compare September 18, 2023 22:19
@renovate renovate bot force-pushed the renovate/major-tests branch from d8998d0 to bfb88f6 Compare October 24, 2023 00:56
@renovate renovate bot force-pushed the renovate/major-tests branch from bfb88f6 to f1b8924 Compare January 2, 2024 01:32
Copy link
Contributor Author

renovate bot commented Jan 2, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/chai
npm ERR!   dev chai@"^5.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer chai@">= 2.1.2 < 5" from [email protected]
npm ERR! node_modules/chai-as-promised
npm ERR!   dev chai-as-promised@"^7.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/chai
npm ERR!   peer chai@">= 2.1.2 < 5" from [email protected]
npm ERR!   node_modules/chai-as-promised
npm ERR!     dev chai-as-promised@"^7.1.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-01-30T01_34_54_563Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-01-30T01_34_54_563Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-tests branch from f1b8924 to df1e846 Compare January 30, 2024 01:35
@renovate renovate bot force-pushed the renovate/major-tests branch from df1e846 to f89a83b Compare May 21, 2024 11:54
@renovate renovate bot force-pushed the renovate/major-tests branch from f89a83b to 702a496 Compare June 10, 2024 22:30
@renovate renovate bot force-pushed the renovate/major-tests branch from 702a496 to 83d5aa1 Compare September 15, 2024 03:32
@renovate renovate bot force-pushed the renovate/major-tests branch from 83d5aa1 to f58c6b2 Compare October 29, 2024 04:18
@renovate renovate bot force-pushed the renovate/major-tests branch from f58c6b2 to 2db4925 Compare January 1, 2025 04:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants