-
Notifications
You must be signed in to change notification settings - Fork 1
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 external major (major) #28
base: main
Are you sure you want to change the base?
Conversation
This PR will trigger no release when merged. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #28 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 9 9
Lines 1330 1330
=========================================
Hits 1330 1330 ☔ View full report in Codecov by Sentry. |
f3589d2
to
c87c846
Compare
05c3cab
to
7c21d55
Compare
e9ae41a
to
7556ee6
Compare
4b9ffd3
to
6aa0784
Compare
f8ebe30
to
584d210
Compare
f381002
to
5adc177
Compare
f411e48
to
b9d57c7
Compare
|
170d25c
to
7a23604
Compare
b7b560a
to
fa0860e
Compare
3d28fdb
to
cb7736b
Compare
cb7736b
to
173f0b0
Compare
52a6729
to
ffe88dd
Compare
d8ea2fe
to
a195fbc
Compare
9f0b9a8
to
76daa03
Compare
76daa03
to
72966c5
Compare
This PR contains the following updates:
9.0.2
->12.0.1
v3
->v4
v3
->v4
^3.0.0
->^4.0.0
7.14.0
->10.1.2
3.3.0
->4.1.0
8.57.0
->9.9.0
v2
->v3
8.0.3
->9.1.4
13.3.0
->15.2.9
^2.6.11
->^3.0.0
^19.0.2
->^24.0.0
7.0.8
->8.0.2
^15.2.0
->^18.0.0
Release Notes
semantic-release/npm (@semantic-release/npm)
v12.0.1
Compare Source
Bug Fixes
v12.0.0
Compare Source
Features
exports
to point at ./index.js (9e193c2)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
v11.0.3
Compare Source
Bug Fixes
even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully
v11.0.2
Compare Source
Bug Fixes
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v10.0.6
Compare Source
Bug Fixes
v10.0.5
Compare Source
Bug Fixes
v10.0.4
Compare Source
Bug Fixes
v10.0.3
Compare Source
Bug Fixes
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Bug Fixes
Code Refactoring
Features
BREAKING CHANGES
can be found at https://github.com/npm/cli/releases/tag/v9.0.0
raised to v20.1.0 in order to support loading of ESM plugins
errors
propertyNPM_USERNAME
andNPM_PASSWORD
is no longer supported. UseNPM_TOKEN
instead.@semantic-release/npm
is now a native ES Module. Ithas named exports for each plugin hook (
verifyConditions
,prepare
,publish
,addChannel
)actions/checkout (actions/checkout)
v4
Compare Source
actions/setup-node (actions/setup-node)
v4
Compare Source
m-radzikowski/aws-sdk-client-mock (aws-sdk-client-mock)
v4.0.1
Compare Source
v4.0.0
Compare Source
bcoe/c8 (c8)
v10.1.2
Compare Source
Bug Fixes
v10.1.1
Compare Source
Bug Fixes
v10.1.0
Compare Source
Features
v10.0.0
Compare Source
⚠ BREAKING CHANGES
Bug Fixes
v9.1.0
Compare Source
Features
Bug Fixes
v9.0.0
Compare Source
⚠ BREAKING CHANGES
Features
v8.0.1
Compare Source
Bug Fixes
v8.0.0
Compare Source
⚠ BREAKING CHANGES
Miscellaneous Chores
eslint/eslint (eslint)
v9.9.0
Compare Source
Features
41d0206
feat: Add support for TS config files (#18134) (Arya Emami)3a4eaf9
feat: add suggestion torequire-await
to removeasync
keyword (#18716) (Dave)Documentation
9fe068c
docs: how to author plugins with configs that extend other configs (#18753) (Alec Gibson)48117b2
docs: add version support page in the side navbar (#18738) (Amaresh S M)fec2951
docs: add version support page to the dropdown (#18730) (Amaresh S M)38a0661
docs: Fix typo (#18735) (Zaina Al Habash)3c32a9e
docs: Update yarn command for creating ESLint config (#18739) (Temitope Ogunleye)f9ac978
docs: Update README (GitHub Actions Bot)Chores
461b2c3
chore: upgrade to@eslint/js@9.9.0
(#18765) (Francesco Trotta)59dba1b
chore: package.json update for @eslint/js release (Jenkins)fea8563
chore: update dependency @eslint/core to ^0.3.0 (#18724) (renovate[bot])aac191e
chore: update dependency @eslint/json to ^0.3.0 (#18760) (renovate[bot])b97fa05
chore: update wdio dependencies for more stable tests (#18759) (Christian Bromann)v9.8.0
Compare Source
v9.7.0
Compare Source
Features
7bd9839
feat: add support for es2025 duplicate named capturing groups (#18630) (Yosuke Ota)1381394
feat: addregex
option inno-restricted-imports
(#18622) (Nitin Kumar)Bug Fixes
14e9f81
fix: destructuring in catch clause inno-unused-vars
(#18636) (Francesco Trotta)Documentation
9f416db
docs: Add Powered by Algolia label to the search. (#18633) (Amaresh S M)c8d26cb
docs: Open JS Foundation -> OpenJS Foundation (#18649) (Milos Djermanovic)6e79ac7
docs:loadESLint
does not support optioncwd
(#18641) (Francesco Trotta)Chores
793b718
chore: upgrade @eslint/js@9.7.0 (#18680) (Francesco Trotta)7ed6f9a
chore: package.json update for @eslint/js release (Jenkins)7bcda76
refactor: Add type references (#18652) (Nicholas C. Zakas)51bf57c
chore: add tech sponsors through actions (#18624) (Strek)6320732
refactor: don't useparent
property inNodeEventGenerator
(#18653) (Milos Djermanovic)9e6d640
refactor: move "Parsing error" prefix adding to Linter (#18650) (Milos Djermanovic)v9.6.0
Compare Source
v9.5.0
Compare Source
v9.4.0
Compare Source
v9.3.0
Compare Source
v9.2.0
Compare Source
v9.1.1
Compare Source
v9.1.0
Compare Source
v9.0.0
Compare Source
github/codeql-action (github/codeql-action)
v3
Compare Source
typicode/husky (husky)
v9.1.4
Compare Source
v9.1.3
Compare Source
PATH
v9.1.2
Compare Source
v9.1.1
Compare Source
v9.1.0
Compare Source
Super saiyan
goddog! 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 🐺⚡️
A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.
For more advanced use cases, see lint-staged.
Fixes
bunx husky init
commandDeprecations
#!/usr/bin/env sh
and. "$(dirname -- "$0")/_/husky.sh"
from your hooks~/.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
~/.huskyrc
correctly (compatibility with v8)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
v9
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
v9
Further Size Reduction
v8
was already the most compact Git hooks manager at approximately6kB
.v9
takes this a step further, reducing the size to just3kB
, 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
--provenance
for safer publishing.$XDG_CONFIG_HOME
support. Move~/.huskyrc
to~/.config/husky/init.sh
for centralized configuration.husky install
. Usehusky
orhusky some/dir
for the same functionality (deprecation notice to be added)..git
is missing; it now triggers a warning instead of failure.HUSKY_DEBUG=1
withHUSKY=2
for debugging.ESM
for module usage.How to Migrate
v9
is backward compatible withv8
, allowing you to freely upgrade and migrate your hooks later.package.json
.husky/pre-commit
lint-staged/lint-staged (lint-staged)
v15.2.9
Compare Source
Patch Changes
b69ce2d
Thanks @iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warningMaxListenersExceededWarning: Possible EventEmitter memory leak detected
.v15.2.8
Compare Source
Patch Changes
f0480f0
Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevel
command was taken into use for resolving the current git repo root. This version switched the--show-toplevel
flag with--show-cdup
, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_process
. The new flag returns a path relative to the working directory, avoiding the issue.The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.
v15.2.7
Compare Source
Patch Changes
a51be80
Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevel
command was taken into use for resolving the current git repo root. This version drops the--path-format=absolute
option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgradinggit
to the latest version.v15.2.6
Compare Source
Patch Changes
119adb2
Thanks @iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.v15.2.5
Compare Source
Patch Changes
#1424
31a1f95
Thanks @iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.#1423
91abea0
Thanks @iiroj! - Improve error logging when failing to read or parse a configuration file#1424
ee43f15
Thanks @iiroj! - Upgrade micromatch@4.0.7v15.2.4
Compare Source
Patch Changes
4f4537a
Thanks @iiroj! - Fix release issue with previous version; update dependenciesv15.2.2
Compare Source
Patch Changes
fdcdad4
Thanks @iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.v15.2.1
Compare Source
Patch Changes
e4023f6
Thanks @iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means thestdin
of the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdin
is ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.v15.2.0
Compare Source
Minor Changes
f3378be
Thanks @iiroj! - Using the--no-stash
flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag--no-hide-partially-staged
that is automatically enabled when--no-stash
is used.Patch Changes
#1362
17bc480
Thanks @antonk52! - update lilconfig@3.0.0#1368
7c55ca9
Thanks @iiroj! - Update most dependencies#1368
777d4e9
Thanks @iiroj! - To improve performance, only uselilconfig
when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.#1373
85eb0dd
Thanks @iiroj! - When determining git directory, usefs.realpath()
only for symlinks. It looks likefs.realpath()
changes some Windows mapped network filepaths unexpectedly, causing issues.v15.1.0
Compare Source
Minor Changes
0423311
Thanks @danielbayley! - Add support for loading configuration frompackage.yaml
andpackage.yml
files, supported bypnpm
.Patch Changes
105d901
Thanks @iiroj! - Suppress some warnings when using the "--quiet" flagv15.0.2
Compare Source
Patch Changes
8e82364
Thanks @iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.v15.0.1
Compare Source
Patch Changes
d2e6f8b
Thanks @louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.v15.0.0
Compare Source
Major Changes
#1322
66b93aa
Thanks @iiroj! - Require at least Node.js 18.12.0This release drops support for Node.js 16, which is EOL after 2023-09-11.
Please upgrade your Node.js to the latest version.
Additionally, all dependencies have been updated to their latest versions.
v14.0.1
Compare Source
Bug Fixes
v14.0.0
Compare Source
Features
BREAKING CHANGES
16.14.0
.node-fetch/node-fetch (node-fetch)
v3.3.2
Compare Source
Bug Fixes
v3.3.1
Compare Source
Bug Fixes
v3.3.0
Compare Source
Features
v3.2.10
Compare Source
Bug Fixes
Configuration
📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, 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.
This PR was generated by Mend Renovate. View the repository job log.