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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update npm dependencies without major updates #196

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

fix(deps): update npm dependencies without major updates #196

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 2, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@commitlint/config-conventional (source) 19.1.0 -> 19.8.0 age adoption passing confidence devDependencies minor
@types/node (source) 18.19.26 -> 18.19.80 age adoption passing confidence devDependencies patch
@types/yargs (source) 17.0.32 -> 17.0.33 age adoption passing confidence devDependencies patch
@vitest/coverage-v8 (source) 1.4.0 -> 1.6.1 age adoption passing confidence devDependencies minor
ajv (source) ^8.14.0 -> 8.14.0 age adoption passing confidence dependencies pin
commitlint (source) 19.2.1 -> 19.8.0 age adoption passing confidence devDependencies minor
husky 9.0.11 -> 9.1.7 age adoption passing confidence devDependencies minor
lint-staged 15.2.2 -> 15.4.3 age adoption passing confidence devDependencies minor
p-map ^7.0.1 -> 7.0.1 age adoption passing confidence dependencies pin
tree-sitter 0.20.6 -> 0.22.4 age adoption passing confidence dependencies minor
typescript (source) 5.3.3 -> 5.8.2 age adoption passing confidence devDependencies minor

Release Notes

conventional-changelog/commitlint (@​commitlint/config-conventional)

v19.8.0

Compare Source

