Bump lint-staged from 15.4.3 to 15.5.2

[dependabot]

Bumps lint-staged from 15.4.3 to 15.5.2.

Release notes

Sourced from lint-staged's releases.

v15.5.2

Patch Changes

• #1544 5561321 Thanks @​YimingIsCOLD! - Correctly handle colon (:) characters in staged filenames.

v15.5.1

Patch Changes

• #1533 5d53534 Thanks @​iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:

  ✖ Failed to get staged files!
  

v15.5.0

Minor Changes

• #1526 630af5f Thanks @​iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.

  Example with Prettier

  By default Prettier prefers double quotes.

  Previously

  1. Stage file.js with only double quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
  5. Commit was not done, original state is restored and single quotes ' are staged

  Now

  1. Stage file.js with only double-quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails and cancels the commit
  5. Commit was not done, and there are no staged changes

Changelog

Sourced from lint-staged's changelog.

15.5.2

Patch Changes

• #1544 5561321 Thanks @​YimingIsCOLD! - Correctly handle colon (:) characters in staged filenames.

15.5.1

Patch Changes

• #1533 5d53534 Thanks @​iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:

  ✖ Failed to get staged files!
  

15.5.0

Minor Changes

• #1526 630af5f Thanks @​iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.

  Example with Prettier

  By default Prettier prefers double quotes.

  Previously

  1. Stage file.js with only double quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
  5. Commit was not done, original state is restored and single quotes ' are staged

  Now

  1. Stage file.js with only double-quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails and cancels the commit
  5. Commit was not done, and there are no staged changes

Commits

• 8e91302 chore(changeset): release
• 64148fd Merge pull request #1545 from lint-staged/revert-v16-changes
• 46f47b2 Revert "build(deps): update dependencies"
• 9472af9 Revert "build(execa): upgrade execa@9.5.2, require Node.js ^18.19.0 || >=20.5.0"
• 9e17c9c Revert "chore: remove validation of deprecated advanced config options"
• 6fda79a Revert "feat: remove --shell flag support"
• e1ea676 Revert "feat: replace execa with nano-spawn"
• 5561321 fix: handle colon characters in staged filenames (#1544)
• dcc9a51 feat: replace execa with nano-spawn
• 2fa909d feat: remove --shell flag support
• Additional commits viewable in compare view