Skip to content

chore(deps): update external major (major) - #24

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate-major-external-major
Open

chore(deps): update external major (major)#24
renovate[bot] wants to merge 1 commit into
mainfrom
renovate-major-external-major

Conversation

@renovate

@renovate renovate Bot commented May 4, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@semantic-release/changelog 6.0.3 → 7.0.0 age confidence devDependencies major
@semantic-release/git 10.0.1 → 11.0.1 age confidence devDependencies major
actions/checkout v5 → v7 age confidence action major
actions/setup-node v6 → v7 age confidence action major
aws-actions/aws-secretsmanager-get-secrets v2 → v3 age confidence action major
aws-actions/configure-aws-credentials v5 → v6 age confidence action major
c8 10.1.3 → 12.0.0 age confidence devDependencies major
codecov/codecov-action v5 → v7 age confidence action major
lint-staged 16.4.0 → 17.2.0 age confidence devDependencies major 17.3.0
nock 13.5.6 → 14.0.16 age confidence devDependencies major 14.0.17
sinon (source) 21.1.2 → 22.1.0 age confidence devDependencies major

Release Notes

semantic-release/changelog (@​semantic-release/changelog)

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • @semantic-release/changelog is now a native ES
    Module. It has named exports for each plugin hook (verifyConditions,
    prepare)
  • the minimum required version of semantic-release to use
    @semantic-release/changelog is now
    v20.1.0
Other Notable Changes
  • Replaced xo with prettier with default configuration; following
    newly established convention
  • Replaced nyc with c8 for code coverage
  • Replaced lodash with lodash-es for proper esm support
Related Issue
semantic-release/git (@​semantic-release/git)

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

Features
BREAKING CHANGES
  • @semantic-release/git is now a native ES Module. It
    has named exports for each plugin hook (verifyConditions, prepare)
  • the minimum required version of semantic-release to use
    @semantic-release/git is now v20.1.0
Other Notable Changes
  • @semantic-release/error ^3 → ^4 (ESM-only)
  • aggregate-error ^3 → ^5 (ESM-only, uses native AggregateError)
  • execa ^5 → ^9 (ESM-only, named export)
  • p-reduce ^2 → ^3 (ESM-only)
  • Removed CJS-only devDeps: clear-module, file-url, fs-extra,
    get-stream, nyc
  • Added c8 for coverage; bumped ava, sinon, tempy,
    semantic-release, prettier
  • Engine: ^22.22.2 || >= 24.15;
  • Scripts: nyc → c8, added pretest, removed test:ci
Related Issue
actions/checkout (actions/checkout)

v7.0.1

Compare Source

v7.0.0

Compare Source

v7

Compare Source

v6.1.0

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v6

Compare Source

actions/setup-node (actions/setup-node)

v7.0.0

Compare Source

What's Changed
Enhancements:
Bug fixes:
Documentation updates:
Dependency update:
New Contributors

Full Changelog: actions/setup-node@v6...v7.0.0

v7

Compare Source

aws-actions/aws-secretsmanager-get-secrets (aws-actions/aws-secretsmanager-get-secrets)

v3.0.1

Compare Source

What's Changed

Full Changelog: aws-actions/aws-secretsmanager-get-secrets@v3...v3.0.1

v3.0.0

Compare Source

What's Changed
New Contributors

Full Changelog: aws-actions/aws-secretsmanager-get-secrets@v2...v3.0.0

v3

Compare Source

This tracks the latest v3.x.x version

aws-actions/configure-aws-credentials (aws-actions/configure-aws-credentials)

v6.2.3

Compare Source

v6.2.2

Compare Source

v6.2.2

Compare Source

Miscellaneous Chores

v6.2.1

Compare Source

Bug Fixes

v6.2.0

Compare Source

Features
Bug Fixes

v6.1.3

Compare Source

Bug Fixes
  • fix: allow kubelet token symlink in #​1805

v6.1.2

Compare Source

Bug Fixes

v6.1.1

Compare Source

What's Changed

Full Changelog: aws-actions/configure-aws-credentials@v6...v6.1.1

v6.1.0

Compare Source

Features

v6.0.0

Compare Source

⚠ BREAKING CHANGES
  • Update action to use node24 Note this requires GitHub action runner version v2.327.1 or later (#​1632) (a7a2c11)
Features
Bug Fixes
  • properly output aws-account-id and authenticated-arn when using role-chaining (#​1633) (7ceaf96)

v6

Compare Source

bcoe/c8 (c8)

v12.0.0

Compare Source

⚠ BREAKING CHANGES
  • yargs enforces a stricter range of Node versions ^20.19.0 || ^22.12.0 || >=23
Features

v11.0.0

Compare Source

⚠ BREAKING CHANGES
  • deps: transitive deps require 20 || >=22
Bug Fixes
codecov/codecov-action (codecov/codecov-action)

v7.0.0

Compare Source

⚠️ Due to migration issues with keybase, we are unable to update our keys under the codecovsecurity account. We have deleted the account and are using codecovsecops with the original gpg key

What's Changed

Full Changelog: codecov/codecov-action@v6.0.1...v7.0.0

v7

Compare Source

v6.0.2

Compare Source

This is a copy of the v7.0.0 release to make updates easier

What's Changed

Full Changelog: codecov/codecov-action@v6.0.1...v6.0.2

v6.0.1

Compare Source

What's Changed

Full Changelog: codecov/codecov-action@v6.0.0...v6.0.1

v6.0.0

Compare Source

⚠️ This version introduces support for node24 which make cause breaking changes for systems that do not currently support node24. ⚠️
What's Changed

Full Changelog: codecov/codecov-action@v5.5.4...v6.0.0

v6

Compare Source

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

v17.2.0

Compare Source

Minor Changes

  • #​1823 ee156cc - The chunking of tasks based on maximum command line argument length has been re-implemented to be more precise. Now the chunking happens based on the final generated command string, instead of just the list of staged files like previously. This benefits mainly Windows platforms and function commands like:

    /** @type {import('lint-staged').Configuration} */
export default {
  "*.ts": () => "tsc", // Run "tsc" when any TS file is changed (for entire project)
};

    Where the spawned command is literally "tsc" without any extra arguments. Previously, this was still chunked when a lot of files were staged. Now, it probably won't be chunked because the length of the command is just three letters.

    Also, native JavaScript/Node.js function tasks won't be chunked at all, when previously they were run multiple times when chunked:

    /** @type {import('lint-staged').Configuration} */
export default {
  "*.js": {
    title: "Log staged JS files to console",
    task: async (files) => {
      console.log("Staged JS files:", files);
    },
  },
};

v17.1.1

Compare Source

Patch Changes
  • #​1820 a626a9f - It's now possible to set --max-arg-length=Infinity to effectively disable chunking of tasks based on the number of staged files. The parsing and validation of the numeric CLI options --max-arg-length and --concurrency has been improved.

v17.1.0

Compare Source

Minor Changes

  • #​1816 7568d4f - The console output of lint-staged has been simplified so that there's less interactive spinners and more explicit messages like "Started…" -> "Done!". The primary purpose of this was to remove Listr2, a very large dependency.

    Before:

    Size of node_modules/ after installing: 1561.7 kB with 29 packages.

    Fancy interactive spinners, but output dynamically changes:

    ✔ Backed up original state in git stash (0b191303)
✔ Running tasks for staged files...
✔ Staging changes from tasks...
✔ Cleaning up temporary files...

    After:

    Size of node_modules/ after installing: 974.0 kB with 5 packages (37.6 % smaller, 82.7 % less transitive dependencies).

    Simpler but more explicit output:

    ⋯ Backing up original state…
✔ Done backing up original state (35b38ed1)!
⋯ Running tasks for staged files…
    *.js — 1 file
      ⋯ oxlint --fix
    *.{json,md} — 1 file
      ⋯ oxfmt --write

✔ oxfmt --write
✔ oxlint --fix

✔ Done running tasks for staged files!
⋯ Staging changes from tasks…
✔ Done staging changes from tasks!
⋯ Cleaning up temporary files…
✔ Done cleaning up temporary files!
Patch Changes

  • #​1816 c19079d - Try to restore hidden unstaged changes when using --no-revert.

  • #​1818 efb23a2 - Console output colors are enabled/disabled more consistently.

  • #​1818 26112a1 - Failed JS function tasks now properly kill other tasks, unless --continue-on-error is used. Previously their failure didn't affect other tasks.

v17.0.8

Compare Source

Patch Changes

  • #​1809 179b437 - Fix lint-staged discarding the ongoing merge conflict status (.git/MERGE_HEAD) when using the --hide-unstaged or --hide-all options.

  • #​1811 3d0b2c0 - Fix issues with Git commands that are successful but also emit warnings to stderr, by ignoring the stderr output completely when the process exits with code 0. This was the behavior when using nano-spawn and execa, but when switching to tinyexec in 16.3.0 both stdout and stderr were used as interleaved output.

v17.0.7

Compare Source

Patch Changes

v17.0.6

Compare Source

Patch Changes

  • #​1803 bdf2770 - Run all tests with Deno, in addition to Node.js and Bun.

  • #​1796 7508272 - Fix performance regression of lint-staged v17 by going back to using git add to stage task modifications. This was changed to git update-index --again in v17 for less manual work, but unfortunately the update-index command gets slower in very large Git repos.

  • #​1797 7b2505a - This version of lint-staged uses the new staged publishing for npm packages feature. Releases are already published from GitHub Actions with trusted publishing, but now an additional approval with two-factor authentication is also required.

  • #​1802 321b0a9 - Downgrade dependency tinyexec@1.2.2 to avoid issues in version 1.2.3.

v17.0.5

Compare Source

Patch Changes
  • #​1792 1f67271 - Correctly set the --max-arg-length default value based on the running platform. This controls how very long lists of staged files are split into multiple chunks.

v17.0.4

Compare Source

Patch Changes

  • #​1788 f95c1f8 - Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:

    • after editing <file> it is staged with git add <file>, and then committed with git commit
    • after editing <file> it is committed with git commit --all without explicit git add
    • after editing <file> it is committed with git commit <pathspec> without explicit git add

    There's new test cases which actually setup the Git pre_commit hook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.

v17.0.3

Compare Source

Patch Changes
  • #​1782 06813f9 Thanks @​iiroj! - Fix lint-staged behavior when implicitly committing files without using git add by either:
    • git commit -am "my commit message" where -a (--all) means to automatically stage all tracked modified and deleted files
    • git commit -m "my commit message" . where . is an example of a pathspec where matching files will be staged

v17.0.2

Compare Source

Patch Changes

v17.0.1

Compare Source

Patch Changes
  • #​1776 4a5664b Thanks @​iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.

v17.0.0

Compare Source

Major Changes

  • #​1745 e244adf Thanks @​iiroj! - Node.js v20 is no longer supported, and the oldest supported version is now 22.22.1, which is an active LTS version at the time of this release. Node.js 20 will be EOL after April 2026. Please upgrade your Node.js version!

  • #​1676 0584e0b Thanks @​outslept! - Lint-staged now tries to verify the installed Git version is at least 2.32.0, released in 2021. If you're using an even older Git version, you need to upgrade it before running lint-staged!

  • #​1745 2dcc40a Thanks @​iiroj! - The dependency yaml is now marked as optional and probably won't be installed by default. If you're using a YAML configuration file you should install the package separately:

    npm install --development yaml

    If you're using .lintstagedrc as the config file name (without a file extension), it will be treated as a YAML file. If the content is JSON, consider renaming it to .lintstagedrc.json to avoid needing to install yaml.

Minor Changes

  • #​1748 809d5ef Thanks @​iiroj! - Add new option --hide-all for hiding all unstaged changes and untracked files, before running tasks. This makes it easier to run tools like Knip which check for unused code. Untracked files are included in the backup stash and restored automatically after running.

  • #​1759 f13045a Thanks @​iiroj! - Update dependencies, including tinyexec@1.1.1 to fix the following issues:

    • When using a Node.js version manager with multiple versions installed (nvm, n, for example), scripts with the #!/usr/bin/env node shebang (Prettier, ESLint, for example) were previously spawned using the default Node.js version configured by the version manager (the one which node points to) on POSIX systems. Now, they will be spawned with the same version that lint-staged itself was started with.
      • For example, if your default Node.js version is 24.14.1 but lint-staged is run with the latest version 25.9.0, the tasks spawned by lint-staged will now also use version 25.9.0. Previously they were spawned using 24.14.1.
    • When installing Node.js from the Ubuntu App Center (Snap store), the node executable available in PATH is a symlink pointing to Snap itself. The sandboxing features of Snap prevented lint-staged from spawning scripts with the #!/usr/bin/env node shebang, because it meant lint-staged tried to spawn Snap via the symlink. This resulted in an ENOENT error when tryi

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Zurich)

  • Branch creation
    • "after 2pm on Monday"
  • 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.

@github-actions

github-actions Bot commented May 4, 2026

Copy link
Copy Markdown

This PR will trigger no release when merged.

@renovate
renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from 473449f to 087bec0 Compare May 5, 2026 03:27
@renovate
renovate Bot force-pushed the renovate-major-external-major branch 2 times, most recently from b4f23af to ffcb9af Compare May 18, 2026 14:40
@renovate
renovate Bot force-pushed the renovate-major-external-major branch 6 times, most recently from 38b08ed to bc58906 Compare May 24, 2026 15:15
@renovate
renovate Bot force-pushed the renovate-major-external-major branch 3 times, most recently from 083acb6 to 71b36bd Compare June 2, 2026 00:57
@renovate
renovate Bot force-pushed the renovate-major-external-major branch 4 times, most recently from ff82e5e to 52a63a7 Compare June 14, 2026 14:54
@renovate
renovate Bot force-pushed the renovate-major-external-major branch from 52a63a7 to aceda5b Compare June 21, 2026 03:04
@renovate
renovate Bot force-pushed the renovate-major-external-major branch 3 times, most recently from f294f15 to 9047da7 Compare July 4, 2026 23:24
@renovate
renovate Bot force-pushed the renovate-major-external-major branch 3 times, most recently from fcf5d17 to 722c2d3 Compare July 16, 2026 19:10
@renovate
renovate Bot force-pushed the renovate-major-external-major branch 4 times, most recently from c18b169 to 96e47cd Compare July 28, 2026 14:41
@renovate
renovate Bot force-pushed the renovate-major-external-major branch from 96e47cd to 2de3d6e Compare August 1, 2026 19:04
@renovate
renovate Bot force-pushed the renovate-major-external-major branch 7 times, most recently from 3e851bc to cc4deab Compare August 7, 2026 06:50
@renovate
renovate Bot force-pushed the renovate-major-external-major branch from cc4deab to 1b7c392 Compare August 11, 2026 00:04
@renovate
renovate Bot force-pushed the renovate-major-external-major branch from 1b7c392 to 57c3bb6 Compare August 12, 2026 03:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants