GeezerVison is showing github.com — [skip ci] chore(deps-dev): bump lint-staged from 15.2.7 to 15.5.1 by dependabot[bot] · Pull Request #239 · someengineering/docs.fix.security
Conversation
Bumps lint-staged from 15.2.7 to 15.5.1.
Release notes
Sourced from lint-staged's releases.
v15.5.1
Patch Changes
v15.5.0
Minor Changes
-
#1526 630af5f Thanks @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
- Stage
file.js with only double quotes " changed to '
- Run
git commit -am "I don't like double quotes"
- Lint-staged runs
prettier --write file.js, converting all the ' back to "
- Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
- Commit was not done, original state is restored and single quotes
' are staged
Now
- Stage
file.js with only double-quotes " changed to '
- Run
git commit -am "I don't like double quotes"
- Lint-staged runs
prettier --write file.js, converting all the ' back to "
- Because there are now no changes, lint-staged fails and cancels the commit
- Commit was not done, and there are no staged changes
v15.4.3
Patch Changes
- #1512
cbfed1d Thanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.
v15.4.2
Patch Changes
- #1509
8827ebf Thanks @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.1
Patch Changes
v15.4.0
... (truncated)
Changelog
Sourced from lint-staged's changelog.
15.5.1
Patch Changes
15.5.0
Minor Changes
-
#1526 630af5f Thanks @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
- Stage
file.js with only double quotes " changed to '
- Run
git commit -am "I don't like double quotes"
- Lint-staged runs
prettier --write file.js, converting all the ' back to "
- Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
- Commit was not done, original state is restored and single quotes
' are staged
Now
- Stage
file.js with only double-quotes " changed to '
- Run
git commit -am "I don't like double quotes"
- Lint-staged runs
prettier --write file.js, converting all the ' back to "
- Because there are now no changes, lint-staged fails and cancels the commit
- Commit was not done, and there are no staged changes
15.4.3
Patch Changes
- #1512
cbfed1d Thanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.
15.4.2
Patch Changes
- #1509
8827ebf Thanks @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.
15.4.1
... (truncated)
Commits
6a73e5b chore(changeset): release
cf7f1a5 Merge pull request #1533 from lint-staged/fix-submodules-filter
6acd5bf ci: bump Cygwin action v5
5d53534 fix: handle uninitialized submodules when listing staged files
ccf8fa5 docs(package): fix repository url and bin; add homepage and bugs urls (#1532)
7e6abe4 chore(changeset): release
0ebfa69 build(deps): update dependencies
630af5f feat: do not reset to original state when preventing empty commit
7b8be70 chore: update default branch references from "master" to "main"
362a78d docs: add workaround for tsc ignoring tsconfig.json issue to README FAQ (#1523)
- 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 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)
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This branch has not been deployed
No deployments
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.