Bumpslint-staged from 13.2.2 to 16.2.3.
Release notes
Sourced fromlint-staged's releases.
v16.2.3
Patch Changes
- #1669
27cd541 Thanks@iiroj! - When using--fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to makelint-staged fail.
v16.2.2
Patch Changes
#1667699f95d Thanks@iiroj! - The backup stash will not be dropped when using--fail-on-changes and there are errors. When reverting to original state is disabled (via--no-revert or--fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.
Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:
% npx lint-staged --fail-on-changes✔ Backed up original statein git stash (c18d55a3)✔ Running tasksfor staged files...✖ Tasks modified files and --fail-on-changes was used!↓ Cleaning up temporary files...✖ lint-staged failed because --fail-on-changes was used.Any lost modifications can be restored from a git stash:> git stash list --format="%h %s"c18d55a3 On main: lint-staged automatic backup> git apply --index c18d55a3
v16.2.1
Patch Changes
#16648277b3b Thanks@iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions isreadonly string[] and can't be mutated. Thanks@outslept!
export default {--- "*": (files: string[]) => void console.log('staged files', files)+++ "*": (files: readonly string[]) => void console.log('staged files', files)}#165470b9af3 Thanks@iiroj! - This version has been published from GitHub Actions usingTrusted Publishing for npm packages.
#16594996817 Thanks@iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there arepackage.json files in the working directory. This situation might happen when runninglint-staged for a single package in a monorepo.
#16547021f0a Thanks@iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates tolint-staged. This was changed in16.2.0 after the vulnerability issues withchalk anddebug, which were also removed in the same version.
Given the recent vulnerabilities in thenpm ecosystem, it's best to be very careful when updating dependencies.
v16.2.0
Minor Changes
... (truncated)
Changelog
Sourced fromlint-staged's changelog.
16.2.3
Patch Changes
- #1669
27cd541 Thanks@iiroj! - When using--fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to makelint-staged fail.
16.2.2
Patch Changes
#1667699f95d Thanks@iiroj! - The backup stash will not be dropped when using--fail-on-changes and there are errors. When reverting to original state is disabled (via--no-revert or--fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.
Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:
% npx lint-staged --fail-on-changes✔ Backed up original statein git stash (c18d55a3)✔ Running tasksfor staged files...✖ Tasks modified files and --fail-on-changes was used!↓ Cleaning up temporary files...✖ lint-staged failed because --fail-on-changes was used.Any lost modifications can be restored from a git stash:> git stash list --format="%h %s"c18d55a3 On main: lint-staged automatic backup> git apply --index c18d55a3
16.2.1
Patch Changes
#16648277b3b Thanks@iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions isreadonly string[] and can't be mutated. Thanks@outslept!
export default {--- "*": (files: string[]) => void console.log('staged files', files)+++ "*": (files: readonly string[]) => void console.log('staged files', files)}#165470b9af3 Thanks@iiroj! - This version has been published from GitHub Actions usingTrusted Publishing for npm packages.
#16594996817 Thanks@iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there arepackage.json files in the working directory. This situation might happen when runninglint-staged for a single package in a monorepo.
#16547021f0a Thanks@iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates tolint-staged. This was changed in16.2.0 after the vulnerability issues withchalk anddebug, which were also removed in the same version.
Given the recent vulnerabilities in thenpm ecosystem, it's best to be very careful when updating dependencies.
... (truncated)
Commits
bdcd03a chore(changeset): release27cd541 fix: do not count hidden (partially) unstaged changes when using `--fail-on-c...ab2f42e fix: emit correct value to debug logs3fc5832 refactor: make general error messages more clear they originate from lint-staged409d79a chore(changeset): release7edaee9 docs: fix typo in changeset699f95d fix: backup stash example uses real hash if available47d01a9 fix: print backup stash example when failing to--fail-on-changes325dc03 fix: restore unstaged changes on errors when--fail-on-errors or `--no-reve...53bb27b fix: do not drop backup stash when errors and--fail-on-changes was used- Additional commits viewable incompare view
Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for lint-staged since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting@dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR@dependabot recreate will recreate this PR, overwriting any edits that have been made to it@dependabot merge will merge this PR after your CI passes on it@dependabot squash and merge will squash and merge this PR after your CI passes on it@dependabot cancel merge will cancel a previously requested merge and block automerging@dependabot reopen will reopen this PR if it is closed@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumpslint-staged from 13.2.2 to 16.2.3.
Release notes
Sourced fromlint-staged's releases.
... (truncated)
Changelog
Sourced fromlint-staged's changelog.
... (truncated)
Commits
bdcd03achore(changeset): release27cd541fix: do not count hidden (partially) unstaged changes when using `--fail-on-c...ab2f42efix: emit correct value to debug logs3fc5832refactor: make general error messages more clear they originate from lint-staged409d79achore(changeset): release7edaee9docs: fix typo in changeset699f95dfix: backup stash example uses real hash if available47d01a9fix: print backup stash example when failing to--fail-on-changes325dc03fix: restore unstaged changes on errors when--fail-on-errorsor `--no-reve...53bb27bfix: do not drop backup stash when errors and--fail-on-changeswas usedMaintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for lint-staged since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)