Skip to content

Update all (major) #75

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
Open

Update all (major) #75

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 20.14.2 -> 22.15.31 age adoption passing confidence
eslint-config-prettier 9.1.0 -> 10.1.5 age adoption passing confidence
lint-staged 15.2.5 -> 16.1.2 age adoption passing confidence
web-vitals 4.1.0 -> 5.0.3 age adoption passing confidence

Release Notes

prettier/eslint-config-prettier (eslint-config-prettier)

v10.1.5

Compare Source

Patch Changes

v10.1.4

Compare Source

Patch Changes

v10.1.3

Compare Source

Patch Changes

v10.1.2

Compare Source

Patch Changes

v10.1.1

Compare Source

Patch Changes
  • #​309 eb56a5e Thanks @​JounQin! - fix: separate the /flat entry for compatibility

    For flat config users, the previous "eslint-config-prettier" entry still works, but "eslint-config-prettier/flat" adds a new name property for config-inspector, we just can't add it for the default entry for compatibility.

    See also #​308

    // before
    import eslintConfigPrettier from "eslint-config-prettier";
    
    // after
    import eslintConfigPrettier from "eslint-config-prettier/flat";

v10.1.0

Compare Source

Minor Changes

v10.0.3

Compare Source

Patch Changes

v10.0.2

Compare Source

Patch Changes

v10.0.1

Compare Source

eslint-config-prettier

10.0.1

What's Changed

New Contributors

Full Changelog: prettier/eslint-config-prettier@v9.1.0...v10.0.1

v10.0.0

Compare Source

Major Changes
lint-staged/lint-staged (lint-staged)

v16.1.2

Compare Source

Patch Changes
  • #​1570 a7c0c88 Thanks @​ItsNickBarry! - When using --diff-filter with the D option to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error from git add like fatal: pathspec 'deleted-file' did not match any files.

  • 38f942e Thanks @​iiroj! - Removed an extraneous log entry that printed shouldHidePArtiallyStagedFiles to console output.

v16.1.1

Compare Source

Patch Changes
  • #​1565 3686977 Thanks @​iiroj! - Lint-staged now explicitly warns about potential data loss when using --no-stash.

  • #​1571 02299a9 Thanks @​iiroj! - Function tasks (introduced in v16.0.0) only received the staged files matching the conpmnfigured glob, instead of all staged files.

  • #​1563 bc61c74 Thanks @​iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the --no-stash option. This happened because --no-stash implied --no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.

    The previous (incorrect) behavior can still be achieved by using both options --no-stash --no-hide-partially-staged at the same time.

v16.1.0

Compare Source

Minor Changes
  • #​1536 e729daa Thanks @​iiroj! - A new flag --no-revert has been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, lint-staged will clear all task modifications and revert to the original state.

  • #​1550 b27fa3f Thanks @​iiroj! - Lint-staged now ignores symlinks and leaves them out from the list of staged files.

Patch Changes

v16.0.0

Compare Source

Major Changes
  • #​1546 158d15c Thanks @​iiroj! - Processes are spawned using nano-spawn instead of execa. If you are using Node.js scripts as tasks, you might need to explicitly run them with node, especially when using Windows:

    {
      "*.js": "node my-js-linter.js"
    }
  • #​1546 158d15c Thanks @​iiroj! - The --shell flag has been removed and lint-staged no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via "$@​":

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.
GoogleChrome/web-vitals (web-vitals)

v5.0.3

Compare Source

  • Remove visibilitychange event listeners when no longer required (#​627)

v5.0.2

Compare Source

  • Handle layout shifts with no sources (#​623)

v5.0.1

Compare Source

  • Fix missing FCP and LCP for prerendered pages (#​621)

v5.0.0

Compare Source

[!NOTE]
See the upgrading to v5 guide for a complete list of all API changes in version 5.

  • [BREAKING] Remove the deprecated onFID() function (#​519)
  • [BREAKING] Change browser support policy to Baseline Widely available (#​525)
  • [BREAKING] Sort the classes that appear in attribution selectors to reduce cardinality (#​518)
  • Extend INP attribution with extra LoAF information: longest script and buckets (#​592)
  • Add support for generating custom targets in the attribution build (#​585)
  • Support multiple calls to onINP() with different config options (#​583)
  • Use visibility-state performance entries (#​612)
  • Ensure idle callbacks don't run twice (#​541) and (#​548)
  • Cap nextPaintTime at processingStart (#​540) and (#​546)
  • Cap INP breakdowns to INP duration (#​528)
  • Cap LCP load duration to LCP time (#​527)

v4.2.4

Compare Source

  • Fix memory leak in registering new event listeners on every keydown and click (#​554)

v4.2.3

Compare Source

  • Fix missing LoAF entries in INP attribution (#​512)

v4.2.2

Compare Source

  • Fix interaction count after bfcache restore (#​505)

v4.2.1

Compare Source

  • Fix compatibility issues with TypeScript v5.5 (#​497)

v4.2.0

Compare Source

  • Refactor INP attribution code to fix errors on Windows 10 (#​495)

v4.1.1

Compare Source

  • Fix pending LoAF cleanup logic (#​493)

Configuration

📅 Schedule: Branch creation - "on the first day of the month" (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/major-all branch 3 times, most recently from 9a23afc to f9d5aae Compare January 3, 2025 09:29
@renovate renovate bot force-pushed the renovate/major-all branch from f9d5aae to fd4347a Compare January 13, 2025 16:43
@renovate renovate bot changed the title Update dependency @types/node to v22 Update all (major) Jan 13, 2025
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 94d108e to 1a4411c Compare January 16, 2025 01:38
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from bfe013c to f642943 Compare January 28, 2025 05:07
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from b35845c to ad15ba2 Compare February 4, 2025 00:42
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 1dc40f7 to 9686a09 Compare February 13, 2025 23:25
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from ac8dca9 to 4476033 Compare February 26, 2025 14:38
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from 0150405 to b104d53 Compare March 7, 2025 10:07
@renovate renovate bot force-pushed the renovate/major-all branch from b104d53 to e70d67f Compare March 8, 2025 10:42
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 646df1e to 6544799 Compare March 27, 2025 06:28
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from 0d0975b to c663207 Compare April 2, 2025 21:43
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from bd3efc4 to 3401767 Compare April 28, 2025 07:48
@renovate renovate bot force-pushed the renovate/major-all branch 11 times, most recently from a69de82 to 1c286e5 Compare May 10, 2025 22:14
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 1a72d5f to a448c4d Compare May 19, 2025 03:14
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from b22f9ea to 310204e Compare May 27, 2025 20:08
@renovate renovate bot force-pushed the renovate/major-all branch 5 times, most recently from 97b676d to 6d19661 Compare May 30, 2025 19:33
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 55e7035 to 657780d Compare June 11, 2025 19:50
@renovate renovate bot force-pushed the renovate/major-all branch from 657780d to 36f2f1c Compare June 14, 2025 09:04
@renovate renovate bot force-pushed the renovate/major-all branch from 36f2f1c to 5fdc225 Compare June 15, 2025 14:12
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.

0 participants