Update dependency lint-staged to v15 - autoclosed #68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
11.2.6->15.5.2Release Notes
lint-staged/lint-staged (lint-staged)
v15.5.2Compare Source
Patch Changes
5561321Thanks @YimingIsCOLD! - Correctly handle colon (:) characters in staged filenames.v15.5.1Compare Source
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:v15.5.0Compare Source
Minor Changes
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
file.jswith only double quotes"changed to'git commit -am "I don't like double quotes"prettier --write file.js, converting all the'back to"'are stagedNow
file.jswith only double-quotes"changed to'git commit -am "I don't like double quotes"prettier --write file.js, converting all the'back to"v15.4.3Compare Source
Patch Changes
cbfed1dThanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.v15.4.2Compare Source
Patch Changes
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.1Compare Source
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.0Compare Source
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: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.Patch Changes
9b79364Thanks @iiroj! - Handle possible failures when logging user shell for debug info.v15.3.0Compare Source
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:
where the backup can be seen with
git show 20addf8, orgit stash list:v15.2.11Compare Source
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.10Compare Source
Patch Changes
e3f283bThanks @iiroj! - Update minor dependencies, includingmicromatch@~4.0.8.v15.2.9Compare Source
Patch Changes
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.8Compare Source
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.7Compare Source
Patch Changes
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.6Compare Source
Patch Changes
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.5Compare Source
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.7v15.2.4Compare Source
Patch Changes
4f4537aThanks @iiroj! - Fix release issue with previous version; update dependenciesv15.2.2Compare Source
Patch Changes
fdcdad4Thanks @iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.v15.2.1Compare Source
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.0Compare Source
Minor Changes
f3378beThanks @iiroj! - Using the--no-stashflag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag--no-hide-partially-stagedthat is automatically enabled when--no-stashis used.Patch Changes
#1362
17bc480Thanks @antonk52! - update lilconfig@3.0.0#1368
7c55ca9Thanks @iiroj! - Update most dependencies#1368
777d4e9Thanks @iiroj! - To improve performance, only uselilconfigwhen searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.#1373
85eb0ddThanks @iiroj! - When determining git directory, usefs.realpath()only for symlinks. It looks likefs.realpath()changes some Windows mapped network filepaths unexpectedly, causing issues.v15.1.0Compare Source
Minor Changes
0423311Thanks @danielbayley! - Add support for loading configuration frompackage.yamlandpackage.ymlfiles, supported bypnpm.Patch Changes
105d901Thanks @iiroj! - Suppress some warnings when using the "--quiet" flagv15.0.2Compare Source
Patch Changes
8e82364Thanks @iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.v15.0.1Compare Source
Patch Changes
d2e6f8bThanks @louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.v15.0.0Compare Source
Major Changes
#1322
66b93aaThanks @iiroj! - Require at least Node.js 18.12.0This release drops support for Node.js 16, which is EOL after 2023-09-11.
Please upgrade your Node.js to the latest version.
Additionally, all dependencies have been updated to their latest versions.
v14.0.1Compare Source
Bug Fixes
v14.0.0Compare Source
Features
BREAKING CHANGES
16.14.0.v13.3.0Compare Source
Bug Fixes
Features
listr2@​6.6.0(09844ca)v13.2.3Compare Source
Bug Fixes
--diffoption implies--no-stash(66a716d)v13.2.2Compare Source
Bug Fixes
yaml@2.2.2(GHSA-f9xv-q969-pqx4) (#1290) (cf691aa)v13.2.1Compare Source
Bug Fixes
v13.2.0Compare Source
Bug Fixes
colorettewithchalkfor better color support detection (f598725)Features
v13.1.4Compare Source
v13.1.3Compare Source
v13.1.2Compare Source
Bug Fixes
v13.1.1Compare Source
Bug Fixes
--stashwhen using the--diffoption (99390c3)v13.1.0Compare Source
Features
v13.0.4Compare Source
Bug Fixes
v13.0.3Compare Source
Bug Fixes
v13.0.2Compare Source
Bug Fixes
--diffand--diff-filteroptions when checking task modifications (1a5a66a)v13.0.1Compare Source
Bug Fixes
process.killwhen killing tasks on failure (f2c6bdd)Performance Improvements
EventsEmitterinstead ofsetIntervalfor killing tasks on failure (c508b46)v13.0.0Compare Source
Bug Fixes
execa@^6.1.0(659c85c)yaml@^2.1.1(2750a3d)Features
BREAKING CHANGES
lint-stagedwill no longer support Node.js 12, which is EOL since 30 April 2022v12.5.0Compare Source
Bug Fixes
--config <path>(641d1c2)--diffoption (d4da24d)Features
--diff-filteroption for overriding list of (staged) files (753ef72)--diffoption for overriding list of (staged) files (35fcce9)v12.4.3Compare Source
Bug Fixes
v12.4.2Compare Source
Bug Fixes
v12.4.1Compare Source
Bug Fixes
v12.4.0Compare Source
Bug Fixes
parseGitZOutput(a118817)Features
--max-arg-lengthcli option (e8291b0)v12.3.8Compare Source
Bug Fixes
v12.3.7Compare Source
Bug Fixes
--silentandFORCE_COLORsettings (d327873)v12.3.6Compare Source
Bug Fixes
v12.3.5Compare Source
Bug Fixes
v12.3.4Compare Source
Bug Fixes
package.jsonto exports (#1059) (3395150)v12.3.3Compare Source
Bug Fixes
v12.3.2Compare Source
Bug Fixes
v12.3.1Compare Source
Bug Fixes
v12.3.0Compare Source
Features
--cwdoption for overriding task directory (62b5b83)v12.2.2Compare Source
Bug Fixes
cwdfirst (4afcda5)v12.2.1Compare Source
Bug Fixes
v12.2.0Compare Source
Bug Fixes
Features
v12.1.7Compare Source
Bug Fixes
v12.1.6Compare Source
Bug Fixes
v12.1.5Compare Source
Bug Fixes
--debugoption enables debug mode (5cceeb6)v12.1.4Compare Source
Bug Fixes
v12.1.3Compare Source
Bug Fixes
v12.1.2Compare Source
Bug Fixes
v12.1.1Compare Source
Bug Fixes
v12.1.0Compare Source
Features
.jsconfig file with ESM syntax (410c3ba)cosmiconfigwithlilconfig+yamlto reduce dependencies (e7f9fa0).mjsconfig (8d3b176)v12.0.3Compare Source
Bug Fixes
enquirer(e01585f)v12.0.2Compare Source
Bug Fixes
npmversion requirement (#1047) (e50d6d4)v12.0.1Compare Source
Bug Fixes
v12.0.0Compare Source
Features
BREAKING CHANGES
requires Node.js version
^12.20.0 || ^14.13.1 || >=16.0.0.To update your Node.js integration, please use:
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.
This PR was generated by Mend Renovate. View the repository job log.