Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 27, 2023

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@types/got (source) 8.3.58.3.6 age confidence devDependencies patch
@types/node (source) 10.17.1710.17.60 age confidence devDependencies patch
lint-staged 15.1.015.5.2 age confidence devDependencies minor
node (source) 20.9.020.20.0 age confidence volta minor
typedoc (source) 0.25.00.28.16 age confidence devDependencies minor
typescript (source) 3.6.33.9.10 age confidence devDependencies minor
yarn 1.22.211.22.22 age confidence volta patch

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.

nodejs/node (node)

v20.20.0: 2026-01-13, Version 20.20.0 'Iron' (LTS), @​marco-ippolito

Compare Source

This is a security release.

Notable Changes

lib:

Commits

v20.19.6: 2025-11-25, Version 20.19.6 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

v20.19.5: 2025-09-03, Version 20.19.5 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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/all-minor-patch branch from 97f2040 to 59ac2d3 Compare December 4, 2023 17:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from caa51ed to 1402dc2 Compare January 2, 2024 05:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from acef5cd to 12e3c7d Compare January 10, 2024 05:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e545bb9 to 29dd03a Compare February 6, 2024 05:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from bfef96a to 41d25a1 Compare February 15, 2024 05:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 41d25a1 to 024568d Compare February 26, 2024 04:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 4a2c707 to 542e14d Compare March 10, 2024 14:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 542e14d to 49c384c Compare March 12, 2024 03:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 49c384c to 34970b8 Compare March 27, 2024 02:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from d4399a4 to b0ef6ff Compare April 12, 2024 18:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 0f1a131 to 19ff1b8 Compare May 10, 2024 05:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 214bd6f to f47fe98 Compare May 29, 2024 02:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 4bcd0c3 to 76658e3 Compare June 13, 2024 23:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 21b3727 to e0f85b3 Compare June 28, 2024 05:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e0f85b3 to cc700f7 Compare July 9, 2024 11:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0dae44b to 678be2c Compare April 12, 2025 23:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e669096 to 2cc97b9 Compare April 26, 2025 11:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 7a9b663 to ee8bdc5 Compare May 10, 2025 11:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ee8bdc5 to 44f5109 Compare May 17, 2025 15:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 44f5109 to 79b80f0 Compare May 27, 2025 00:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 79b80f0 to 8e35b93 Compare June 29, 2025 00:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8e35b93 to 1bb4bef Compare July 6, 2025 08:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1bb4bef to c67c97e Compare July 20, 2025 04:03
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c67c97e to 90c0167 Compare August 3, 2025 19:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 90c0167 to a34776f Compare August 14, 2025 20:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 0e1aac0 to 59ef13d Compare August 25, 2025 03:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b626a2e to 81ae385 Compare September 4, 2025 07:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 81ae385 to 651971c Compare September 15, 2025 03:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 651971c to 2d57b95 Compare September 26, 2025 07:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2d57b95 to ab4a1ba Compare October 11, 2025 11:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ab4a1ba to fabc19f Compare October 25, 2025 20:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fabc19f to b3aac8d Compare November 15, 2025 12:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 5ec2832 to f5ae0c8 Compare November 29, 2025 07:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f5ae0c8 to daba3ee Compare December 5, 2025 11:11
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from daba3ee to 59bb5b3 Compare January 1, 2026 03:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from caba5c4 to f40a59d Compare January 14, 2026 08:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f40a59d to 13a909b Compare February 3, 2026 23:37
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