Update lint-staged 13.0.3 → 14.0.1 (major) #175
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ lint-staged (13.0.3 → 14.0.1) · Repo
Release Notes
14.0.1
14.0.0
13.3.0
13.2.3
13.2.2
13.2.1
13.2.0
13.1.2
13.1.1
13.1.0
13.0.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 50 commits:
fix: fix reading config from stdin, introduced in v14.0.0 (#1317)feat: drop support for Node.js 14 (#1312)Merge pull request #1289 from okonet/updates-2023-04-20test: move mock to avoid name collision warning from jest-haste-mapfix: detect duplicate redundant braces in patterntest: skip test failing on Windows Node.js ~20.4.0refactor: replace "object-inspect" with built-in utilrefactor: use built-in truncation of Listr2refactor: reimplement "normalize-path"test: add debugrefactor: use top-level await in bintest: use GitHub Actions' temp dir if availabletest: replace `fs-extra` with native `node:fs/promises`chore(dependencies): update all dependencieschore: add script for listing required Node.js versions for dependencieschore(dependencies): update all dependenciesfeat(dependencies): update `[email protected]`feat!: drop support for Node.js 14 as it's EOL after 2023-04-30ci: run with Node.js 20fix(dependencies): update most dependenciesdocs: Fix configuration link (#1305)fix: the `--diff` option implies `--no-stash`fix(dependencies): update `[email protected]` (GHSA-f9xv-q969-pqx4) (#1290)fix: ignore "package.json" as config file when it's invalid JSON (#1281)feat: version bump only (#1275)ci: disable workflow for `next` branchdocs: update README.md (#1273)fix: use index-based stash references for improved MSYS2 compatibility (#1270)chore(dependencies): update all dependenciesfix(dependencies): replace `colorette` with `chalk` for better color support detectionchore(dependencies): update all dependenciesdocs: Clean up readme.me (#1263)fix: disable stash by default when using diff option (#1259)docs: fix broken links in readme (#1258)fix: allow re-enabling `--stash` when using the `--diff` optiondocs: add example to integrate with Next.js (#1256)docs: blog.johnnyreilly.com -> johnnyreilly.com (#1255)docs: Update link to a blog post (#1246)feat: expose cli entrance from "lint-staged/bin" (#1237)docs: add note about multiple configs files to READMEdocs: add note about git hook TTY to READMEtest: remove Windows snapshot workaroundtest: allow file protocol in git submodule testtest: update Jest snapshot formatci: install latest npm for older Node.js versionsci: bump GitHub Actions' versionsfix(deps): update all dependenciesfix(deps): update all dependenciesci: set GitHub Actions permissionschore(deps): bump colorette from 2.0.17 to 2.0.19 (#1177)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands