chore(deps-dev): bump the npm-tools-visual-chromatic-patch-minor group in /tools/visual-chromatic with 3 updates#192
Closed
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the npm-tools-visual-chromatic-patch-minor group in /tools/visual-chromatic with 3 updates: [@chromatic-com/playwright](https://github.com/chromaui/chromatic-e2e/tree/HEAD/packages/playwright), [@playwright/test](https://github.com/microsoft/playwright) and [chromatic](https://github.com/chromaui/chromatic-cli). Updates `@chromatic-com/playwright` from 0.12.3 to 0.14.10 - [Release notes](https://github.com/chromaui/chromatic-e2e/releases) - [Changelog](https://github.com/chromaui/chromatic-e2e/blob/main/packages/playwright/CHANGELOG.md) - [Commits](https://github.com/chromaui/chromatic-e2e/commits/@chromatic-com/playwright@0.14.10/packages/playwright) Updates `@playwright/test` from 1.58.2 to 1.61.1 - [Release notes](https://github.com/microsoft/playwright/releases) - [Commits](microsoft/playwright@v1.58.2...v1.61.1) Updates `chromatic` from 16.0.0 to 16.10.1 - [Release notes](https://github.com/chromaui/chromatic-cli/releases) - [Changelog](https://github.com/chromaui/chromatic-cli/blob/main/CHANGELOG.md) - [Commits](chromaui/chromatic-cli@v16.0.0...v16.10.1) --- updated-dependencies: - dependency-name: "@chromatic-com/playwright" dependency-version: 0.14.10 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm-tools-visual-chromatic-patch-minor - dependency-name: "@playwright/test" dependency-version: 1.61.1 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm-tools-visual-chromatic-patch-minor - dependency-name: chromatic dependency-version: 16.10.1 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm-tools-visual-chromatic-patch-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
area:ci
dependabot
Bot
added
type:chore
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
Prekzursil
pushed a commit
that referenced
this pull request
Jul 25, 2026
Supersedes the first attempt on this branch, which forced brace-expansion to
5.0.8 and was DEFECTIVE. Recording why, so it is not retried:
brace-expansion 5.x exports { EXPANSION_MAX, EXPANSION_MAX_LENGTH, expand }
with NO callable module and NO default export. minimatch 3.1.5 does
`require('brace-expansion')` and calls it, so forcing 5.x yields
`TypeError: expand is not a function` on any brace pattern. The osv gate
went green anyway because CI never evaluates a brace pattern -- a green
gate was hiding a real runtime break.
Root cause of the finding: GHSA-mh99-v99m-4gvg (CVE-2026-14257) has a single
affected range, `introduced: 0 / fixed: 5.0.8`. There is NO 1.x or 2.x patch,
so no in-major bump could ever clear it while minimatch 3.x is in the tree.
Real fix -- delete the vulnerable subtree instead of patching it. Adopting the
tooling bumps from #192 drops the whole legacy webpack chain
(fork-ts-checker-webpack-plugin -> minimatch ^3.0.4 -> brace-expansion):
@chromatic-com/playwright ^0.12.3 -> ^0.14.10
@playwright/test 1.58.2 -> 1.61.1
chromatic ^16.0.0 -> ^16.10.1
tree: 343 -> 113 packages
minimatch, brace-expansion, fast-uri, fork-ts-checker-webpack-plugin: ABSENT
That alone retires GHSA-3jxr-9vmj-r5cp, GHSA-mh99-v99m-4gvg, GHSA-4c8g-83qw-93j6
and GHSA-v2hh-gcrm-f6hx by removal. Two bounded floors cover the remainder,
which #192's stale lock still carried (postcss 8.5.16, esbuild 0.27.7):
postcss >=8.5.18 <9 (GHSA-r28c-9q8g-f849) -> resolves 8.5.23
esbuild >=0.28.1 <0.29 (GHSA-g7r4-m6w7-qqqr) -> resolves 0.28.1
Bounded floors, not exact pins -- an exact pin freezes the package and blinds
dependabot to future patches. The pre-existing unbounded entries are why
fast-uri drifted a whole major to 4.0.0.
No [[IgnoredVulns]] entry is added: the finding is fixed by upgrade, which is
what osv-scanner.toml's stated policy requires, and CLAUDE.md forbids
suppressions.
Verified locally, independent of CI:
osv-scanner scan source --config=osv-scanner.toml --recursive ./tools/visual-chromatic
-> No issues found (exit 0)
npm ci --ignore-scripts -> exit 0, found 0 vulnerabilities
Prekzursil
added a commit
that referenced
this pull request
Jul 25, 2026
…gate (#197) * fix(deps): pin bounded floors for brace-expansion, fast-uri, postcss The `quality / quality` required check has been failing on `main` since 2026-07-24 at the `gate-deps osv-scanner` step. osv-scanner exits 1 on ANY finding, so every open dependabot PR in this repo is unmergeable until the whole set is clean -- no individual bump can turn the gate green. Closes the four open Dependabot alerts in tools/visual-chromatic: GHSA-3jxr-9vmj-r5cp brace-expansion 1.1.13 -> 5.0.8 (fix >=1.1.16) GHSA-4c8g-83qw-93j6 fast-uri 4.0.0 -> 4.1.1 (fix >=4.0.1) GHSA-v2hh-gcrm-f6hx fast-uri 4.0.0 -> 4.1.1 (fix >=4.1.1) GHSA-r28c-9q8g-f849 postcss 8.5.15 -> 8.5.23 (fix >=8.5.18) plus GHSA-mh99-v99m-4gvg, which osv-scanner reports but which has no Dependabot alert yet. It is only fixed in brace-expansion 5.0.8, so a `<2` bound is NOT sufficient -- hence the 5.x floor. Bounded floors (`>=X <NextMajor`), not exact pins: an exact pin freezes the package and blinds dependabot to future patches. The pre-existing entries in this overrides block were unbounded (`>=3.1.2`), which is how fast-uri drifted a whole major to 4.0.0; the three managed here now carry upper bounds. Verified locally (independent of CI): osv-scanner scan source --recursive ./tools/visual-chromatic -> No issues found npm ci --ignore-scripts -> 326 packages, 0 vulnerabilities * fix(deps): upgrade visual-chromatic tooling to clear the osv gate Supersedes the first attempt on this branch, which forced brace-expansion to 5.0.8 and was DEFECTIVE. Recording why, so it is not retried: brace-expansion 5.x exports { EXPANSION_MAX, EXPANSION_MAX_LENGTH, expand } with NO callable module and NO default export. minimatch 3.1.5 does `require('brace-expansion')` and calls it, so forcing 5.x yields `TypeError: expand is not a function` on any brace pattern. The osv gate went green anyway because CI never evaluates a brace pattern -- a green gate was hiding a real runtime break. Root cause of the finding: GHSA-mh99-v99m-4gvg (CVE-2026-14257) has a single affected range, `introduced: 0 / fixed: 5.0.8`. There is NO 1.x or 2.x patch, so no in-major bump could ever clear it while minimatch 3.x is in the tree. Real fix -- delete the vulnerable subtree instead of patching it. Adopting the tooling bumps from #192 drops the whole legacy webpack chain (fork-ts-checker-webpack-plugin -> minimatch ^3.0.4 -> brace-expansion): @chromatic-com/playwright ^0.12.3 -> ^0.14.10 @playwright/test 1.58.2 -> 1.61.1 chromatic ^16.0.0 -> ^16.10.1 tree: 343 -> 113 packages minimatch, brace-expansion, fast-uri, fork-ts-checker-webpack-plugin: ABSENT That alone retires GHSA-3jxr-9vmj-r5cp, GHSA-mh99-v99m-4gvg, GHSA-4c8g-83qw-93j6 and GHSA-v2hh-gcrm-f6hx by removal. Two bounded floors cover the remainder, which #192's stale lock still carried (postcss 8.5.16, esbuild 0.27.7): postcss >=8.5.18 <9 (GHSA-r28c-9q8g-f849) -> resolves 8.5.23 esbuild >=0.28.1 <0.29 (GHSA-g7r4-m6w7-qqqr) -> resolves 0.28.1 Bounded floors, not exact pins -- an exact pin freezes the package and blinds dependabot to future patches. The pre-existing unbounded entries are why fast-uri drifted a whole major to 4.0.0. No [[IgnoredVulns]] entry is added: the finding is fixed by upgrade, which is what osv-scanner.toml's stated policy requires, and CLAUDE.md forbids suppressions. Verified locally, independent of CI: osv-scanner scan source --config=osv-scanner.toml --recursive ./tools/visual-chromatic -> No issues found (exit 0) npm ci --ignore-scripts -> exit 0, found 0 vulnerabilities --------- Co-authored-by: Prekzursil <noreply@prekzursil.dev>
Owner
|
Superseded by #197 (@chromatic-com/playwright ^0.14.10, @playwright/test 1.61.1, chromatic ^16.10.1 -- the exact three bumps this PR proposed), merged c2db63a. Verified against the merged manifest, not the title: tools/visual-chromatic/package.json on main now reads devDependencies {@chromatic-com/playwright ^0.14.10, @playwright/test 1.61.1, chromatic ^16.10.1}. #197 additionally floors postcss >=8.5.18 <9 and esbuild >=0.28.1 <0.29, which this PR's lock still had at 8.5.16 / 0.27.7. |
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/tools/visual-chromatic/npm-tools-visual-chromatic-patch-minor-ae42713263
branch
July 25, 2026 07:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the npm-tools-visual-chromatic-patch-minor group in /tools/visual-chromatic with 3 updates: @chromatic-com/playwright, @playwright/test and chromatic.
Updates
@chromatic-com/playwrightfrom 0.12.3 to 0.14.10Release notes
Sourced from @chromatic-com/playwright's releases.
... (truncated)
Changelog
Sourced from @chromatic-com/playwright's changelog.
... (truncated)
Commits
688fc10Version Packages (#406)161a994fix: preserve asset extension when handling query params (#405)45000feVersion Packages (#402)6837593fix(playwright): prevent duplicate story ids by allowing multiple projects to...ebbb5bcVersion Packages (#393)f1ba7f9fix(playwright): snapshot script fails injavaScriptEnabled: false(#392)7351f43Version Packages (#390)f95b82afix: hide unrelevant Storybook options (#389)6dc4db9Version Packages (#385)daa3ffefix(playwright): wait for browser module before takeSnapshot (#387)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@chromatic-com/playwrightsince your current version.Updates
@playwright/testfrom 1.58.2 to 1.61.1Release notes
Sourced from @playwright/test's releases.
... (truncated)
Commits
39e3553cherry-pick(#41399): fix(test): load require-reached files as commonjs in syn...4328122chore: mark v1.61.1 (#41404)2c29a94fix(tracing): stop recording websocket frames outside of chunks (#41398)4324b19cherry-pick(#41367): fix(test): keep builtin expect matchers on base extend041e7e3cherry-pick(#41364): fix(har):WebSocketmessage timestamps should be in mi...b8a0fc3cherry-pick(#41309, #43149): Revert "fix(firefox): treat `navigationCommitted...b5a3175cherry-pick(#41319): fix(loader): support other node versionsd4724a9cherry-pick(#41290): feat(docker): add Ubuntu 26.04 (Resolute Raccoon) image1cc5a90cherry-pick(#41295): chore: PLAYWRIGHT_TRACING_NO_WEBSOCKET_FRAMES and PLAYWR...a6772bdcherry-pick(#41280): Revert "fix(trace-viewer): add keyboard navigation to `N...Updates
chromaticfrom 16.0.0 to 16.10.1Release notes
Sourced from chromatic's releases.
... (truncated)
Changelog
Sourced from chromatic's changelog.
... (truncated)
Commits
3a6f612Bump version to: 16.10.1 [skip ci]e0e9ce9Update CHANGELOG.md [skip ci]8ece961Merge pull request #1332 from chromaui/CAP-44005087fb8Supportall: false7b1c005Fix getUncommittedHash in Windows environments1a8c8ceMerge pull request #1326 from chromaui/cody/flaky-test7e9321eRemove duplicate skipped tested870e5Increase flaky test timeout9ed03ecMerge pull request #1323 from chromaui/CAP-438566af1d1Bump version to: 16.10.0 [skip ci]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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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