apex-recipes
apex-recipes copied to clipboard
build(deps-dev): bump lint-staged from 15.5.1 to 16.1.0
Bumps lint-staged from 15.5.1 to 16.1.0.
Release notes
Sourced from lint-staged's releases.
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 [email protected].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"$@":# my-script.sh #!/bin/bashecho "Staged files: $@"
and
{ "*.js": "my-script.sh" }If you were using the shell option to avoid passing filenames to tasks, for example
bash -c 'tsc --noEmit', use the function syntax instead:export default { '*.ts': () => 'tsc --noEmit' }#1546
158d15cThanks@iiroj! - Validation for deprecated advanced configuration has been removed. The advanced configuration was removed in lint-staged version 9 and until now validation has failed if advanced configuration options were detected. Going forward the entire configuration will be treated with the same logic and if these advanced options are still present, they might be treated as valid globs for staged files instead.#1546
158d15cThanks@iiroj! - The lowest supported Node.js version is20.18. Please upgrade your Node.js version.Minor Changes
- #1401
27110efThanks@RohitLuthra19! - Added support for directly running functions on staged files. To configure a function task, use an object with a title and the task itself:
... (truncated)
Changelog
Sourced from lint-staged's changelog.
16.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 [email protected].16.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"$@":# my-script.sh #!/bin/bashecho "Staged files: $@"
and
{ "*.js": "my-script.sh" }If you were using the shell option to avoid passing filenames to tasks, for example
bash -c 'tsc --noEmit', use the function syntax instead:export default { '*.ts': () => 'tsc --noEmit' }#1546
158d15cThanks@iiroj! - Validation for deprecated advanced configuration has been removed. The advanced configuration was removed in lint-staged version 9 and until now validation has failed if advanced configuration options were detected. Going forward the entire configuration will be treated with the same logic and if these advanced options are still present, they might be treated as valid globs for staged files instead.#1546
158d15cThanks@iiroj! - The lowest supported Node.js version is20.18. Please upgrade your Node.js version.Minor Changes
... (truncated)
Commits
f92caaachore(changeset): releasee729daafeat: add "--no-revert" flag to disable reverting to original state in case o...c37dc38fix: lower minimum required Node.js version to 20.1748f778fbuild(deps): update dependenciesb27fa3ffeat: leave out symlinks from list of staged filesa941f2cdocs: add table of contents section to README.md (#1555)dad5490chore(changeset): release1c19e82build(deps): update dependencies and require Node.js 20.1808cf8f5docs: update README.md and bump nano-spawn as major change276dcc8refactor: simplify config validation- Additional commits viewable in compare view
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)