Skip to content

chore(deps): update external dev major (major) - #702

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

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

Conversation

@renovate

@renovate renovate Bot commented Aug 31, 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
@web/test-runner (source) ^0.18.0 → ^1.0.0 age confidence
@web/test-runner-commands (source) 0.9.0 → 1.0.1 age confidence
chai (source) 4.5.0 → 6.2.2 age confidence
lint-staged ^16.2.7 → ^17.0.0 age confidence
sinon (source) 13.0.2 → 22.1.0 age confidence

Release Notes

modernweb-dev/web (@​web/test-runner)

v1.0.0

Compare Source

Major Changes
  • 5260164: Drop support for Node.js 18 and 20, which have reached end-of-life. The minimum supported Node.js version is now 22.0.0.
    The Node code is compiled to ES2024 which is aligned with the Node 22.
Patch Changes

v0.20.2

Compare Source

Patch Changes
  • 7aedbaa: Summary Reporter - re-enabled error reporting and made option to disable browser logs and error reporting in this reporter

v0.20.1

Compare Source

Patch Changes

  • 24e3290: Improve debug message for test runner uncaught exceptions

    This should make debugging easier. It wasn't very easy to figure out
    where the errors originated from (because of how the actual uncaught
    exception only happened with many concurrent builds inside a sandbox
    environment that is hard to debug).

  • Updated dependencies [79b0ba4]

v0.20.0

Compare Source

Minor Changes
  • 86eaa21: Upgrade puppeteer version to v24
Patch Changes

v0.19.0

Compare Source

Minor Changes
  • b546e8b: Upgrade puppeteer-core and puppeteer to v23
Patch Changes
modernweb-dev/web (@​web/test-runner-commands)

v1.0.1

Compare Source

Patch Changes
  • 19de300: fix importing under typescript

v1.0.0

Compare Source

Major Changes
  • 5260164: Drop support for Node.js 18 and 20, which have reached end-of-life. The minimum supported Node.js version is now 22.0.0.
    The Node code is compiled to ES2024 which is aligned with the Node 22.
Patch Changes
chaijs/chai (chai)

v6.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v6.2.1...v6.2.2

v6.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v6.2.0...v6.2.1

v6.2.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v6.1.0...v6.2.0

v6.1.0

Compare Source

