Skip to content

chore(deps)(deps-dev): bump vitest from 4.1.11 to 5.0.2 - #21032

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest-5.0.2
Closed

chore(deps)(deps-dev): bump vitest from 4.1.11 to 5.0.2#21032
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest-5.0.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps vitest from 4.1.11 to 5.0.2.

Release notes

Sourced from vitest's releases.

v5.0.2

   🐞 Bug Fixes

    View changes on GitHub

v5.0.1

   🚀 Features

   🐞 Bug Fixes

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 1, 2026
@github-actions github-actions Bot added the size/m label Oct 1, 2026
@github-actions

github-actions Bot commented Oct 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 9b81314c29f7339d564f1025e217ac931beb7e5e → packageMentionDocs.

This was referenced Oct 1, 2026
Closed
Merged
@dependabot
chore(deps)(deps-dev): bump vitest from 4.1.11 to 5.0.2
3fa1cf9 
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.11 to 5.0.2.
- [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.2/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 5.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/vitest-5.0.2 branch from fad625d to 3fa1cf9 Compare October 1, 2026 06:30
@objectstack-fleet

objectstack-fleet Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Closed 2026-10-01T08:01Z on the maintainer's instruction: the vitest 5 major is deferred for now.

Provenance:

  • Who: the maintainer.
  • Verbatim: 「三组大版本升级:同意 * vitest:关两个 PR,先放着(推荐)。」
  • Where: PM seat session session_018gA1pE6eJtwHhqx72G8U9X, 2026-10-01.

Recorded for whoever lifts it later. These are measured on this PR's CI and on its sibling #21030, which must land together with it because @vitest/coverage-v8 pins vitest exactly:

  • The bench export was removed. packages/spec/src/benchmark.bench.ts and packages/objectql/src/engine-data-events.bench.ts import it. Type Check · source gates failed with TS2724.
  • Nested vi.mock calls are now an error. There are two in metadata.test.ts.
  • An unawaited .resolves now fails the test (memory-driver.test.ts).
  • The vitest-filter preflight reports "vitest's bundle shape changed" (project-cli-override-preflight).
  • Twenty packages were never reached across Test Core shards 1, 2 and 6.
  • The published @objectstack/metadata-core peer "vitest": "^4.0.0" would need widening, with a changeset.

Generated by Claude Code

@objectstack-fleet objectstack-fleet Bot closed this Oct 1, 2026
@dependabot @github

dependabot Bot commented on behalf of github Oct 1, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/vitest-5.0.2 branch October 1, 2026 08:02
@objectstack-fleet objectstack-fleet Bot mentioned this pull request Oct 1, 2026
Closed
akarma-synetal pushed a commit to akarma-synetal/framework that referenced this pull request Oct 7, 2026
@objectstack-fleet @claude
ci(dogfood): carry the shard slice in a task env so the dogfood test …
e0c768f 
…hash sees its upstream closure (objectstack-ai#21074)

Fixes objectstack-ai#20820

Clause-②: no

## What

The required `Dogfood Regression Gate (k/3)` leg ran `turbo run test
--filter=@objectstack/dogfood --only -- --shard=k/3`. `--only` drops the
`^build` closure out of the `dogfood#test` hash, so a PR that changed
only an upstream package could match a main-seeded cache entry and be
replayed green. This ports objectstack-ai#19278's shape to the dogfood leg:

- `turbo.json`: `@objectstack/dogfood#test` now declares `OS_TEST_SHARD`
in its `env`. The shared `test` task already declares it (objectstack-ai#20824), but a
per-package task entry REPLACES the shared entry's `env` instead of
extending it, so the shared declaration did not cover dogfood: measured,
the pre-change plan listed only `OS_TEST_TIERS` for that task.
- `packages/qa/dogfood/vitest.config.ts`: reads
`process.env.OS_TEST_SHARD` into the root `test.shard` (same spelling as
`packages/cli/vitest.config.ts`).
- `.github/workflows/ci.yml`: the leg exports `OS_TEST_SHARD="k/3"` and
runs `pnpm turbo run test --filter=@objectstack/dogfood
--log-order=stream`: no `--`, no `--only`, no `--force`. Stall guard,
`dogfood.log` tee, `NODE_OPTIONS` / `--report-dir`, cache restore/save
are untouched. The step's comment states the new mechanism.

Also touched (comment only, one deviation from the card's file surface,
flagged): the comment of the preceding closure-build step said it exists
"so that the sharded run in the next step can be `--only`", which is now
false; it now says so. The step itself is unchanged.

No second shard mechanism. `scripts/measure-test-shard-timings.mjs` /
`partition-test-shards.mjs` / `report-test-timings.mjs` are untouched:
the dogfood leg passes no `--summarize` and has no timings consumer, so
there is nothing to reuse or change.

## Measurements

turbo 2.10.10 dry-runs (`--dry=json`) and real vitest runs, in this
worktree at head 55bd9e0.

Pin 1, hash moves (shard 1/3, edit = append a comment line to the file,
restored from HEAD after):

| leg | clean | + `packages/objectql/src/index.ts` |
|---|---|---|
| old (`--only -- --shard=1/3`) | a963b53363c79e20 | a963b53363c79e20
(unchanged: the defect) |
| new, pre-build tree | d6f169ed1431553e | 2ee13c0afd852c96 (moves) |
| new, post-build tree | bd114335fad78510 | 55dc2dd1da35f8e0 (moves) |

The pre-build and post-build clean hashes differ (d6f169ed vs bd114335);
I did not isolate why (suspect built output under the
`examples/app-showcase/**` input). Each row's before/after is on one
tree.

Pin 2, lit control (post-build tree, shard 1/3, clean bd114335fad78510):

- `packages/client-react/src/index.tsx` (a workspace package NOT in the
dogfood closure, checked against the plan): bd114335fad78510, unchanged.
- `packages/qa/dogfood/test/action-params-contract.dogfood.test.ts`
(dogfood-internal): a5dc81d7aadebe29, moves.

Pin 3, shards differ: post-build 1/3 bd114335fad78510, 2/3
0387e6b5b568a93c, 3/3 d3b158ab11f62582; pre-build d6f169ed1431553e /
fd1f57f4bbe9537f / bc48cac953e838cc. Pins 1 to 3 are dry-run hash
readings, not executions.

Pin 4, the shard is honoured: vitest 4.1.11 (lockfile). Real
`OS_TEST_SHARD=k/3 vitest run` in `packages/qa/dogfood` ran 50 / 49 / 49
test files (148 in total, 148 in the union, 0 overlap between any two
shards), 0 failed in each. `vitest list --filesOnly` is NOT a valid
measure of this: it prints all 148 files for any shard, even with
`--shard=1/3` on the command line. objectstack-ai#21032's vitest 5.0.2 is NOT
MEASURED; the env-read shape is the one `packages/cli/vitest.config.ts`
already uses, so the dogfood read breaks together with it if a vitest
line stops honouring `test.shard`.

Plan cost of dropping `--only` (`OS_TEST_SHARD=1/3 turbo run test
--filter=@objectstack/dogfood --dry=json`): 66 tasks. Against the cache
the step above fills: 63 HIT / 3 MISS (the test, plus two `#build` nodes
of packages with no `build` script, which never execute); cold cache: 66
MISS. The leg's 65 `build` hashes are identical to `turbo run build
--filter=@objectstack/dogfood`'s plan (65 same, 0 differ, 0 missing), so
the closure replays rather than rebuilds. The old leg planned 1 task.

Pin 5, nothing is replayed green: a replay needs an equal `dogfood#test`
hash. That hash now carries the shard value (pin 3), the upstream
closure (pin 1) and the package's own files (pin 2), the control shows
it is not moving on everything, and pin 4 shows the shard value is what
selects the files that execute. NOT MEASURED: an end-to-end executed
replay across an upstream edit on the new leg.

## Gates

`node scripts/pm/dispatch-gates.mjs --commands`: 79 derived; 78 run, all
exit 0, recorded with `--ran`. `pnpm check:dual-build-cjs-loads` exited
3 (PREREQUISITE NOT MET: `Run pnpm build first`, nothing measured), so
it is NOT MEASURED; the diff changes no built output. `pnpm --filter
@objectstack/dogfood typecheck` exit 0, but that program does not
compile `vitest.config.ts` (0 hits in `tsc --listFiles`), so the
`satisfies` clause is checked only by vitest loading the file.
actionlint is not installed here: NOT MEASURED; `ci.yml` parses as YAML
and `turbo.json` as JSON.

## Changeset

None. `@objectstack/dogfood` is `"private": true`, and `ci.yml` /
`turbo.json` ship in no package's `files[]`.

## Acceptance notes

None beyond the above.

---
🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01VDtqoecgES7ScQYGbFVDRv

---------

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code size/m

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants