chore(deps-dev): bump the dev-dependencies group across 1 directory with 5 updates

[dependabot]

Bumps the dev-dependencies group with 5 updates in the / directory:

Package	From	To
jsdom	27.0.0	27.1.0
lint-staged	16.2.4	16.2.6
mocha	11.7.4	11.7.5
mochawesome-report-generator	6.3.0	6.3.2
semantic-release	25.0.0	25.0.1

Updates jsdom from 27.0.0 to 27.1.0

Release notes

Sourced from jsdom's releases.

Version 27.1.0

• Improved CSS parsing by switching to @acemir/cssom, including support for nested selectors, nested declarations, layer statements, and improved at-rule validation. (acemir)
• Fixed some selector cache invalidation issues where changes to attributes were not being picked up. (asamuzaK)
• Fixed package.json "engines" field to reflect the new minimum Node.js versions needed to run jsdom, as noted in the changelog for v27.0.1.

Version 27.0.1

This release inadvertently raised the minimum Node.js version from v20.0.0 to v20.19.0+, v22.12.0+, v24.0.0+. (This happened via a dependency update.) This probably should have been a breaking (major) change, instead of happening in a patch version, since it prevents using earlier Node.js versions.

After further testing, we found that most of our development dependencies also require these versions, and so it's not feasible for the jsdom project to support earlier Node.js versions. (For example, our testing frameworks will not run on them.) If you need to use such earlier versions, or otherwise are working in an environment which gives related errors such as ERR_REQUIRE_ESM, then please stick with the v26.1.0 release of jsdom. (Noting, of course, that such versions are unsupported, and we will not respond to bug reports opened against them.)

Subsequent jsdom releases will explicitly require these minimum Node.js versions, and will have CI testing to ensure that the minimum version is not accidentally raised again.

Normal changelog:

• Fixed some regressions in CSS selectors. Most such regression fixes were done in a minor update of a dependency, and thus available for all fresh installs of v27.0.0. However, one related to class="" attribute changes is only possible with a new version of jsdom. (asamuzaK)

Changelog

Sourced from jsdom's changelog.

27.1.0

• Improved CSS parsing by switching to @acemir/cssom, including support for nested selectors, nested declarations, layer statements, and improved at-rule validation. (acemir)
• Fixed some selector cache invalidation issues where changes to attributes were not being picked up. (asamuzaK)
• Fixed package.json "engines" field to reflect the new minimum Node.js versions needed to run jsdom, as noted in the changelog for v27.0.1.

27.0.1

This release inadvertently raised the minimum Node.js version from v20.0.0 to v20.19.0+, v22.12.0+, v24.0.0+. (This happened via a dependency update.) This probably should have been a breaking (major) change, instead of happening in a patch version, since it prevents using earlier Node.js versions.

After further testing, we found that most of our development dependencies also require these versions, and so it's not feasible for the jsdom project to support earlier Node.js versions. (For example, our testing frameworks will not run on them.) If you need to use such earlier versions, or otherwise are working in an environment which gives related errors such as ERR_REQUIRE_ESM, then please stick with the v26.1.0 release of jsdom. (Noting, of course, that such versions are unsupported, and we will not respond to bug reports opened against them.)

Subsequent jsdom releases will explicitly require these minimum Node.js versions, and will have CI testing to ensure that the minimum version is not accidentally raised again.

Normal changelog:

• Fixed some regressions in CSS selectors. Most such regression fixes were done in a minor update of a dependency, and thus available for all fresh installs of v27.0.0. However, one related to class="" attribute changes is only possible with a new version of jsdom. (asamuzaK)

Commits

• adb999a Version 27.1.0
• 91f40c4 Update dependencies and dev dependencies
• ebad33c Note more strict minimum version requirement
• bd02585 Swap rweb-cssom to @​acemir/cssom
• f15c830 Add failing test for cssText setter
• a833763 Clear domSelector cache on attribute change
• 819ff52 Version 27.0.1
• 23539d4 Call domSelector.clear() on class change
• 894151b Add regression tests and update dependencies
• aa2d8db Add a regression test for getComputedStyle() across shadow boundaries
• Additional commits viewable in compare view

Updates lint-staged from 16.2.4 to 16.2.6

Release notes

Sourced from lint-staged's releases.

v16.2.6

Patch Changes

• #1693 33d4502 Thanks @​Adrian-Baran-GY! - Fix problems with --continue-on-error option, where tasks might have still been killed (SIGINT) when one of them failed.

v16.2.5

Patch Changes

• #1687 9e02d9d Thanks @​iiroj! - Fix unhandled promise rejection when spawning tasks (instead of the tasks themselves failing). Previously when a task failed to spawn, lint-staged also failed and the backup stash might not have been automatically restored.

Changelog

Sourced from lint-staged's changelog.

16.2.6

Patch Changes

• #1693 33d4502 Thanks @​Adrian-Baran-GY! - Fix problems with --continue-on-error option, where tasks might have still been killed (SIGINT) when one of them failed.

16.2.5

Patch Changes

• #1687 9e02d9d Thanks @​iiroj! - Fix unhandled promise rejection when spawning tasks (instead of the tasks themselves failing). Previously when a task failed to spawn, lint-staged also failed and the backup stash might not have been automatically restored.

Commits

