Skip to content

(npm): Bump lint-staged from 16.1.0 to 16.1.1#1647

Merged
mergify[bot] merged 1 commit intomainfrom
dependabot/npm_and_yarn/lint-staged-16.1.1
Jun 14, 2025
Merged

(npm): Bump lint-staged from 16.1.0 to 16.1.1#1647
mergify[bot] merged 1 commit intomainfrom
dependabot/npm_and_yarn/lint-staged-16.1.1

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 14, 2025

Bumps lint-staged from 16.1.0 to 16.1.1.

Release notes

Sourced from lint-staged's releases.

v16.1.1

Patch Changes

  • #1565 3686977 Thanks @​iiroj! - Lint-staged now explicitly warns about potential data loss when using --no-stash.

  • #1571 02299a9 Thanks @​iiroj! - Function tasks (introduced in v16.0.0) only received the staged files matching the conpmnfigured glob, instead of all staged files.

  • #1563 bc61c74 Thanks @​iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the --no-stash option. This happened because --no-stash implied --no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.

    The previous (incorrect) behavior can still be achieved by using both options --no-stash --no-hide-partially-staged at the same time.

Changelog

Sourced from lint-staged's changelog.

16.1.1

Patch Changes

  • #1565 3686977 Thanks @​iiroj! - Lint-staged now explicitly warns about potential data loss when using --no-stash.

  • #1571 02299a9 Thanks @​iiroj! - Function tasks (introduced in v16.0.0) only received the staged files matching the conpmnfigured glob, instead of all staged files.

  • #1563 bc61c74 Thanks @​iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the --no-stash option. This happened because --no-stash implied --no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.

    The previous (incorrect) behavior can still be achieved by using both options --no-stash --no-hide-partially-staged at the same time.

Commits
  • 8420429 chore(changeset): release
  • e049fd7 fix: print path to unstaged file patch on error when using --no-stash
  • 92e8a68 build(deps): update devDependencies
  • 99f915c refactor: carry staged files' git status internally
  • 327837b refactor: replace deprecated substr with slice
  • f01915c refactor: create error with cause
  • f9a59e2 chore: fix typos
  • 02299a9 fix: function tasks receive only staged files matching glob
  • c5196c5 build(deps): update dependencies
  • 3686977 fix: warn about potential data loss when using "--no-stash"
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [lint-staged](https://github.com/lint-staged/lint-staged) from 16.1.0 to 16.1.1.
- [Release notes](https://github.com/lint-staged/lint-staged/releases)
- [Changelog](https://github.com/lint-staged/lint-staged/blob/main/CHANGELOG.md)
- [Commits](lint-staged/lint-staged@v16.1.0...v16.1.1)

---
updated-dependencies:
- dependency-name: lint-staged
  dependency-version: 16.1.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/lint-staged-16.1.1 branch from dc0dffd to d9f0b6b Compare June 14, 2025 12:46
@mergify mergify bot merged commit 50ac27d into main Jun 14, 2025
10 checks passed
@mergify mergify bot deleted the dependabot/npm_and_yarn/lint-staged-16.1.1 branch June 14, 2025 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants