Skip to content

chore(deps): update dependency lint-staged to v15 - #1207

Open
renovate[bot] wants to merge 1 commit into
chore/renovateBaseBranchfrom
renovate/lint-staged-15.x
Open

renovate[bot] wants to merge 1 commit into
chore/renovateBaseBranchfrom
renovate/lint-staged-15.x

Conversation

@renovate

@renovate renovate Bot commented Dec 1, 2023 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lint-staged 13.0.3 → 15.5.2 age adoption passing confidence

Release Notes

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

v15.5.2

Compare Source

Patch Changes

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

v15.3.0

Compare Source

Minor Changes
  • #​1495 e69da9e Thanks @​iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.

  • #​1493 fa0fe98 Thanks @​iiroj! - Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

    For example:

    % npx lint-staged
    ✔ Backed up original state in git stash (20addf8)
    ✔ Running tasks for staged files...
    ✔ Applying modifications from tasks...
    ✔ Cleaning up temporary files...
    

    where the backup can be seen with git show 20addf8, or git stash list:

    % git stash list
    stash@{0}: lint-staged automatic backup (20addf8)
    

v15.2.11

Compare Source

Patch Changes
  • #​1484 bcfe309 Thanks @​wormsik! - Escape paths containing spaces when using the "shell" option.

  • #​1487 7dd8caa Thanks @​iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

v15.2.10

Compare Source

Patch Changes

v15.2.9

Compare Source

Patch Changes
  • #​1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Compare Source

Patch Changes
  • f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

    The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

v15.2.7

Compare Source

Patch Changes
  • #​1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

v15.2.6

Compare Source

Patch Changes
  • #​1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

v15.2.5

Compare Source

Patch Changes
  • #​1424 31a1f95 Thanks @​iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.

  • #​1423 91abea0 Thanks @​iiroj! - Improve error logging when failing to read or parse a configuration file

  • #​1424 ee43f15 Thanks @​iiroj! - Upgrade micromatch@​4.0.7

v15.2.4

Compare Source

Patch Changes
  • 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies

v15.2.2

Compare Source

Patch Changes
  • #​1391 fdcdad4 Thanks @​iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.

v15.2.1

Compare Source

Patch Changes
  • #​1484 bcfe309 Thanks @​wormsik! - Escape paths containing spaces when using the "shell" option.

  • #​1487 7dd8caa Thanks @​iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

v15.2.0

Compare Source

Minor Changes
  • #​1371 f3378be Thanks @​iiroj! - Using the --no-stash flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag --no-hide-partially-staged that is automatically enabled when --no-stash is used.
Patch Changes
  • #​1362 17bc480 Thanks @​antonk52! - update lilconfig@​3.0.0

  • #​1368 7c55ca9 Thanks @​iiroj! - Update most dependencies

  • #​1368 777d4e9 Thanks @​iiroj! - To improve performance, only use lilconfig when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.

  • #​1373 85eb0dd Thanks @​iiroj! - When determining git directory, use fs.realpath() only for symlinks. It looks like fs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.

v15.1.0

Compare Source

Minor Changes
Patch Changes

v15.0.2

Compare Source

Patch Changes
  • #​1339 8e82364 Thanks @​iiroj! - Update dependencies, including listr2@​7.0.2 to fix an upstream issue affecting lint-staged.

v15.0.1

Compare Source

Patch Changes
  • #​1217 d2e6f8b Thanks @​louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.

v15.0.0

Compare Source

Major Changes
  • #​1322 66b93aa Thanks @​iiroj! - Require at least Node.js 18.12.0

    This release drops support for Node.js 16, which is EOL after 2023-09-11.
    Please upgrade your Node.js to the latest version.

    Additionally, all dependencies have been updated to their latest versions.

v14.0.1

Compare Source

Bug Fixes
  • fix reading config from stdin, introduced in v14.0.0 (#​1317) (fc3bfea)

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • Please upgrade your Node.js version to at least 16.14.0.

v13.3.0

Compare Source

Bug Fixes
  • dependencies: update most dependencies (7443870)
  • detect duplicate redundant braces in pattern (d895aa8)
Features
  • dependencies: update listr2@6.6.0 (09844ca)

v13.2.3

Compare Source

Bug Fixes
  • the --diff option implies --no-stash (66a716d)

v13.2.2

Compare Source

Bug Fixes

v13.2.1

Compare Source

Bug Fixes
  • ignore "package.json" as config file when it's invalid JSON (#​1281) (e7ed6f7)

v13.2.0

Compare Source

Bug Fixes
  • dependencies: replace colorette with chalk for better color support detection (f598725)
  • use index-based stash references for improved MSYS2 compatibility (#​1270) (60fcd99)
Features

v13.1.4

Compare Source

v13.1.3

Compare Source

v13.1.2

Compare Source

Bug Fixes

v13.1.1

Compare Source

Bug Fixes
  • allow re-enabling --stash when using the --diff option (99390c3)

v13.1.0

Compare Source

Features

v13.0.4

Compare Source

Bug Fixes
  • deps: update all dependencies (336f3b5)
  • deps: update all dependencies (ec995e5)

Configuration

📅 Schedule: (in timezone Europe/Paris)

  • Branch creation
    • "after 4pm on friday,before 9am on monday,every weekend"
  • 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 force-pushed the renovate/lint-staged-15.x branch 5 times, most recently from c17cb37 to e3fc3e6 Compare December 9, 2023 21:56
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch 5 times, most recently from 8e150d1 to ec5fd92 Compare December 15, 2023 22:16
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch 4 times, most recently from 61f6e70 to ba65fb3 Compare December 17, 2023 12:46
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from ba65fb3 to 785a8de Compare December 29, 2023 18:09
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 52b8b51 to 65c0307 Compare February 9, 2024 15:08
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 74db1c5 to 6f9a836 Compare March 8, 2024 16:34
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 6f9a836 to e1711e6 Compare April 14, 2024 07:07
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 06915ca to dc4ffae Compare May 25, 2024 12:20
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from dc4ffae to 747efec Compare June 1, 2024 18:04
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 747efec to da3d85f Compare June 14, 2024 14:44
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from da3d85f to 7ebd413 Compare July 21, 2024 08:05
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 7ebd413 to f31423b Compare August 3, 2024 08:29
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from f31423b to 2fc9ddc Compare August 16, 2024 15:22
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 2fc9ddc to 695397a Compare September 1, 2024 16:19
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 695397a to 14439b9 Compare December 13, 2024 16:00
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 14439b9 to 56e3ba6 Compare December 28, 2024 11:07
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 3d8aaf7 to 3082ef7 Compare January 24, 2025 15:25
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 3082ef7 to b65efb5 Compare January 26, 2025 18:41
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from b65efb5 to 3abf7fb Compare March 14, 2025 17:30
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 3abf7fb to 1ccb069 Compare April 11, 2025 17:25
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 1ccb069 to 4bad8af Compare May 9, 2025 14:31
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 4bad8af to 507306c Compare August 10, 2025 15:34
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 507306c to df055a7 Compare August 22, 2025 18:55
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from df055a7 to fdd0516 Compare August 31, 2025 12:00
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from fdd0516 to c582548 Compare September 26, 2025 15:28
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from c582548 to 77e3c28 Compare October 24, 2025 21:10
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 77e3c28 to 21fbe6d Compare November 14, 2025 21:10
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 21fbe6d to 479ea34 Compare December 5, 2025 15:26
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 479ea34 to 5f24a9f Compare January 23, 2026 15:39
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 5f24a9f to 921ec89 Compare February 6, 2026 19:15
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 921ec89 to 97a0b72 Compare February 20, 2026 16:03
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 97a0b72 to e6bc95b Compare March 6, 2026 19:13
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from e6bc95b to 1f0909d Compare April 3, 2026 14:37
@codacy-production

codacy-production Bot commented Apr 3, 2026 •

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

TIP This summary will be updated as you push new changes.

@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 1f0909d to 6ec2fe5 Compare May 15, 2026 15:01
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 6ec2fe5 to f518d47 Compare August 14, 2026 21:47
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from f518d47 to 998b93a Compare September 18, 2026 23:03
@renovate
renovate Bot force-pushed the renovate/lint-staged-15.x branch from 998b93a to 2401483 Compare October 2, 2026 15:48

This branch has not been deployed

No deployments
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