Repository navigation
chore(deps,sdk-ts): bump vitest from 4.1.10 to 5.0.0 in /sdk-ts - #252
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.10 to 5.0.0. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
DORA Metrics
|
brownjuly2003-code
pushed a commit
that referenced
this pull request
Sep 8, 2026
Dependabot's PR #252 (Vitest 4 -> 5) reported every check green. Its `sdk-ts` job installed Node 20, Vitest 5 declares `engines.node "^22.12.0 || ^24.0.0 || >=26.0.0"`, and npm resolved that mismatch by printing `npm warn EBADENGINE` and installing anyway. The 50 tests ran, so the required gate said yes to a toolchain the runner's Node does not support. Node 20 itself went end-of-life on 2026-04-30, which makes `engines.node >=20` a floor nobody should be handed. The floor moves to `>=22` -- the same move `0988a0d` made from `>=18`, for the same reason: a declared floor has to be one the toolchain can execute. The required `sdk-ts` job pins 22, `sdk-ts-compat` moves to the next LTS (24), and security.yml's `npm-audit`, which also runs `npm ci` from `sdk-ts/`, comes off 20 with them. `sdk-ts` is a required context in branch protection and keeps its name; `sdk-ts-compat` is not, so the matrix rename costs nothing. `sdk-ts/.npmrc` sets `engine-strict=true`, so the next such mismatch fails the install instead of scrolling past. Measured: with the floor mutated to `>=99`, `npm ci` exits 1 on EBADENGINE; restored, the whole gate -- `npm ci`, typecheck, 50 tests, build, `npm pack --dry-run` -- passes on Node 22.20.0. `tests/unit/test_sdk_ts_node_floor.py` holds the declared floor, the four lanes that run `npm ci` from `sdk-ts/`, and the lockfile's own `engines` copy in step. That copy had already drifted: `0988a0d` raised package.json to `>=20` and left the lock claiming `>=18` until a Dependabot bump happened to rewrite it. Five mutants -- required lane back on 20, compat lane duplicating the floor, `npm-audit` back on 20, stale lock engines, `.npmrc` neutered -- each fail the new tests. Sharded Windows suite on this change: 14/14 shards, 3845/3845 tests, peaks 120.4-433.1 MiB against a 600 MiB budget. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017tNEcJFMjms4uMVwERcT5x
Contributor
Author
|
Looks like vitest is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/sdk-ts/vitest-5.0.0
branch
September 8, 2026 10:04
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.
Bumps vitest from 4.1.10 to 5.0.0.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
f441c6fchore: release v5.0.0 (#11130)d46a747fix: treat test.describe as a suite during static collection (#11128)584cf30fix: add a warning if inline project has duplicate plugins due to unexpected ...f08ce4bfix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)897f51fchore: release v5.0.0-rc.4 (#11107)1339b06chore(deps): update all non-major dependencies (#11104)51e9494feat!: parse files statically in vitest list by default (#11088)2122ffdfix: propagate --maxWorkers to projects (#11102)dc10f5ffix(browser): report the action error when a task times out (#11101)d4fe198feat: promote clearCache out of experimental (#11086)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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)