Repository navigation
chore(deps-dev): Bump vitest from 2.1.9 to 5.0.1 in /laya-ts - #631
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 2.1.9 to 5.0.1. - [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.1/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
`laya-ts/tests/truncation.test.ts` had the `systemOne reports truncation in usage` describe block pasted into the middle of the `accounting/%s` test's callback, leaving that test's last three assertions orphaned after the block's closing braces. vitest 2 tolerated the nested registration; the file is still malformed. Two consequences, both of which the fix removes: - The suite reported 580 tests. With the block moved out it reports 585, so five cases were registered inside a running test rather than as tests. - One of the five never passed. The stub `runHead` returned a fixed two-wide logit row, and `Agent._systemOneMany` (src/agent.ts:646-655) requires `logitRow.length >= markers.length` per question, so the four-option `choice` in "questions over one state can disagree" failed validation with `model provider returned invalid output for question wide` rather than reaching its assertion. The row is now `[0, 2, 0, 0]`; extra columns are sliced off, so the noul cases still read `[0, 2]` and the other two tests in the block are unaffected. Verified on both vitest versions the repo could be on, since this is also the blocker for #631: 585 passed on vitest 2.1.9 and 585 passed on vitest 5.0.1. `npm run build` clean and the packed end-to-end test passes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Merged, and it found a real bug on the way in, so this one earned its keep beyond the version number. vitest 5 refused That is not a vitest regression. The Two things fell out of fixing the structure, which I landed as its own commit ahead of this merge:
Verified on both versions so the fix is not vitest-5-specific: 585 passing on vitest 2.1.9 and on vitest 5.0.3, with So the bump is in, and the suite now runs five more tests than it did before, one of which was broken. That is a better outcome than a clean bump would have been. Same note as on #633: the |
Bumps vitest from 2.1.9 to 5.0.1.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
03630a5chore: release v5.0.1 (#11275)a47d790fix(fakeTimers): forcequeueMicrotaskandnextTickintoNotFake(#11261)2ce29d5fix: warn when deprecateddeps.optimizer.webis used (#11214)ccd6d05docs: fix typecheck exclude default in documentation (#11223)91ab158fix(doctor): measure vm pools for custom environments (#11212)23dda73fix: share the server on self-referencingextends(#11034)498fbe9fix: resolve ResolvedConfig exactOptionalPropertyTypes errors (#11175)115c3f6fix: correct typos in error message and comments (#11187)7361465fix: keep metadata file when clearing the cache (#11199)972e24bfix(browser): avoid double quotes inconfig.define(#11198)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.
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)