Packages

lint-staged

17.6.0 · 26 Sep 2026MIT26.8M / weekRepositoryHomepagenpmAtom feed

Upgrading lint-staged from 15.0.2 to 15.5.2

20 releases in betweenevery note read

Other targets from 15.0.2Latest17.6.0
0
changes to make
0
advisories fixed
8
new
23
fixes

Release by release

  1. 15.5.2

    6 May 20251 fix
    • fixed

      Correctly handle colon (:) characters in staged filenames.

  2. 15.5.1

    11 Apr 20251 fix
    • fixed

      Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:

  3. 15.5.0

    12 Mar 20251 new
    • new

      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.

  4. 15.4.3

    26 Jan 20251 fix
    • fixed

      Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

  5. 15.4.2

    23 Jan 20251 fix
    • fixed

      Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.

  6. 15.4.1

    16 Jan 20251 new · 1 fix
    • new

      Add missing conditional exports syntax for TypeScript types.

    • fixed

      Default TypeScript config filenames match JS equivalents.

  7. 15.4.0

    16 Jan 20251 new · 1 fix
    • new

      Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:

    • fixed

      Handle possible failures when logging user shell for debug info.

  8. 15.3.0

    28 Dec 20242 new
    • new

      Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.

    • new

      Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

8 other lines we could not sort, mostly version bumps
  • Stage file.js with only double quotes " changed to '

    15.5.0
  • Run git commit -am "I don't like double quotes"

    15.5.0
  • Lint-staged runs prettier --write file.js, converting all the ' back to "

    15.5.0
  • Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state

    15.5.0
  • Commit was not done, original state is restored and single quotes ' are staged

    15.5.0
  • Stage file.js with only double-quotes " changed to '

    15.5.0
  • Because there are now no changes, lint-staged fails and cancels the commit

    15.5.0
  • Commit was not done, and there are no staged changes

    15.5.0