chore(deps-dev): bump lint-staged from 17.3.0 to 17.4.1

[dependabot]

Bumps lint-staged from 17.3.0 to 17.4.1.

Release notes

Sourced from lint-staged's releases.

v17.4.1

17.4.1

Patch Changes

• #1840 efe5b63 - This is a version-bump-only release because the previous version 17.4.0 was not published to npmjs.com due to problems with GitHub Actions and Changesets.

17.4.0

Minor Changes

• #1836 90ec282 - Added a new defineConfig helper for type-checking the lint-staged configuration:

  // lint-staged.config.ts
  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*.js': ['prettier --check', 'eslint'],
  })

• #1832 510a27c - Added a new flag --all to make lint-staged include all files tracked by Git, instead of only staged.

  By default lint-staged only runs tasks on files that include staged changes (hence the name). Use this flag to include all files tracked in Git version control (standard exclusions apply). Using this flag implies the --no-stash flag, disabling the automatic backup, and the --allow-empty flag so that lint-staged doesn't fail when there are no changes after running. This makes it easier to run npx lint-staged --all on a clean state, for example in CI.

Patch Changes

• #1838 69bec99 - The behavior of the automatic backup stash has been improved when running lint-staged in multiple worktrees in parallel. You should still avoid running multiple instances of lint-staged in parallel in the same tree, because some of the Git operations are locking and might lead to data loss.

• #1839 5e5bdd2 - Parsing of lint-staged CLI flags and Node.js API options has been rewritten to avoid inconsistent behavior between the two.

Changelog

Sourced from lint-staged's changelog.

17.4.1

Patch Changes

• #1840 efe5b63 - This is a version-bump-only release because the previous version 17.4.0 was not published to npmjs.com due to problems with GitHub Actions and Changesets.

17.4.0

Minor Changes

• #1836 90ec282 - Added a new defineConfig helper for type-checking the lint-staged configuration:

  // lint-staged.config.ts
  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*.js': ['prettier --check', 'eslint'],
  })

• #1832 510a27c - Added a new flag --all to make lint-staged include all files tracked by Git, instead of only staged.

  By default lint-staged only runs tasks on files that include staged changes (hence the name). Use this flag to include all files tracked in Git version control (standard exclusions apply). Using this flag implies the --no-stash flag, disabling the automatic backup, and the --allow-empty flag so that lint-staged doesn't fail when there are no changes after running. This makes it easier to run npx lint-staged --all on a clean state, for example in CI.

Patch Changes

• #1838 69bec99 - The behavior of the automatic backup stash has been improved when running lint-staged in multiple worktrees in parallel. You should still avoid running multiple instances of lint-staged in parallel in the same tree, because some of the Git operations are locking and might lead to data loss.

• #1839 5e5bdd2 - Parsing of lint-staged CLI flags and Node.js API options has been rewritten to avoid inconsistent behavior between the two.

Commits

• d0c1517 Merge pull request #1841 from lint-staged/changeset-release/main
• f061335 chore(changeset): release
• d2721af Merge pull request #1840 from lint-staged/updates
• efe5b63 ci: update Changesets action because it failed to publish
• cd76ce3 build: update dependencies
• ea195e1 Merge pull request #1837 from lint-staged/changeset-release/main
• a6a0d61 chore(changeset): release
• 0a09098 Merge pull request #1832 from lint-staged/add-all-flag
• 7fd685b fix: further fix parsing options logic
• 510a27c feat: add --all flag for including all files tracked by Git instead of just...
• 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)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
website-odsf	Ready	Preview	Sep 4, 2026 8:36am UTC

[github-actions]

❌MegaLinter analysis: Error

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ COPYPASTE	jscpd	yes		no	no	0.67s
✅ EDITORCONFIG	editorconfig-checker	1		0	0	0.01s
✅ JSON	jsonlint	1		0	0	0.09s
✅ JSON	npm-package-json-lint	yes		no	no	0.27s
✅ JSON	v8r	1		0	0	8.98s
✅ REPOSITORY	betterleaks	yes		no	no	0.97s
✅ REPOSITORY	checkov	yes		no	no	24.57s
✅ REPOSITORY	gitleaks	yes		no	no	2.24s
✅ REPOSITORY	git_diff	yes		no	no	0.43s
⚠️ REPOSITORY	grype	yes		4	no	50.92s
❌ REPOSITORY	osv-scanner	yes		4	no	1.86s
✅ REPOSITORY	secretlint	yes		no	no	4.71s
✅ REPOSITORY	syft	yes		no	no	3.26s
✅ REPOSITORY	trivy	yes		no	no	10.68s
✅ REPOSITORY	trivy-sbom	yes		no	no	2.31s
✅ REPOSITORY	trufflehog	yes		no	no	2.24s
✅ SPELL	cspell	2		0	0	1.82s
✅ SPELL	lychee	1		0	0	0.03s

Detailed Issues

❌ REPOSITORY / osv-scanner - 4 errors

Scanning dir .
Starting filesystem walk for root: /
Scanned pnpm-lock.yaml file and found 1068 packages
End status: 223 dirs visited, 1094 inodes visited, 1 Extract calls, 31.111795ms elapsed, 31.111893ms wall time

Total 1 package affected by 4 known vulnerabilities (0 Critical, 4 High, 0 Medium, 0 Low, 0 Unknown) from 1 ecosystem.
4 vulnerabilities can be fixed.

+-------------------------------------+------+-----------+----------+---------+---------------+----------------+
| OSV URL                             | CVSS | ECOSYSTEM | PACKAGE  | VERSION | FIXED VERSION | SOURCE         |
+-------------------------------------+------+-----------+----------+---------+---------------+----------------+
| https://osv.dev/GHSA-5jgf-p345-68v8 | 7.5  | npm       | fast-uri | 3.1.5   | 3.1.6         | pnpm-lock.yaml |
| https://osv.dev/GHSA-f65p-4m7j-42xc | 7.5  | npm       | fast-uri | 3.1.5   | 3.1.6         | pnpm-lock.yaml |
| https://osv.dev/GHSA-fph4-wmhf-6fwf | 7.5  | npm       | fast-uri | 3.1.5   | 3.1.6         | pnpm-lock.yaml |
| https://osv.dev/GHSA-jqff-g426-hqxp | 7.5  | npm       | fast-uri | 3.1.5   | 3.1.6         | pnpm-lock.yaml |
+-------------------------------------+------+-----------+----------+---------+---------------+----------------+

⚠️ REPOSITORY / grype - 4 errors

[0000]  WARN no explicit name and version provided for directory source, deriving artifact ID from the given path (which is not ideal) from=syft
NAME      INSTALLED  FIXED IN  TYPE  VULNERABILITY        SEVERITY  EPSS         RISK  
fast-uri  3.1.5      3.1.6     npm   GHSA-5jgf-p345-68v8  High      0.2% (13th)  0.2   
fast-uri  3.1.5      3.1.6     npm   GHSA-jqff-g426-hqxp  High      0.2% (13th)  0.2   
fast-uri  3.1.5      3.1.6     npm   GHSA-f65p-4m7j-42xc  High      0.2% (12th)  0.2   
fast-uri  3.1.5      3.1.6     npm   GHSA-fph4-wmhf-6fwf  High      0.2% (12th)  0.2
[0050] ERROR discovered vulnerabilities at or above the severity threshold

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

Show us your support by starring ⭐ the repository

[github-actions]

	Fails
🚫	📋 Missing Section - Please include the section: ## Description in your PR description.
🚫	📋 Missing Section - Please include the section: ## Type of Change in your PR description.
🚫	📋 Missing Section - Please include the section: ## How Has This Been Tested? in your PR description.
🚫	📋 Missing Section - Please include the section: ## Checklist in your PR description.

	Warnings
⚠️	📋 Unchecked Checklist Item - Please check the item: My code follows the style guidelines of this project in your PR description.
⚠️	📋 Unchecked Checklist Item - Please check the item: I have performed a self-review of my code in your PR description.
⚠️	📋 Unchecked Checklist Item - Please check the item: I have commented my code, particularly in hard-to-understand areas in your PR description.
⚠️	📋 Unchecked Checklist Item - Please check the item: I have made corresponding changes to the documentation in your PR description.
⚠️	📋 Unchecked Checklist Item - Please check the item: My changes generate no new warnings in your PR description.
⚠️	📋 Unchecked Checklist Item - Please check the item: Any dependent changes have been merged and published in downstream modules in your PR description.
⚠️	📋 Unchecked Checklist Item - Please check the item: I have checked my code and corrected any misspellings in your PR description.

	Messages
📖	Thanks! We ❤️ small PRs!

Generated by 🚫 dangerJS against 28b555c