This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| lint-staged | ^15.2.2 -> ^16.1.5 |
Release Notes
lint-staged/lint-staged (lint-staged)
v16.1.5
Patch Changes
- #1608
4e3ce22Thanks @srsatt! - Detect the git repo's top-level directory correctly when in a worktree.
v16.1.4
Patch Changes
- #1604
90b37b0Thanks @iiroj! - Add anothertypesfield topackage.jsonto make even more sure NPM detects that lint-staged includes built-in TypeScript type definitions.
v16.1.3
Patch Changes
- #1602
7ea700bThanks @dword-design! - Add thetypesfield topackage.jsonto make sure NPM detects lint-staged includes built-in TypeScript type definitions.
v16.1.2
Patch Changes
#1570
a7c0c88Thanks @ItsNickBarry! - When using--diff-filterwith theDoption to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error fromgit addlikefatal: pathspec 'deleted-file' did not match any files.38f942eThanks @iiroj! - Removed an extraneous log entry that printedshouldHidePArtiallyStagedFilesto console output.
v16.1.1
Patch Changes
#1565
3686977Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using--no-stash.#1571
02299a9Thanks @iiroj! - Function tasks (introduced in v16.0.0) only received the staged files matching the conpmnfigured glob, instead of all staged files.#1563
bc61c74Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the--no-stashoption. This happened because--no-stashimplied--no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.The previous (incorrect) behavior can still be achieved by using both options
--no-stash --no-hide-partially-stagedat the same time.
v16.1.0
Minor Changes
#1536
e729daaThanks @iiroj! - A new flag--no-reverthas been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, lint-staged will clear all task modifications and revert to the original state.#1550
b27fa3fThanks @iiroj! - Lint-staged now ignores symlinks and leaves them out from the list of staged files.
Patch Changes
- #1558
c37dc38Thanks @iiroj! - The minimum required Node.js version is lowered to20.17following nano-spawn@1.0.2.
v16.0.0
Major Changes
#1546
158d15cThanks @iiroj! - Processes are spawned using nano-spawn instead of execa. If you are using Node.js scripts as tasks, you might need to explicitly run them withnode, especially when using Windows:{ "*.js": "node my-js-linter.js" }#1546
158d15cThanks @iiroj! - The--shellflag has been removed and lint-staged no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via"$@​":
v15.5.2
Patch Changes
- #1544
5561321Thanks @YimingIsCOLD! - Correctly handle colon (:) characters in staged filenames.
v15.5.1
Patch Changes
#1533
5d53534Thanks @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
630af5fThanks @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
- Stage
file.jswith only double quotes"changed to' - Run
git commit -am "I don't like double quotes" - Lint-staged runs
prettier --write file.js, converting all the'back to" - Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
- Commit was not done, original state is restored and single quotes
'are staged
Now
- Stage
file.jswith only double-quotes"changed to' - Run
git commit -am "I don't like double quotes" - Lint-staged runs
prettier --write file.js, converting all the'back to" - Because there are now no changes, lint-staged fails and cancels the commit
- Commit was not done, and there are no staged changes
v15.4.3
Patch Changes
- #1512
cbfed1dThanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.
v15.4.2
Patch Changes
- #1509
8827ebfThanks @iiroj! - 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.
v15.4.1
Patch Changes
#1504
1c7a45eThanks @iiroj! - Default TypeScript config filenames match JS equivalents.#1504
9cc18c9Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types.
v15.4.0
Minor Changes
#1500
a8ec1ddThanks @iiroj! - 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:/** * @​filename: lint-staged.config.js * @​type {import('lint-staged').Configuration} */ export default { '*': 'prettier --write', }It's also possible to use the
.tsfile extension for the configuration if your Node.js version supports it. The--experimental-strip-typesflag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.export NODE_OPTIONS="--experimental-strip-types" npx lint-staged --config lint-staged.config.ts
Patch Changes
v15.3.0
Minor Changes
#1495
e69da9eThanks @iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.#1493
fa0fe98Thanks @iiroj! - Added more help messages around the automaticgit stashthat 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.For example:
% npx lint-staged ✔ Backed up original state in git stash (20addf8) ✔ Running tasks for staged files... ✔ Applying modifications from tasks... ✔ Cleaning up temporary files...where the backup can be seen with
git show 20addf8, orgit stash list:% git stash list stash@{0}: lint-staged automatic backup (20addf8)
v15.2.11
Patch Changes
#1484
bcfe309Thanks @wormsik! - Escape paths containing spaces when using the "shell" option.#1487
7dd8caaThanks @iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.
v15.2.10
Patch Changes
v15.2.9
Patch Changes
- #1463
b69ce2dThanks @iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warningMaxListenersExceededWarning: Possible EventEmitter memory leak detected.
v15.2.8
Patch Changes
f0480f0Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version switched the--show-toplevelflag with--show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_process. The new flag returns a path relative to the working directory, avoiding the issue.The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.
v15.2.7
Patch Changes
- #1440
a51be80Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevelcommand was taken into use for resolving the current git repo root. This version drops the--path-format=absoluteoption to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgradinggitto the latest version.
v15.2.6
Patch Changes
- #1433
119adb2Thanks @iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.
v15.2.5
Patch Changes
#1424
31a1f95Thanks @iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.#1423
91abea0Thanks @iiroj! - Improve error logging when failing to read or parse a configuration file#1424
ee43f15Thanks @iiroj! - Upgrade micromatch@4.0.7
v15.2.4
Patch Changes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.