Skip to content

chore(deps): update dependency lint-staged to v15.5.1 #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lint-staged 15.3.0 -> 15.5.1 age adoption passing confidence

Release Notes

lint-staged/lint-staged (lint-staged)

v15.5.1

Compare Source

Patch Changes
  • #​1533 5d53534 Thanks @​iiroj! - Improve listing of staged files so that lint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:

    ✖ Failed to get staged files!
    

v15.5.0

Compare Source

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
  1. Stage file.js with only double quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails, cancels the commit, and resets back to the original state
  5. Commit was not done, original state is restored and single quotes ' are staged
Now
  1. Stage file.js with only double-quotes " changed to '
  2. Run git commit -am "I don't like double quotes"
  3. Lint-staged runs prettier --write file.js, converting all the ' back to "
  4. Because there are now no changes, lint-staged fails and cancels the commit
  5. Commit was not done, and there are no staged changes

v15.4.3

Compare Source

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

Compare Source

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

Compare Source

Patch Changes

v15.4.0

Compare Source

Minor Changes
  • #​1500 a8ec1dd Thanks @​iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:

    /**
     * @​filename: lint-staged.config.js
     * @​type {import('lint-staged').Configuration}
     */
    export default {
      '*': 'prettier --write',
    }

    It's also possible to use the .ts file extension for the configuration if your Node.js version supports it. The --experimental-strip-types flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.

    export NODE_OPTIONS="--experimental-strip-types"
    
    npx lint-staged --config lint-staged.config.ts
Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.4.0 chore(deps): update dependency lint-staged to v15.4.1 Jan 16, 2025
@renovate renovate bot force-pushed the renovate/lint-staged-15.x-lockfile branch from aa277b9 to 10b3826 Compare January 16, 2025 20:55
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.4.1 chore(deps): update dependency lint-staged to v15.4.2 Jan 23, 2025
@renovate renovate bot force-pushed the renovate/lint-staged-15.x-lockfile branch 2 times, most recently from a443472 to eea6fe8 Compare January 26, 2025 17:42
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.4.2 chore(deps): update dependency lint-staged to v15.4.3 Jan 26, 2025
@renovate renovate bot force-pushed the renovate/lint-staged-15.x-lockfile branch from eea6fe8 to ee81f2c Compare January 30, 2025 17:11
@renovate renovate bot force-pushed the renovate/lint-staged-15.x-lockfile branch 2 times, most recently from c56bd39 to 6732528 Compare February 12, 2025 13:02
@renovate renovate bot force-pushed the renovate/lint-staged-15.x-lockfile branch 2 times, most recently from 8606345 to a81209d Compare March 12, 2025 19:51
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.4.3 chore(deps): update dependency lint-staged to v15.5.0 Mar 12, 2025
@renovate renovate bot force-pushed the renovate/lint-staged-15.x-lockfile branch from a81209d to f78526b Compare March 13, 2025 15:37
@renovate renovate bot force-pushed the renovate/lint-staged-15.x-lockfile branch from f78526b to 6915896 Compare April 1, 2025 10:41
@renovate renovate bot force-pushed the renovate/lint-staged-15.x-lockfile branch from 6915896 to fad141c Compare April 11, 2025 19:44
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.5.0 chore(deps): update dependency lint-staged to v15.5.1 Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants