Skip to content
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

chore(deps): update dependency lint-staged to v15.4.3 #625

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lint-staged 15.2.1 -> 15.4.3 age adoption passing confidence

Release Notes

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

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.

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 is behind base branch, 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.2.2 chore(deps): update dependency lint-staged to v15.2.4 May 21, 2024
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from ae9e89b to 7dc5cef Compare May 21, 2024 23:10
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.2.4 chore(deps): update dependency lint-staged to v15.2.5 May 25, 2024
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 7dc5cef to d9f1464 Compare May 25, 2024 13:06
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.2.5 chore(deps): update dependency lint-staged to v15.2.6 Jun 11, 2024
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from d9f1464 to 5034702 Compare June 11, 2024 19:11
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.2.6 chore(deps): update dependency lint-staged to v15.2.7 Jun 12, 2024
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 5034702 to b04d001 Compare June 12, 2024 18:49
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from b04d001 to 061f10a Compare August 3, 2024 10:18
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.2.7 chore(deps): update dependency lint-staged to v15.2.8 Aug 3, 2024
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 061f10a to a7a5270 Compare August 13, 2024 06:14
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.2.8 chore(deps): update dependency lint-staged to v15.2.9 Aug 13, 2024
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.2.9 chore(deps): update dependency lint-staged to v15.2.10 Sep 1, 2024
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from a7a5270 to 59bbd1c Compare September 1, 2024 16:01
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.2.10 chore(deps): update dependency lint-staged to v15.2.11 Dec 10, 2024
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 59bbd1c to 22f8658 Compare December 26, 2024 15:48
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.2.11 chore(deps): update dependency lint-staged to v15.3.0 Dec 28, 2024
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch from 22f8658 to 56886ef Compare December 28, 2024 12:36
@renovate renovate bot changed the title chore(deps): update dependency lint-staged to v15.3.0 chore(deps): update dependency lint-staged to v15.4.0 Jan 16, 2025
@renovate renovate bot force-pushed the renovate/lint-staged-15.x branch 2 times, most recently from a4ec1f5 to 8a9f056 Compare January 16, 2025 21:56
@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 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 branch from 8a9f056 to e368396 Compare January 23, 2025 13:10
@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 branch from e368396 to d1b0337 Compare January 26, 2025 16:49
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.

1 participant