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

[dependabot]

Bumps lint-staged from 16.4.0 to 17.0.5.

Release notes

Sourced from lint-staged's releases.

v17.0.5

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

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

... (truncated)

Changelog

Sourced from lint-staged's changelog.

17.0.5

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.

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

... (truncated)

Commits

• cbd822e Merge pull request #1793 from lint-staged/changeset-release/main
• 1911244 chore(changeset): release
• 7339d7d Merge pull request #1792 from lint-staged/fix-max-arg-length-default
• 1f67271 fix: default maxArgLength to undefined instead of NaN when parsing cli ...
• 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
• Additional commits viewable in compare view

[github-actions]

⚡ Performance Benchmark Results

❌ Build Time Benchmarks: FAILED

❌ Bundle Size Benchmarks: FAILED

❌ Runtime Vitals Benchmarks: FAILED

📝 Note: Detailed results are available in the job logs.

🎯 Performance Budgets:

• Build time: <70s total
• First-load JS: <100KB gzipped
• FCP: <1.5s, LCP: <2.5s, TTI: <3s

---

Updated: 2026-05-21T18:48:43.094Z

[github-actions]

✅ Visual Regression Test Results

Status: ✅ All visual tests passed!

All screenshots match the baseline. No visual regressions detected! 🎉

[github-actions]

♿ Accessibility Test Results

Overall Status: ✅ 0/0 tests passed

🦮 WCAG 2.1 AA Compliance

No WCAG test results available

⌨️ Keyboard Navigation

No keyboard navigation test results available

---

⚠️ No accessibility tests were executed. Check the workflow logs for setup issues.

📊 Detailed Report

Download the full HTML accessibility report from the workflow artifacts for:

• Detailed WCAG violation descriptions
• Specific element selectors and fixes
• Color contrast issues
• Keyboard navigation flow analysis

🔍 Testing Checklist

Our accessibility tests verify:

• ✅ WCAG 2.1 Level AA compliance
• ✅ Color contrast in light and dark modes
• ✅ Tab key navigation through all interactive elements
• ✅ Focus indicators are visible
• ✅ No keyboard traps
• ✅ Skip links and ARIA landmarks
• ✅ Screen reader compatibility

---

Powered by @axe-core/playwright and Playwright

[github-actions]

❌ Visual Regression Test Results

Status: ❌ Visual regression tests failed

Visual differences were detected! Please review:

1. Download the artifacts from this workflow run
2. Check the visual-regression-diffs artifact for comparison images
3. If changes are intentional, update snapshots locally:

   pnpm test:e2e --update-snapshots
   git add packages/e2e/tests/__screenshots__
   git commit -m "Update visual regression baselines"

---

📸 Baseline screenshots are committed to the repo for reproducible testing.