What's Changed

  • build(deps-dev): bump tar-fs from 3.0.9 to 3.1.1 by @​dependabot[bot] in #​1706
  • feat: add eventEmitter (#​1693)
    Adds an event emitter for hooking into method/property creation in #​1693

Full Changelog: chaijs/chai@v6.0.2...v6.1.0

v6.0.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v6.0.0...v6.0.1

v6.0.0

Compare Source

BREAKING CHANGES

Chai is now bundled into a single file. The lib/*.js files are no longer present, and so any code that imports those files directly will need to change. The only file that can be imported now is ./index.js.

What's Changed

Full Changelog: chaijs/chai@v5.3.2...v6.0.0

v5.3.3

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.3.2...v5.3.3

v5.3.2

Compare Source

Reverts the removal of the bundled version of chai in 5.3.1

What's Changed

Full Changelog: chaijs/chai@v5.3.1...v5.3.2

v5.3.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.3.0...v5.3.1

v5.3.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.2.2...v5.3.0

v5.2.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

Mostly internal changes but @​SuperchupuDev realised the package.json engines field was out of date, so it has been updated to reflect that v5.0.0 onwards only supports Node >=18.

New Contributors

Full Changelog: chaijs/chai@v5.2.0...v5.2.1

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.2...v5.2.0

v5.1.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.1.1...v5.1.2

v5.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.0...v5.1.1

v5.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.0.3...v5.1.0

v5.0.3

Compare Source

Fix bad v5.0.2 publish.

Full Changelog: chaijs/chai@v5.0.2...v5.0.3

v5.0.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.0.1...v5.0.2

v5.0.0

Compare Source

BREAKING CHANGES

  • Chai now only supports EcmaScript Modules (ESM). This means your tests will need to either have import {...} from 'chai' or import('chai'). require('chai') will cause failures in nodejs. If you're using ESM and seeing failures, it may be due to a bundler or transpiler which is incorrectly converting import statements into require calls.
  • Dropped support for Internet Explorer.
  • Dropped support for NodeJS < 18.
  • Minimum supported browsers are now Firefox 100, Safari 14.1, Chrome 100, Edge 100. Support for browsers prior to these versions is "best effort" (bug reports on older browsers will be assessed individually and may be marked as wontfix).

What's Changed

New Contributors

Full Changelog: chaijs/chai@4.3.1...v5.0.0

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

v17.5.1

Compare Source

Patch Changes

  • #​1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

    A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

v17.5.0

Compare Source

Minor Changes
  • #​1847 f9063b7 - Lint-staged now refuses to run when files were staged with --intent-to-add, because Git stash doesn't support them. Previously this was an unhandled error.
Patch Changes

  • #​1848 d718ccc - Lint-staged now handles color support better in non-TTY streams, and honors the FORCE_COLOR environment variable.

  • #​1845 7e5ece8 - Update tinyexec@1.3.1 so that local binaries from node_modules/.bin are resolved starting from the directory of each lint-staged configuration file (in monorepo setups). This behavior was broken in lint-staged@16.3.0 where they were only resolved from the current working directory and up.

  • #​1845 eb8a4e3 - Do not try to restore untracked files when using --hide-all and there is no initial commit yet.

v17.4.1

Compare Source

Patch Changes
  • #​1840 efe5b63 - This is a version-bump-only release because the previous version 17.4.0 was not published to npmjs.com due to problems with GitHub Actions and Changesets.

v17.3.0

Compare Source

Minor Changes

  • #​1825 16b3f74 - It is now possible to run multiple tasks in parallel for a single glob by configuring it with an array of tasks (which run sequentially), and then placing another array inside it (where the tasks will run in parallel). The following demonstrates the order tasks will start in:

    {
  "*.ts": ["first", "second", ["third", "third"], "fourth"]
}

    As a concrete example, lint-staged's own configuration is:

    /** @type {import('./lib/index.js').Configuration} */
export default {
  "*": [
    [
      "oxfmt --check --no-error-on-unmatched-pattern",
      "oxlint --no-error-on-unmatched-pattern",
    ],
  ],
  "*.ts": () => "tsc",
};

    which means:

    1. for all staged files, run the two commands in parallel with staged filenames appended, for example:
      • oxfmt --check --no-error-on-unmatched-pattern lib/index.js
      • oxlint --no-error-on-unmatched-pattern lib/index.js
    2. additionally, if any *.ts files are staged, run tsc without appending any arguments
    3. The two sets of commands also run in parallel
Patch Changes
  • #​1829 15f7e53 - During an in-progress merge, files that are unchanged from the branch being merged are now skipped. Technically, files are only included if there are staged changes against both HEAD and MERGE_HEAD.

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 trying to run prettier, for example. Now, since the real node executable's directory is available in the PATH, lint-staged will instead spawn the script with the real node binary succesfully.

  • #​1761 d3251b1 Thanks @​iiroj! - Lint-staged now runs git update-index --again after running tasks, instead of git add <originally staged files>. This should improve compatibility when using non-default indexes, for example when committing with a pathspec git commit -m "message" . instead of adding files to the index.

  • #​1745 a9585ac Thanks @​iiroj! - Remove commander as a dependency and use the built-in parseArgs from node:util to parse CLI flags.

Patch Changes

❗ Important

✂ 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 is behind base branch, 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.

@aem-code-sync

aem-code-sync Bot commented Aug 31, 2026 •
edited
Loading

Copy link
Copy Markdown

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-sync branch
Commits

@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from d12dd56 to ee43436 Compare September 1, 2026 07:03
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 1, 2026 07:03 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from ee43436 to cc88ead Compare September 1, 2026 08:50
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 1, 2026 08:50 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from cc88ead to 0ec2430 Compare September 1, 2026 11:11
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 1, 2026 11:11 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 0ec2430 to bcca43d Compare September 1, 2026 13:57
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 1, 2026 13:57 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch 2 times, most recently from 6094be2 to e1e1680 Compare September 2, 2026 07:44
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 2, 2026 07:44 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from e1e1680 to 10b6004 Compare September 2, 2026 09:14
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 2, 2026 09:14 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 10b6004 to 8173acd Compare September 2, 2026 13:06
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 2, 2026 13:06 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 8173acd to 8b39749 Compare September 2, 2026 15:18
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 2, 2026 15:18 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 8b39749 to ba5c04c Compare September 3, 2026 12:29
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 3, 2026 12:29 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from ba5c04c to e2918ad Compare September 3, 2026 12:53
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 3, 2026 12:53 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from e2918ad to a405388 Compare September 3, 2026 13:04
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 3, 2026 13:04 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from a405388 to cefea1a Compare September 3, 2026 15:38
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 3, 2026 15:38 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from cefea1a to 8113c1a Compare September 3, 2026 16:39
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 3, 2026 16:39 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 8113c1a to cb2c573 Compare September 4, 2026 09:43
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 4, 2026 09:43 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 32a5030 to d83a607 Compare September 7, 2026 16:01
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 7, 2026 16:01 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from d83a607 to a785c4b Compare September 8, 2026 13:38
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 8, 2026 13:38 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from a785c4b to 26649be Compare September 9, 2026 12:18
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 9, 2026 12:18 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 26649be to e3da95a Compare September 10, 2026 11:55
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 10, 2026 11:55 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from e3da95a to f1bca63 Compare September 10, 2026 17:46
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from f1bca63 to 82d8707 Compare September 10, 2026 19:14
@aem-code-sync
aem-code-sync Bot temporarily deployed to renovate-major-external-dev-major September 10, 2026 19:14 Inactive
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 82d8707 to 6211c16 Compare September 11, 2026 14:25
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 6211c16 to 61202f3 Compare September 14, 2026 15:38
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 61202f3 to 621d478 Compare September 15, 2026 08:11
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 621d478 to 88d9c92 Compare September 15, 2026 09:35
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 88d9c92 to 673b7b6 Compare September 15, 2026 15:55
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 673b7b6 to a9ee5b5 Compare September 16, 2026 08:44
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from a9ee5b5 to 9e43d77 Compare September 16, 2026 16:02
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 9e43d77 to 1ca955e Compare September 17, 2026 09:31
@renovate
renovate Bot force-pushed the renovate-major-external-dev-major branch from 1ca955e to 2b3fe82 Compare September 17, 2026 12:43

This branch was successfully deployed

1 active deployment
renovate-major-external-dev-major — fa6806cc Deployed Oct 5, 2026 by aem-code-sync[bot]
View deployment
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