• a1ec972 chore(changeset): release
• ddd5340 build(deps): regenerate package-lock.json
• ceb253a build(deps): update Vitest 4
• 58cc126 build(deps): update listr2
• 33d4502 fix: run all tasks when --continue-on-error=true
• 54ba9eb test: fix test usage for --continue-on-error
• b1715d9 test: fix test assertions for --continue-on-error to reveal incorrect behavior
• 1f6a326 chore(changeset): release
• 6ab937c ci: use separate caches for MSYS2 and Cygwin
• 6d71384 fix: catch errors when calling spawn
• Additional commits viewable in compare view

Updates mocha from 11.7.4 to 11.7.5

Release notes

Sourced from mocha's releases.

v11.7.5

11.7.5 (2025-11-04)

🩹 Fixes

• swallow more require errors from *ts files (#5498) (d89dbaf)

🧹 Chores

• run tests on PRs for and pushes to v11.x (#5525) (8b21b38)
• setup release-please for v11 (#5522) (663fff4)

Changelog

Sourced from mocha's changelog.

11.7.5 (2025-11-04)

🩹 Fixes

• swallow more require errors from *ts files (#5498) (d89dbaf)

🧹 Chores

• run tests on PRs for and pushes to v11.x (#5525) (8b21b38)
• setup release-please for v11 (#5522) (663fff4)

Commits

• 9a6a5db chore(v11.x): release 11.7.5 (#5523)
• 8b21b38 chore: run tests on PRs for and pushes to v11.x (#5525)
• 663fff4 chore: setup release-please for v11 (#5522)
• 8d97220 Update release-please to include v11.x and use Node ^22
• d89dbaf fix: swallow more require errors from *ts files (#5498)
• See full diff in compare view

Updates mochawesome-report-generator from 6.3.0 to 6.3.2

Release notes

Sourced from mochawesome-report-generator's releases.

6.3.2

What's Changed

• Fixed v6.3.1 missing validator.js file from the published tarball #236

Full Changelog: adamgruber/mochawesome-report-generator@6.3.1...6.3.2

6.3.1

What's Changed

• Inline validators and remove validator.js dependency by @​adamgruber in adamgruber/mochawesome-report-generator#235

Full Changelog: adamgruber/mochawesome-report-generator@6.3.0...6.3.1

Changelog

Sourced from mochawesome-report-generator's changelog.

[6.3.2] - 2025-11-05

Fixed

• Version 6.3.1 is missing the newly added validators.js file #236

[6.3.1] - 2025-11-04

Fixed

• Removed validator.js dependency, opting instead to inline the two validation functions that were being used. This addresses a vulnerability in the package version that was being included and should reduce overall bundle size #234

Commits

• bdeb8d2 Release 6.3.2
• 502a45e Release version 6.3.1
• adc5f53 Merge pull request #235 from adamgruber/remove-validator-dep
• 904bc10 Inline validators and remove dependency
• See full diff in compare view

Updates semantic-release from 25.0.0 to 25.0.1

Release notes

Sourced from semantic-release's releases.

v25.0.1

25.0.1 (2025-10-19)

Bug Fixes

• deps: update to the latest version of the npm plugin to add trusted publishing support (fad173e), closes semantic-release/npm#958

v25.0.1-beta.3

25.0.1-beta.3 (2025-10-19)

Bug Fixes

• deps: update to latest npm plugin (a96aced)

v25.0.1-beta.2

25.0.1-beta.2 (2025-10-19)

Bug Fixes

• deps: update to the stable version of the npm plugin to add trusted publishing support (fad173e), closes semantic-release/npm#958

v25.0.1-beta.1

25.0.1-beta.1 (2025-10-16)

Bug Fixes

• deps: update to the beta of the npm plugin (c770748), closes semantic-release/npm#958
• deps: update to the latest alpha of the npm plugin (7c39330), closes semantic-release/npm#958
• deps: update to the latest alpha of the npm plugin (2434041), closes semantic-release/npm#958
• deps: update to the latest alpha of the npm plugin (a3c1129)
• deps: updated to latest alpha of the npm plugin (ea56799)
• deps: upgrade to the latest alpha of the npm plugin (e4ff786), closes semantic-release/npm#958
• deps: use the alpha of the npm plugin (ce3618e), closes semantic-release/npm#958

v25.0.1-alpha.4

25.0.1-alpha.4 (2025-10-16)

Bug Fixes

• deps: update to the beta of the npm plugin (c770748), closes semantic-release/npm#958

v25.0.1-alpha.3

... (truncated)

Commits

• 45b1552 Merge pull request #3906 from semantic-release/beta
• a96aced fix(deps): update to latest npm plugin
• fad173e fix(deps): update to the stable version of the npm plugin to add trusted publ...
• 98ad71d ci(action): update github/codeql-action action to v4.30.9 (#3910)
• 7dcca47 chore(deps): update dependency @​types/node to v22.18.11 (#3909)
• f1f2b89 chore(deps): update dependency got to v14.6.0 (#3908)
• ec8d899 Merge pull request #3905 from semantic-release/alpha
• c770748 fix(deps): update to the beta of the npm plugin
• e6faf9a docs(trusted-publishing): mention the updated restrictions for auth against t...
• 7c39330 fix(deps): update to the latest alpha of the npm plugin
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Note

Free review on us!

CodeRabbit is offering free reviews until Fri Nov 07 2025 to showcase some of the refinements we've made.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}