Repository navigation
chore(deps-dev): bump vitest, playwright, vite, vue and @types/node in one batch - #59
Merged
Merged
Conversation
…n one batch Dependabot opened four patch updates: #55 (vitest group 5.0.3 to 5.0.4 and playwright 1.63.0 to 1.64.0), #56 (vite 8.3.3 to 8.3.4, demo), #57 (@types/node 26.6.4 to 26.6.5, the dev group) and #58 (vue 3.5.43 to 3.5.44). vitest's snapshot keys carry vite's and @types/node's versions as peer suffixes, so all four rewrite the same lockfile lines and they land as one branch, as #50 and #54 did. #55 failed its browser job on its own: the job runs inside mcr.microsoft.com/playwright, whose tag Dependabot cannot see, so the 1.64 client asked a 1.63 image for browsers it does not carry. The tag moves to v1.64.0-noble in ci.yml and release.yml, as the note in dependabot.yml asks. The lockfile is the union of what the four pull requests resolved. A plain re-resolve picked vitest 5.0.5 and playwright 1.64.1, newer than the pull requests, while leaving rolldown behind; it was rebuilt from #56's lockfile with the vitest set pinned for one install, and the package set now matches main plus each pull request's changes exactly. vue moves only as a devDependency of @hexcanvas/vue; its peer range stays ^3.4.0, and pnpm api reports all five API reports unchanged. Closes #55 Closes #56 Closes #57 Closes #58 Tags: #deps #ci Co-Authored-By: htjulia <htjulia1@gmail.com>
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
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.
Dependabot opened four patch updates: #55 (vitest group 5.0.3 to
5.0.4 and playwright 1.63.0 to 1.64.0), #56 (vite 8.3.3 to 8.3.4,
demo), #57 (@types/node 26.6.4 to 26.6.5, the dev group) and #58 (vue
3.5.43 to 3.5.44). vitest's snapshot keys carry vite's and
@types/node's versions as peer suffixes, so all four rewrite the same
lockfile lines and they land as one branch, as #50 and #54 did.
#55 failed its browser job on its own: the job runs inside
mcr.microsoft.com/playwright, whose tag Dependabot cannot see, so the
1.64 client asked a 1.63 image for browsers it does not carry. The
tag moves to v1.64.0-noble in ci.yml and release.yml, as the note in
dependabot.yml asks.
The lockfile is the union of what the four pull requests resolved. A
plain re-resolve picked vitest 5.0.5 and playwright 1.64.1, newer
than the pull requests, while leaving rolldown behind; it was rebuilt
from #56's lockfile with the vitest set pinned for one install, and
the package set now matches main plus each pull request's changes
exactly. vue moves only as a devDependency of @hexcanvas/vue; its
peer range stays ^3.4.0, and pnpm api reports all five API reports
unchanged.
Local verification
pnpm install --frozen-lockfile— cleanpnpm check— build, typecheck of 7 packages, 16 unit files / 391 tests passpnpm api— all five API reports unchanged;pnpm api:docsbuildspnpm test:browserinsidemcr.microsoft.com/playwright:v1.64.0-noble(amd64 under emulation on Apple silicon): chromium and firefox pass; 4 webkit tests time out at 15s. The same webkit project onmainwith the v1.63.0 image fails 5 tests the same way under the same emulation, so this is emulation speed, not the bump. The native CIbrowserjob is the deciding run.Closes #55
Closes #56
Closes #57
Closes #58