Skip to content

chore(deps): update dependency lint-staged to ^17.2.0 - #261

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/lint-staged-17.x
Open

chore(deps): update dependency lint-staged to ^17.2.0#261
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/lint-staged-17.x

Conversation

@renovate

@renovate renovate Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
lint-staged ^17.0.0^17.2.0 age confidence

Release Notes

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

v17.2.0

Compare Source

Minor Changes
  • #​1823 ee156cc - The chunking of tasks based on maximum command line argument length has been re-implemented to be more precise. Now the chunking happens based on the final generated command string, instead of just the list of staged files like previously. This benefits mainly Windows platforms and function commands like:

    /** @​type {import('lint-staged').Configuration} */
    export default {
      "*.ts": () => "tsc", // Run "tsc" when any TS file is changed (for entire project)
    };

    Where the spawned command is literally "tsc" without any extra arguments. Previously, this was still chunked when a lot of files were staged. Now, it probably won't be chunked because the length of the command is just three letters.

    Also, native JavaScript/Node.js function tasks won't be chunked at all, when previously they were run multiple times when chunked:

    /** @​type {import('lint-staged').Configuration} */
    export default {
      "*.js": {
        title: "Log staged JS files to console",
        task: async (files) => {
          console.log("Staged JS files:", files);
        },
      },
    };

v17.1.1

Compare Source

Patch Changes
  • #​1820 a626a9f - It's now possible to set --max-arg-length=Infinity to effectively disable chunking of tasks based on the number of staged files. The parsing and validation of the numeric CLI options --max-arg-length and --concurrency has been improved.

v17.1.0

Compare Source

Minor Changes
  • #​1816 7568d4f - The console output of lint-staged has been simplified so that there's less interactive spinners and more explicit messages like "Started…" -> "Done!". The primary purpose of this was to remove Listr2, a very large dependency.

    Before:

    Size of node_modules/ after installing: 1561.7 kB with 29 packages.

    Fancy interactive spinners, but output dynamically changes:

    ✔ Backed up original state in git stash (0b191303)
    ✔ Running tasks for staged files...
    ✔ Staging changes from tasks...
    ✔ Cleaning up temporary files...

    After:

    Size of node_modules/ after installing: 974.0 kB with 5 packages (37.6 % smaller, 82.7 % less transitive dependencies).

    Simpler but more explicit output:

    ⋯ Backing up original state…
    ✔ Done backing up original state (35b38ed1)!
    ⋯ Running tasks for staged files…
        *.js — 1 file
          ⋯ oxlint --fix
        *.{json,md} — 1 file
          ⋯ oxfmt --write
    
    ✔ oxfmt --write
    ✔ oxlint --fix
    
    ✔ Done running tasks for staged files!
    ⋯ Staging changes from tasks…
    ✔ Done staging changes from tasks!
    ⋯ Cleaning up temporary files…
    ✔ Done cleaning up temporary files!
Patch Changes
  • #​1816 c19079d - Try to restore hidden unstaged changes when using --no-revert.

  • #​1818 efb23a2 - Console output colors are enabled/disabled more consistently.

  • #​1818 26112a1 - Failed JS function tasks now properly kill other tasks, unless --continue-on-error is used. Previously their failure didn't affect other tasks.

v17.0.8

Compare Source

Patch Changes
  • #​1809 179b437 - Fix lint-staged discarding the ongoing merge conflict status (.git/MERGE_HEAD) when using the --hide-unstaged or --hide-all options.

  • #​1811 3d0b2c0 - Fix issues with Git commands that are successful but also emit warnings to stderr, by ignoring the stderr output completely when the process exits with code 0. This was the behavior when using nano-spawn and execa, but when switching to tinyexec in 16.3.0 both stdout and stderr were used as interleaved output.

v17.0.7

Compare Source

Patch Changes

v17.0.6

Compare Source

Patch Changes
  • #​1803 bdf2770 - Run all tests with Deno, in addition to Node.js and Bun.

  • #​1796 7508272 - Fix performance regression of lint-staged v17 by going back to using git add to stage task modifications. This was changed to git update-index --again in v17 for less manual work, but unfortunately the update-index command gets slower in very large Git repos.

  • #​1797 7b2505a - This version of lint-staged uses the new staged publishing for npm packages feature. Releases are already published from GitHub Actions with trusted publishing, but now an additional approval with two-factor authentication is also required.

  • #​1802 321b0a9 - Downgrade dependency tinyexec@1.2.2 to avoid issues in version 1.2.3.

v17.0.5

Compare Source

Patch Changes
  • #​1792 1f67271 - Correctly set the --max-arg-length default value based on the running platform. This controls how very long lists of staged files are split into multiple chunks.

v17.0.4

Compare Source

Patch Changes
  • #​1788 f95c1f8 - Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:

    • after editing <file> it is staged with git add <file>, and then committed with git commit
    • after editing <file> it is committed with git commit --all without explicit git add
    • after editing <file> it is committed with git commit <pathspec> without explicit git add

    There's new test cases which actually setup the Git pre_commit hook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.

v17.0.3

Compare Source

Patch Changes
  • #​1782 06813f9 Thanks @​iiroj! - Fix lint-staged behavior when implicitly committing files without using git add by either:
    • git commit -am "my commit message" where -a (--all) means to automatically stage all tracked modified and deleted files
    • git commit -m "my commit message" . where . is an example of a pathspec where matching files will be staged

Configuration

