Update lint-staged 15.2.10 → 15.2.11 (patch) #621
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ lint-staged (15.2.10 → 15.2.11) · Repo · Changelog
Release Notes
15.2.11
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 11 commits:
Merge pull request #1485 from lint-staged/changeset-release/master
chore(changeset): release
Merge pull request #1487 from lint-staged/submodule-test
fix: do not treat submodule root paths as staged files
test: assert committing changes to submodule works from the repo
Merge pull request #1486 from lint-staged/deps-2024-12-10
build(deps): update dependencies
Merge pull request #1484 from wormsik/path-space-fix
docs: extract function and link to execa's implementation
fix: escape paths with spaces when using "shell" option
ci: add Node v23 to the CI PR test matrix (#1477)
Release Notes
4.4.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
4.4.0
fix inefficient .enable() regex and .enabled() test
Commits
See the full diff on Github. The new version differs by 3 commits:
Release v10.4.0
Update to draft release of Unicode v16.0.0
Cross-link emoji-regex-xs (#113)
Release Notes
3.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
3.1.3
do not duplicate github actions runs, run on push to master or full pull requests
update reusable github actions steps
use node v22 by default and move node v20 to old node tests
run ci checks on pull request
extract coveralls to only run on push to main
fix linter
modern setup node step
ignore postinstall scripts for CI jobs that does not require biome
Comment why we explicitly we need uvu tests
run old node tests on windows too
test for default js loaders using dynamic import
run npm audit fix
fix: .mjs configuration file error
remove unused ts-expect-error
fix lint
Release Notes
8.2.5 (from changelog)
Does any of this look wrong? Please let us know.
Release Notes
2.6.1
2.6.0
2.5.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
2.6.1
fix: Default to literal block scalar if folded would overflow (fixes #585)
fix: Tighten regexp for JSON !!bool (#587)
fix: Do not strip :00 seconds from !!timestamp values (#578)
chore: Refresh lockfile
chore: Add .well-known/funding-manifest-urls
2.6.0
fix: Stringify a Document as a Document (fixes #576)
feat: Add stringKeys parse option (#581)
docs: Update Manifest logo (#582)
docs: Align logos using the restricted styling available for GitHub readmes
docs: Fix manifest.png reference
chore: Add sponsorship by Manifest
chore: Refresh lockfile
feat: Use a proper tag for !!merge << keys (#580)
2.5.1
chore: Simplify Babel config, inlining it Jest config
chore: Re-enable linting with type information
chore: Update to eslint 9, fix found issues
chore: Refresh lockfile (keeping rollup at 4.19.0 due to rollup/rollup#5633)
fix: Include range in flow sequence pair maps (fixes #573)
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