Skip to content

chore(deps-dev): Bump vitest from 2.1.9 to 5.0.1 in /laya-ts - #631

Merged
NandhaKishorM merged 1 commit into
mainfrom
dependabot/npm_and_yarn/laya-ts/vitest-5.0.1
Oct 1, 2026
Merged

NandhaKishorM merged 1 commit into
mainfrom
dependabot/npm_and_yarn/laya-ts/vitest-5.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 27, 2026

Copy link
Copy Markdown
Contributor

Bumps vitest from 2.1.9 to 5.0.1.

Release notes

Sourced from vitest's releases.

v5.0.1

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v5.0.0

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

... (truncated)

Commits
  • 03630a5 chore: release v5.0.1 (#11275)
  • a47d790 fix(fakeTimers): force queueMicrotask and nextTick in toNotFake (#11261)
  • 2ce29d5 fix: warn when deprecated deps.optimizer.web is used (#11214)
  • ccd6d05 docs: fix typecheck exclude default in documentation (#11223)
  • 91ab158 fix(doctor): measure vm pools for custom environments (#11212)
  • 23dda73 fix: share the server on self-referencing extends (#11034)
  • 498fbe9 fix: resolve ResolvedConfig exactOptionalPropertyTypes errors (#11175)
  • 115c3f6 fix: correct typos in error message and comments (#11187)
  • 7361465 fix: keep metadata file when clearing the cache (#11199)
  • 972e24b fix(browser): avoid double quotes in config.define (#11198)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.


Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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>
@dependabot @github

dependabot Bot commented on behalf of github Sep 27, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

NandhaKishorM added a commit that referenced this pull request Oct 1, 2026
`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>
@NandhaKishorM
NandhaKishorM merged commit e525557 into main Oct 1, 2026
19 of 21 checks passed
@NandhaKishorM

Copy link
Copy Markdown
Owner

Merged, and it found a real bug on the way in, so this one earned its keep beyond the version number.

vitest 5 refused tests/truncation.test.ts:

FAIL tests/truncation.test.ts > reported counts match the sequence > accounting/512
Error: Calling the suite function inside test function is not allowed.

That is not a vitest regression. The systemOne reports truncation in usage describe block had been 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 and the file has been malformed on main for some time.

Two things fell out of fixing the structure, which I landed as its own commit ahead of this merge:

  • Five tests were not being counted. The suite reported 580; with the block moved out it reports 585.
  • One of them had never passed. The stub runHead returned a fixed two-wide logit row, and Agent._systemOneMany requires logitRow.length >= markers.length per question, so the four-option choice in "questions over one state can disagree" died with model provider returned invalid output for question wide before 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 tests in the block are unchanged.

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 npm run build clean and the packed end-to-end test passing.

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 dependencies label in dependabot.yml does not exist in this repo, hence the label warning on every Dependabot PR.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/laya-ts/vitest-5.0.1 branch October 1, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant