chore(deps-dev): bump lint-staged from 16.4.0 to 17.0.4

[dependabot]

Bumps lint-staged from 16.4.0 to 17.0.4.

Release notes

Sourced from lint-staged's releases.

v17.0.4

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

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

v17.0.2

Patch Changes

• #1779 88670ca Thanks @​iiroj! - Enable immutable GitHub releases

v17.0.1

Patch Changes

• #1776 4a5664b Thanks @​iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.

v17.0.0

Major Changes

• #1745 e244adf Thanks @​iiroj! - Node.js v20 is no longer supported, and the oldest supported version is now 22.22.1, which is an active LTS version at the time of this release. Node.js 20 will be EOL after April 2026. Please upgrade your Node.js version!

• #1676 0584e0b Thanks @​outslept! - Lint-staged now tries to verify the installed Git version is at least 2.32.0, released in 2021. If you're using an even older Git version, you need to upgrade it before running lint-staged!

• #1745 2dcc40a Thanks @​iiroj! - The dependency yaml is now marked as optional and probably won't be installed by default. If you're using a YAML configuration file you should install the package separately:

  npm install --development yaml

  If you're using .lintstagedrc as the config file name (without a file extension), it will be treated as a YAML file. If the content is JSON, consider renaming it to .lintstagedrc.json to avoid needing to install yaml.

Minor Changes

• #1748 809d5ef Thanks @​iiroj! - Add new option --hide-all for hiding all unstaged changes and untracked files, before running tasks. This makes it easier to run tools like Knip which check for unused code. Untracked files are included in the backup stash and restored automatically after running.

• #1759 f13045a Thanks @​iiroj! - Update dependencies, including tinyexec@1.1.1 to fix the following issues:

  • When using a Node.js version manager with multiple versions installed (nvm, n, for example), scripts with the #!/usr/bin/env node shebang (Prettier, ESLint, for example) were previously spawned using the default Node.js version configured by the version manager (the one which node points to) on POSIX systems. Now, they will be spawned with the same version that lint-staged itself was started with.
    • For example, if your default Node.js version is 24.14.1 but lint-staged is run with the latest version 25.9.0, the tasks spawned by lint-staged will now also use version 25.9.0. Previously they were spawned using 24.14.1.

... (truncated)

Changelog

Sourced from lint-staged's changelog.

17.0.4

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.

17.0.3

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

17.0.2

Patch Changes

• #1779 88670ca Thanks @​iiroj! - Enable immutable GitHub releases

17.0.1

Patch Changes

• #1776 4a5664b Thanks @​iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.

17.0.0

Major Changes

• #1745 e244adf Thanks @​iiroj! - Node.js v20 is no longer supported, and the oldest supported version is now 22.22.1, which is an active LTS version at the time of this release. Node.js 20 will be EOL after April 2026. Please upgrade your Node.js version!

• #1676 0584e0b Thanks @​outslept! - Lint-staged now tries to verify the installed Git version is at least 2.32.0, released in 2021. If you're using an even older Git version, you need to upgrade it before running lint-staged!

• #1745 2dcc40a Thanks @​iiroj! - The dependency yaml is now marked as optional and probably won't be installed by default. If you're using a YAML configuration file you should install the package separately:

  npm install --development yaml

  If you're using .lintstagedrc as the config file name (without a file extension), it will be treated as a YAML file. If the content is JSON, consider renaming it to .lintstagedrc.json to avoid needing to install yaml.

Minor Changes

• #1748 809d5ef Thanks @​iiroj! - Add new option --hide-all for hiding all unstaged changes and untracked files, before running tasks. This makes it easier to run tools like Knip which check for unused code. Untracked files are included in the backup stash and restored automatically after running.

... (truncated)

Commits

• 2862964 Merge pull request #1789 from lint-staged/changeset-release/main
• c9ecd54 chore(changeset): release
• cc6b51a Merge pull request #1788 from lint-staged/fix-update-index-again
• f95c1f8 fix: update both default index.lock and non-standard lock when latter exists
• f44ee68 Merge pull request #1786 from lint-staged/update-repo-url
• a61cf18 build(deps): update dependencies
• ea00037 docs: disable Changesets "thanks"
• ab7c26c docs: update repo URL to point in lint-staged/lint-staged
• a36ec1e Merge pull request #1783 from lint-staged/changeset-release/main
• 03ce2a9 chore(changeset): release
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Summary by cubic

lint-staged를 16.4.0 → 17.0.4로 업데이트했습니다. 최신 pre-commit 동작과 버그 픽스를 적용합니다.

⚠️ Breaking Changes

• Node.js 22.22.1 이상만 지원합니다. CI/로컬 Node 버전 업데이트가 필요합니다.
• Git 2.32.0 이상이 필요합니다.
• YAML 구성 사용 시 yaml를 별도 설치하거나 설정 파일을 .lintstagedrc.json으로 변경하세요.

How to test

• 버전 확인: node -v, git --version이 요구사항을 만족하는지 확인합니다.
• YAML 설정을 쓴다면: npm i -D yaml 설치 후 npx lint-staged -v로 실행 확인.
• 파일을 수정하고 git add → git commit을 실행해 훅이 정상 동작하는지 확인합니다.
• 암시적 커밋 경로도 확인: git commit -am "test" 또는 git commit -m "test" . 실행 시 태스크 결과가 커밋에 반영되는지 확인합니다.

^{Written for commit 1f0831c. Summary will update on new commits. Review in cubic}

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cubic-dev-ai]

1 issue found across 1 file

Confidence score: 3/5

• package.json was changed without updating bun.lock, so installs may continue using old resolved versions and the dependency upgrade may not actually take effect.
• This is a moderate, concrete risk (severity 6/10 with high confidence 9/10): behavior can differ across environments due to manifest/lockfile drift, but the fix is straightforward.
• Pay close attention to package.json, bun.lock - regenerate and commit the lockfile so dependency resolution is deterministic and matches the intended versions.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="package.json">

<violation number="1" location="package.json:48">
P2: 의존성 버전만 변경되고 `bun.lock`이 갱신되지 않아 실제 설치 버전이 업그레이드되지 않을 수 있습니다. `bun.lock`도 함께 갱신해 커밋하세요.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.}

[cubic-dev-ai]

P2: 의존성 버전만 변경되고 bun.lock이 갱신되지 않아 실제 설치 버전이 업그레이드되지 않을 수 있습니다. bun.lock도 함께 갱신해 커밋하세요.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 48:

<comment>의존성 버전만 변경되고 `bun.lock`이 갱신되지 않아 실제 설치 버전이 업그레이드되지 않을 수 있습니다. `bun.lock`도 함께 갱신해 커밋하세요.</comment>

<file context>
@@ -45,7 +45,7 @@
     "happy-dom": "^20.8.7",
     "husky": "^9.1.7",
-    "lint-staged": "^16.4.0",
+    "lint-staged": "^17.0.4",
     "tsdown": "^0.21.4",
     "typescript": "^6.0.2",
</file context>