Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 1, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lint-staged 13.3.0 -> 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

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

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.

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 force-pushed the renovate/lint-staged-15.x branch from 5039d4a to d20eda2 Compare November 11, 2023 18:54
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from d20eda2 to 8d24e93 Compare December 3, 2023 20:39
Copy link

github-actions bot commented Dec 3, 2023

Visit the preview URL for this PR (updated for commit e12a4cb):

https://ent-ninsar-dev--pr192-renovate-lint-staged-1g7l0sn5.web.app

(expires Sat, 17 May 2025 12:18:36 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 459be81c3496ac31e0d1abe75517fb8af6c796be

@renovate renovate bot changed the title Update dependency lint-staged from v13.2.3 to v15 Update dependency lint-staged from v13.3.0 to v15 Dec 10, 2023
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from f71db2b to 2c0ca9b Compare December 11, 2023 02:10
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 3a10dee to f5397ae Compare January 3, 2024 00:03
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from f5397ae to 52e5b15 Compare January 18, 2024 06:29
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from d3729b8 to 25c0f69 Compare February 5, 2024 15:59
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 3c2631b to 09c77b7 Compare February 21, 2024 06:49
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 09c77b7 to 4d17801 Compare March 14, 2024 00:05
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 4d17801 to df1ca3c Compare April 4, 2024 03:48
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from df1ca3c to 9cc05b5 Compare April 12, 2024 03:53
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from d61241c to a926edc Compare May 7, 2024 08:10
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 0d64fdb to 5de79f2 Compare May 17, 2024 06:49
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 07c8034 to 4e8a05a Compare May 25, 2024 12:39
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from d219334 to 0a326d7 Compare May 31, 2024 03:06
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 4 times, most recently from 779c01c to c2d1786 Compare June 18, 2024 01:56
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from a6335ad to fddeb1a Compare July 12, 2024 01:28
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 8cd70f2 to dde57b3 Compare November 2, 2024 03:58
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 8bbd4a9 to 03b121c Compare November 15, 2024 04:58
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 69c031e to aa8130a Compare December 4, 2024 04:30
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 7623cfd to fd8115f Compare December 13, 2024 03:08
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from 48bef66 to cc932a2 Compare January 4, 2025 06:45
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 4 times, most recently from 89ef327 to 0a984a7 Compare January 16, 2025 18:59
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from a76f243 to 3ff8d6e Compare January 26, 2025 18:16
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 3ff8d6e to d096dd8 Compare February 6, 2025 06:32
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from d096dd8 to 7f71f62 Compare February 14, 2025 05:33
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 7f71f62 to 4d11df5 Compare February 25, 2025 05:31
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from dae2b1e to b56906b Compare March 18, 2025 04:34
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from ac728a5 to 1cf0db9 Compare April 11, 2025 17:34
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 1cf0db9 to 4ac8fff Compare April 22, 2025 05:27
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 4ac8fff to e12a4cb Compare May 10, 2025 12:16
Copy link

@renovate renovate bot changed the title Update dependency lint-staged from v13.3.0 to v15 Update dependency lint-staged from v13.3.0 to v15 - autoclosed May 10, 2025
@renovate renovate bot closed this May 10, 2025
@renovate renovate bot deleted the renovate/lint-staged-15.x branch May 10, 2025 20:48
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