Performance Improvements
  • use node: prefix to bypass require.cache call for builtins (#​4302) (0cd8f41)

19.7.1 (2025-02-02)

Note: Version bump only for package @​commitlint/config-conventional

v19.7.1

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

v19.6.0

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

v19.5.0

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

19.4.1 (2024-08-28)

Note: Version bump only for package @​commitlint/config-conventional

19.2.2 (2024-04-14)

Note: Version bump only for package @​commitlint/config-conventional

v19.4.1

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

v19.2.2

Compare Source

Note: Version bump only for package @​commitlint/config-conventional

vitest-dev/vitest (@​vitest/coverage-v8)

v1.6.1

Compare Source

This release includes security patches for:

   🐞 Bug Fixes
    View changes on GitHub

v1.6.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v1.5.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
conventional-changelog/commitlint (commitlint)

v19.8.0

Compare Source

Performance Improvements
  • use node: prefix to bypass require.cache call for builtins (#​4302) (0cd8f41)

19.7.1 (2025-02-02)

Note: Version bump only for package commitlint

19.6.1 (2024-12-15)

Note: Version bump only for package commitlint

v19.7.1

Compare Source

Note: Version bump only for package commitlint

v19.6.1

Compare Source

Note: Version bump only for package commitlint

v19.6.0

Compare Source

Note: Version bump only for package commitlint

v19.5.0

Compare Source

Note: Version bump only for package commitlint

19.4.1 (2024-08-28)

Note: Version bump only for package commitlint

v19.4.1

Compare Source

Note: Version bump only for package commitlint

v19.4.0

Compare Source

Note: Version bump only for package commitlint

v19.3.0

Compare Source

Note: Version bump only for package commitlint

19.2.2 (2024-04-14)

Note: Version bump only for package commitlint

19.2.1 (2024-03-19)

Note: Version bump only for package commitlint

v19.2.2

Compare Source

Note: Version bump only for package commitlint

typicode/husky (husky)

v9.1.7

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.6...v9.1.7

v9.1.6

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.5...v9.1.6

v9.1.5

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.4...v9.1.5

v9.1.4

Compare Source

  • Improve deprecation notice

v9.1.3

Compare Source

  • fix: better handle space in PATH

v9.1.2

Compare Source

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

Compare Source

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

Deprecations

  • #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" are deprecated. husky command will automatically remove them, no action required.
  • If you're having code in ~/.huskyrc please 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

Compare Source

lint-staged/lint-staged (lint-staged)

v15.4.3

Compare Source

Patch Changes
  • #​1512 cbfed1d Thanks @​tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

v15.4.2

Compare Source

Patch Changes
  • #​1509 8827ebf Thanks @​iiroj! - Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.

v15.4.1

Compare Source

Patch Changes

v15.4.0

Compare Source

Minor Changes

  • #​1500 a8ec1dd Thanks @​iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:

    /**
 * @&#8203;filename: lint-staged.config.js
 * @&#8203;type {import('lint-staged').Configuration}
 */
export default {
  '*': 'prettier --write',
}

    It's also possible to use the .ts file extension for the configuration if your Node.js version supports it. The --experimental-strip-types flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.

    export NODE_OPTIONS="--experimental-strip-types"

npx lint-staged --config lint-staged.config.ts
Patch Changes

v15.3.0

Compare Source

Minor Changes

  • #​1495 e69da9e Thanks @​iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.

  • #​1493 fa0fe98 Thanks @​iiroj! - Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

    For example:

    % npx lint-staged
✔ Backed up original state in git stash (20addf8)
✔ Running tasks for staged files...
✔ Applying modifications from tasks...
✔ Cleaning up temporary files...

    where the backup can be seen with git show 20addf8, or git stash list:

    % git stash list
stash@{0}: lint-staged automatic backup (20addf8)

v15.2.11

Compare Source

Patch Changes

  • #​1484 bcfe309 Thanks @​wormsik! - Escape paths containing spaces when using the "shell" option.

  • #​1487 7dd8caa Thanks @​iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

v15.2.10

Compare Source

Patch Changes

v15.2.9

Compare Source

Patch Changes
  • #​1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Compare Source

Patch Changes

  • f0480f0 Thanks @​iiroj! - In the previous version the native git 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.js child_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
  • #​1440 a51be80 Thanks @​iiroj! - In the previous version the native git 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 upgrading git to the latest version.

v15.2.6

Compare Source

Patch Changes
  • #​1433 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

v15.2.4

Compare Source

Patch Changes
  • 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies
tree-sitter/node-tree-sitter (tree-sitter)

v0.22.4

Compare Source

Full Changelog: tree-sitter/node-tree-sitter@v0.22.3...v0.22.4

v0.22.3

Compare Source

v0.22.2

Compare Source

v0.22.1

Compare Source

v0.22.0

Compare Source

v0.21.1

Compare Source

v0.21.0

Compare Source

BREAKING CHANGES:

Other changes:

  • add more methods/properties to bring Node inline with Rust bindings (contributed by @​amaanq in #​191)
  • make module context aware (contributed by @​segevfiner in #​184)
  • drop Node 14 and 16 support
  • switch to prebuildify instead of prebuild-install (now binaries are stored on npm instead of GitHub Releases) (contributed by @​ObserverOfTime in #​192)
microsoft/TypeScript (typescript)

v5.8.2

Compare Source

[v5.7.3](https://redirect.github.com/micros

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Europe/Berlin, 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/npm-dependencies-without-major-updates branch 6 times, most recently from 8ca11f6 to 7893ad3 Compare March 13, 2024 16:27
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 6 times, most recently from eacb59e to fd1055b Compare March 20, 2024 21:02
@clemens-mw clemens-mw mentioned this pull request Mar 20, 2024
Open
@mylinhdao
Copy link
Collaborator

To update the new tree-sitter version, all our supported languages need to update their Node binding for using Node API. So we should wait them to be changed before we merge this PR.

@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 2 times, most recently from 05aec1e to 49bd960 Compare March 28, 2024 12:21
@renovate renovate bot changed the title chore(deps): update npm dependencies without major updates fix(deps): update npm dependencies without major updates Mar 28, 2024
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 3 times, most recently from cae8153 to 5883ff2 Compare March 30, 2024 08:52
@renovate renovate bot changed the title fix(deps): update npm dependencies without major updates chore(deps): update npm dependencies without major updates Mar 30, 2024
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 5 times, most recently from 743cce8 to 28ff1e3 Compare April 9, 2024 08:01
@github-actions GitHub Actions
Copy link

github-actions bot commented Apr 9, 2024 •
edited
Loading

Coverage Report

Status Category Percentage Covered / Total
🔴 Lines 64.72% (🎯 90%) 3189 / 4927
🔴 Statements 64.72% (🎯 90%) 3189 / 4927
🔴 Functions 57.52% (🎯 90%) 130 / 226
🔴 Branches 88.7% (🎯 90%) 267 / 301
File CoverageNo changed files found.
Generated in workflow #282 for commit c2b76ad by the Vitest Coverage Report Action

@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 3 times, most recently from 25fdab3 to c85039f Compare April 11, 2024 18:10
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 2 times, most recently from 9b4c468 to 9b29a2f Compare November 28, 2024 07:26
@renovate renovate bot changed the title chore(deps): update npm dependencies without major updates fix(deps): update npm dependencies without major updates Dec 10, 2024
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 3 times, most recently from d176b05 to 008fd6e Compare December 15, 2024 16:04
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 2 times, most recently from 371f691 to ed18452 Compare December 30, 2024 03:44
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 3 times, most recently from 8c70153 to f463d7d Compare January 8, 2025 23:06
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 6 times, most recently from 065d32a to 1e6504d Compare January 23, 2025 12:40
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch from 1e6504d to 185f2bb Compare January 26, 2025 16:47
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 3 times, most recently from 826cc38 to c2b76ad Compare February 4, 2025 00:57
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch from c2b76ad to c00ff89 Compare February 14, 2025 02:56
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Feb 14, 2025 •
edited
Loading

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/vitest
npm error   dev vitest@"1.4.0" from the root project
npm error   peer vitest@"1.4.0" from @vitest/[email protected]
npm error   node_modules/@vitest/browser
npm error     peerOptional @vitest/browser@"1.4.0" from [email protected]
npm error   1 more (@vitest/ui)
npm error
npm error Could not resolve dependency:
npm error peer vitest@"1.6.1" from @vitest/[email protected]
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"1.6.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-03-08T10_36_04_890Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-03-08T10_36_04_890Z-debug-0.log

@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch 5 times, most recently from a0324f5 to 12a0071 Compare March 7, 2025 17:51
@renovate renovate bot force-pushed the renovate/npm-dependencies-without-major-updates branch from 12a0071 to 4296be3 Compare March 8, 2025 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@mylinhdao