📅 Schedule: (in timezone Asia/Kolkata)

  • Branch creation
    • Between 09:00 AM and 09:59 AM, only on Monday and Thursday (* 9 * * 1,4)
  • Automerge
    • Between 09:00 PM and 09:59 PM, only on Monday and Thursday (* 21 * * 1,4)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate Bot added the minor label Jul 27, 2026
@changeset-bot

changeset-bot Bot commented Jul 27, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 2f4d3a3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate
renovate Bot force-pushed the renovate/lint-staged-17.x branch from f185dbe to 8813662 Compare July 27, 2026 05:46
@pkg-pr-new

pkg-pr-new Bot commented Jul 27, 2026

Copy link
Copy Markdown

Open in StackBlitz

js-utils-kit

npm i https://pkg.pr.new/js-utils-kit@261
pnpm add https://pkg.pr.new/js-utils-kit@261
yarn add https://pkg.pr.new/js-utils-kit@261.tgz
bun add https://pkg.pr.new/js-utils-kit@261.tgz

juk-cli

npm i https://pkg.pr.new/juk-cli@261
pnpm add https://pkg.pr.new/juk-cli@261
yarn add https://pkg.pr.new/juk-cli@261.tgz
bun add https://pkg.pr.new/juk-cli@261.tgz

juk-web

npm i https://pkg.pr.new/juk-web@261
pnpm add https://pkg.pr.new/juk-web@261
yarn add https://pkg.pr.new/juk-web@261.tgz
bun add https://pkg.pr.new/juk-web@261.tgz

@js-utils-kit/array

npm i https://pkg.pr.new/@js-utils-kit/array@261
pnpm add https://pkg.pr.new/@js-utils-kit/array@261
yarn add https://pkg.pr.new/@js-utils-kit/array@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/array@261.tgz

@js-utils-kit/charset

npm i https://pkg.pr.new/@js-utils-kit/charset@261
pnpm add https://pkg.pr.new/@js-utils-kit/charset@261
yarn add https://pkg.pr.new/@js-utils-kit/charset@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/charset@261.tgz

@js-utils-kit/constants

npm i https://pkg.pr.new/@js-utils-kit/constants@261
pnpm add https://pkg.pr.new/@js-utils-kit/constants@261
yarn add https://pkg.pr.new/@js-utils-kit/constants@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/constants@261.tgz

@js-utils-kit/core

npm i https://pkg.pr.new/@js-utils-kit/core@261
pnpm add https://pkg.pr.new/@js-utils-kit/core@261
yarn add https://pkg.pr.new/@js-utils-kit/core@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/core@261.tgz

@js-utils-kit/env

npm i https://pkg.pr.new/@js-utils-kit/env@261
pnpm add https://pkg.pr.new/@js-utils-kit/env@261
yarn add https://pkg.pr.new/@js-utils-kit/env@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/env@261.tgz

@js-utils-kit/fs

npm i https://pkg.pr.new/@js-utils-kit/fs@261
pnpm add https://pkg.pr.new/@js-utils-kit/fs@261
yarn add https://pkg.pr.new/@js-utils-kit/fs@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/fs@261.tgz

@js-utils-kit/number

npm i https://pkg.pr.new/@js-utils-kit/number@261
pnpm add https://pkg.pr.new/@js-utils-kit/number@261
yarn add https://pkg.pr.new/@js-utils-kit/number@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/number@261.tgz

@js-utils-kit/object

npm i https://pkg.pr.new/@js-utils-kit/object@261
pnpm add https://pkg.pr.new/@js-utils-kit/object@261
yarn add https://pkg.pr.new/@js-utils-kit/object@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/object@261.tgz

@js-utils-kit/pm

npm i https://pkg.pr.new/@js-utils-kit/pm@261
pnpm add https://pkg.pr.new/@js-utils-kit/pm@261
yarn add https://pkg.pr.new/@js-utils-kit/pm@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/pm@261.tgz

@js-utils-kit/regex

npm i https://pkg.pr.new/@js-utils-kit/regex@261
pnpm add https://pkg.pr.new/@js-utils-kit/regex@261
yarn add https://pkg.pr.new/@js-utils-kit/regex@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/regex@261.tgz

@js-utils-kit/string

npm i https://pkg.pr.new/@js-utils-kit/string@261
pnpm add https://pkg.pr.new/@js-utils-kit/string@261
yarn add https://pkg.pr.new/@js-utils-kit/string@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/string@261.tgz

@js-utils-kit/system

npm i https://pkg.pr.new/@js-utils-kit/system@261
pnpm add https://pkg.pr.new/@js-utils-kit/system@261
yarn add https://pkg.pr.new/@js-utils-kit/system@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/system@261.tgz

@js-utils-kit/types

npm i https://pkg.pr.new/@js-utils-kit/types@261
pnpm add https://pkg.pr.new/@js-utils-kit/types@261
yarn add https://pkg.pr.new/@js-utils-kit/types@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/types@261.tgz

@js-utils-kit/valid

npm i https://pkg.pr.new/@js-utils-kit/valid@261
pnpm add https://pkg.pr.new/@js-utils-kit/valid@261
yarn add https://pkg.pr.new/@js-utils-kit/valid@261.tgz
bun add https://pkg.pr.new/@js-utils-kit/valid@261.tgz

commit: 2f4d3a3

@codecov

codecov Bot commented Jul 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@renovate
renovate Bot force-pushed the renovate/lint-staged-17.x branch from acb149a to 710369b Compare July 27, 2026 10:05
@renovate
renovate Bot force-pushed the renovate/lint-staged-17.x branch from aefe6e4 to 2fa0f6c Compare July 27, 2026 10:08
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.

0 participants