Skip to content

chore(deps-dev): bump vitest from 4.1.10 to 5.0.1 - #58

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

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

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 20, 2026 •
edited by amitpaz1
Loading

Copy link
Copy Markdown
Contributor

Bumps vitest from 4.1.10 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

agentrig-train-row:55a31290-169c-48c8-bfe6-801b211bb1e2

Summary — TASK101 Vitest 5 validation

Validate existing Dependabot Vitest 4.1.10 → 5.0.1 update without speculative migration edits. Existing pushed head 17860b7, main/parent 9aa1c26. No new commit, manual refresh, lock regeneration or push was needed. Only package.json, package-lock.json and pnpm-lock.yaml differ from main; no source, tests, assertions, snapshots or production engines changed.

Adoption / predecessor evidence

Entry pin OLD 3bcf1db → supplied observed 252290a → freshly verified NEW 17860b7. Target remains Vitest 5.0.1, original major update class unchanged. Fresh PR inventory shows a sole dependabot[bot] authored commit (GitHub committer) atop accepted main. Complete entry-to-current and observed-to-current deltas inspected and retained: only lock reconciliation of accepted predecessor types/tsx/yaml/Inquirer/Zod closures; observed-to-current is Inquirer/Zod reconciliation. Complete main-to-head diff is Vitest and its development dependency/peer closure. No unknown author or unrelated source movement. All stale-head receipts/reviews are invalidated, not carried as current-head proof. Head rechecked unchanged before ledger write; no Dependabot race or manual refresh.

Accepted predecessor queue #60, #52, #59, #57, #61 is merged. Preserve #61 evidence: both managers 88 tests/16 files, interactive PTYs/config probes, and both independent PASS reviews, plus main CI https://github.com/agentkitai/agentkit-cli/actions/runs/36239524914 on 9aa1c26 as freshly checked by conductor at dispatch. Full PR61 body re-fetched into predecessor.json. No predecessor review is claimed to cover this Vitest update.

Design decisions / migration inventory

  • No demonstrated migration: retain current tests/config unchanged. Upstream migration guide https://vitest.dev/guide/migration.html fetched and inspected (saved migration.html; current docs display 5.0.2; installed manifests are authoritative for this 5.0.1 head).
  • Exact Vitest engine is ^22.12.0 || ^24.0.0 || >=26.0.0, not simply every Node >=22. Node20, Node22.0 and Node25 fail that range; Node22.12 passes. Node22.23.1, Node24.21.0, Node26.5.0 were actually executed. Production package has no engines field and none was added.
  • Vite is now an automatically installed required peer: range ^6.4.0 || ^7.0.0 || ^8.0.0. npm resolves Vite8.3.0; pnpm resolves Vite8.0.16. Both Vite engines are ^20.19.0 || >=22.12.0. All 379 declared engine ranges across both lockfiles satisfy each tested runtime. Locks have identical direct versions/specifiers and Vitest target, not identical transitive graphs; their preexisting manager-specific Vite resolution differs and remains compatible. No speculative graph homogenization or hand-splicing. Production npm package records and all non-Vitest accepted direct versions equal main.
  • clearMocks defaults true in v5. Doctor/status already clear calls before each test and establish implementations per case. The three mock.calls readers (audit, evidence, doctor) inspect calls from their own test, not prior tests or beforeAll. No opt-out needed; do not weaken isolation.
  • Four vi.mock calls (doctor twice, status, init) are module-top-level factories. No nested vi.mock/unmock/hoisted calls, no hoisting edit required. Module imports succeed in all six runs.
  • Four async assertions (MCP twice, stack MCP, status) are explicitly awaited, including multiline MCP expect. No unawaited resolves/rejects/file-snapshot assertions; v5 full runs pass without async assertion warnings.
  • No removed sequential/bench APIs or deprecated Vitest entrypoints; imports use vitest and vitest/config. No custom matchers, browser/DOM/locator APIs, custom environments/reporters/pools, coverage configuration, projects, worker-ID assumptions or fake timer/Temporal use. Config has only globals:true and root:'.'; invocation remains at project root.
  • Baseline PR61 and all six current-head runs: 88 passed tests /16 files, no skipped tests. Snapshot inventory: zero before and after; no inline/file snapshot assertions or snapshot files. Tests/config/src are byte-identical to main. No relaxed assertion, update-snapshot mode or changed discovery.

Declared checks / verification

Resolved with trusted /Users/amit/agentrig/packages/cli/dist/project-checks.js → resolveProjectChecks(explicit repository root), no selected profile. Repository has no tracked declaration; explicit registered fallback is /Users/amit/.agentrig/projects/d9bd3b23f875084481332b6afc285bad180de775059e3665b33cc0775a0bd5ff/config.json (packs.ship.checks, normalized by resolver). Resolved commands saved in checks.json and displayed before execution. Declared order bootstrap → build → test; no preflight declared. Independent conductor checks/reviews still required.

Durable full logs, receipts.jsonl, checks.json, run.py, compatibility.cjs/log, complete diffs and predecessor/head inventories: /Users/amit/.agentrig/task-evidence/pr58-6a8bb5f7/ (outside scratch and retained). Every following receipt is bound to exact head 17860b7, runner darwin-arm64, owned detached validation worktree /Users/amit/.agentrig/worktrees/pr58-6a8bb5f7, TMPDIR /tmp/pr58-6a8bb5f7. No edits required attaching a writable branch. Node22 PATH /opt/homebrew/opt/node@22/bin; Node24 PATH /Users/amit/.npm/_npx/387698761821791d/node_modules/node/bin; Node26 PATH /opt/homebrew/opt/node@26/bin. npm10.9.8 on 22/24, npm version on 26 recorded in npm26-install.log; pnpm10.34.5. Test commands are unmodified project scripts; install commands remove node_modules between managers/runtime cells. Bootstrap starts from absent node_modules. Full suites run in joined background job job-1, exit0.

Named receipt Exact command (runtime PATH above) UTC start → end Exit Counts
bootstrap export PATH=/opt/homebrew/opt/node@22/bin:$PATH; node --version && npm --version && npx --yes pnpm@10 --version && npx --yes pnpm@10 install --frozen-lockfile 2026-09-26T11:46:35.769782+00:00 → 2026-09-26T11:46:38.630487+00:00 0 N/A
build export PATH=/opt/homebrew/opt/node@22/bin:$PATH; npx --yes pnpm@10 run build 2026-09-26T11:46:38.644684+00:00 → 2026-09-26T11:46:41.193036+00:00 0 N/A
test export PATH=/opt/homebrew/opt/node@22/bin:$PATH; npx --yes pnpm@10 test 2026-09-26T11:46:41.206536+00:00 → 2026-09-26T11:46:43.736226+00:00 0 88 tests / 16 files
pnpm22-resolution node -e 'for(const n of ["vitest","vite"]){const p=require(require.resolve(n+"/package.json",{paths:[require.resolve("vitest")]}));console.log(n,p.version,p.engines,p.peerDependencies?.vite)}' 2026-09-26T11:46:43.750370+00:00 → 2026-09-26T11:46:43.832359+00:00 0 N/A
npm22-install rm -rf node_modules && npm ci --engine-strict 2026-09-26T11:46:43.846531+00:00 → 2026-09-26T11:46:46.998956+00:00 0 N/A
npm22-build npm run build 2026-09-26T11:46:47.013256+00:00 → 2026-09-26T11:46:48.454143+00:00 0 N/A
npm22-test npm test 2026-09-26T11:46:48.469640+00:00 → 2026-09-26T11:46:49.949129+00:00 0 88 tests / 16 files
npm22-resolution node -e 'for(const n of ["vitest","vite"]){const p=require(n+"/package.json");console.log(n,p.version,p.engines,p.peerDependencies?.vite)}' 2026-09-26T11:46:49.963944+00:00 → 2026-09-26T11:46:50.042752+00:00 0 N/A
node24-locate npx --yes --package=node@24 -- node -p process.execPath 2026-09-26T11:46:50.056672+00:00 → 2026-09-26T11:46:54.826506+00:00 0 N/A
npm24-install node --version && npm --version && rm -rf node_modules && npm ci --engine-strict 2026-09-26T11:46:54.840896+00:00 → 2026-09-26T11:46:56.989143+00:00 0 N/A
npm24-build npm run build 2026-09-26T11:46:57.002936+00:00 → 2026-09-26T11:46:58.313894+00:00 0 N/A
npm24-test npm test 2026-09-26T11:46:58.329508+00:00 → 2026-09-26T11:46:59.579842+00:00 0 88 tests / 16 files
pnpm24-install rm -rf node_modules && npx --yes pnpm@10 install --frozen-lockfile --config.engine-strict=true 2026-09-26T11:46:59.594352+00:00 → 2026-09-26T11:47:01.501307+00:00 0 N/A
pnpm24-build npx --yes pnpm@10 run build 2026-09-26T11:47:01.515711+00:00 → 2026-09-26T11:47:03.657064+00:00 0 N/A
pnpm24-test npx --yes pnpm@10 test 2026-09-26T11:47:03.670971+00:00 → 2026-09-26T11:47:05.766445+00:00 0 88 tests / 16 files
npm26-install node --version && npm --version && rm -rf node_modules && npm ci --engine-strict 2026-09-26T11:47:05.780518+00:00 → 2026-09-26T11:47:07.789653+00:00 0 N/A
npm26-build npm run build 2026-09-26T11:47:07.804157+00:00 → 2026-09-26T11:47:09.176002+00:00 0 N/A
npm26-test npm test 2026-09-26T11:47:09.191049+00:00 → 2026-09-26T11:47:10.465197+00:00 0 88 tests / 16 files
pnpm26-install rm -rf node_modules && npx --yes pnpm@10 install --frozen-lockfile --config.engine-strict=true 2026-09-26T11:47:10.479476+00:00 → 2026-09-26T11:47:12.927675+00:00 0 N/A
pnpm26-build npx --yes pnpm@10 run build 2026-09-26T11:47:12.941610+00:00 → 2026-09-26T11:47:15.659241+00:00 0 N/A
pnpm26-test npx --yes pnpm@10 test 2026-09-26T11:47:15.673073+00:00 → 2026-09-26T11:47:18.343823+00:00 0 88 tests / 16 files
final-state git diff --exit-code && git diff --cached --exit-code && git status --porcelain 2026-09-26T11:47:18.357831+00:00 → 2026-09-26T11:47:18.404637+00:00 0 N/A
compatibility node /Users/amit/.agentrig/task-evidence/pr58-6a8bb5f7/compatibility.cjs 2026-09-26T11:48:50.737572+00:00 → 2026-09-26T11:48:50.939335+00:00 0 379 engine ranges; 10 direct deps; 16 test files

All receipts exit0. No mutation/fail-first claim: no new source behavior, tests, guards or refusals introduced. Existing assertions plus dependency/engine/static compatibility inventory are migration proof. No touched skill/instruction-contract text, so CRLF skill-copy tests are not applicable.

Warnings retained, not hidden: pnpm's default ignored esbuild build-script warning; no approval/config override, native toolchain still builds/tests. npm Vite8.3 reports current ESM syntax in CommonJS vitest.config.ts would be unsupported by a future default native config loader. Current default loads correctly on all tested runtimes. No speculative rename/module-type change or warning suppression for a future Vite major.

Security / audit

Optional explicit npm audit main/head comparison was not run, so no audit non-regression claim is made. npm ci automatically reported baseline dependency vulnerabilities; install output retained in full, not a clean-audit certification. No audit fix or unrelated dependency update. Image scanning not applicable: no image build, Dockerfile or image-reference change.

Deviations

None. Validation-only adoption permitted explicitly when no migration is demonstrated. Scope takes precedence over generic STATUS/ROADMAP edits; those files are absent and no out-of-scope docs created. Both managers and supported tooling runtime majors22/24/26 exercised; unsupported Node20/25 not falsely certified.

Review disposition

Repair round: 0/3
Fresh adoption inventory has no existing comments/reviews/findings. Independent review pending; child skips external reviews and does not approve or merge. Conductor owns same-head independent checks and declared reviewer slots. No stale-head coverage retained. Hosted CI observed SUCCESS without waiting: https://github.com/agentkitai/agentkit-cli/actions/runs/36239659860/job/108397659372, test started 2026-09-26T11:42:29Z and completed 2026-09-26T11:42:51Z on this current head. Lander must reverify actual head and all gates.

Residuals

No demonstrated migration defect or test failure. Known nonblocking future-native-loader warning disclosed above; no current incompatibility proven. No audit comparison claimed. Independent review/landing gates outstanding; no issues, approvals, settings, credentials, publications, deployments or tags mutated.

Checklist

  1. Addressed: no source behavior/docs/skill contracts changed; dev dependency migration requires no demonstrated docs/config change.
  2. N/A: no parser/matcher implementation replaced.
  3. N/A: no new branch/guard/refusal; no fictitious mutant receipt.
  4. Addressed: all tests, Vitest imports, hoisted mocks, mock-history consumers, async assertions and config inspected; both locks/direct dependency specifiers verified.
  5. Addressed: row marker, ship ledger, round0/3, receipt table and Residuals recorded. STATUS/ROADMAP absent and outside task scope.
  6. Addressed: exact engines, mock semantics, removed APIs, async awaits, all supported tooling runtime majors and both clean managers validated without skipped tests/speculative edits. Optional audit explicitly not claimed.
  7. Addressed: entire API-use inventory and both dependency graphs checked, not one cited test.
  8. Addressed: tests/config/src unchanged; no safety gate, error path or assertion relaxed. Production dependency records unchanged.
  9. N/A: no new inputs or name/value validation logic introduced; existing regression assertions retained.
  10. Addressed: proof scoped to PR58/current head, predecessor evidence separately identified.
  11. Addressed: engine/manifest consistency script asserts and fails on mismatch; no malformed evidence accepted. No product input parsing changed.
  12. Addressed: exact full OLD/observed/NEW/main SHAs and PR/origin/bot identity compared. Stale receipts invalidated; all current proof bound to unchanged head.

Authorization and child boundary

Verbatim human authorization, bound solely to PR58; child must not merge:

For agentkitai/agentkit-cli, Amit authorizes scoped validation, necessary migration edits and sequential merging of PRs #58 only. Only these named PRs may be refreshed for accepted predecessors; no replacement PR or unrelated repository work is authorized. Merge only after every required check is green on that exact head, the row's own tests/validation passed, and there are no unresolved blocking review comments, using the merge guard's standard squash merge pinned to the verified head SHA, with the squash subject/body the land skill requires (as PR #60 in agentkit-cli was landed); never with the admin override; branch protection requires no approving review. Amit authorized merging from his account (amitpaz1); required approving reviews are 0 on main. No approval action or settings change is authorized.

Handoff and cleanup

Existing pushed PR58 ready for conductor independent proof/review, not a landing certification. No source edits, commits or push necessary. All jobs joined; tracked/index/status clean. Durable proof persisted outside scratch. After this append-only ledger is persisted/read back, remove the owned validation worktree with git worktree remove and its external TMPDIR; preserve author checkout and durable proof. No hosted CI waiting, external reviews or merge by child.

Cleanup confirmation — 2026-09-26T11:51:32.602693+00:00

Ledger exact-byte readback and head equality passed. All jobs joined; clean owned worktree removed with git worktree remove, registration pruned, external TMPDIR removed and absence verified. Author checkout remains clean on main9aa1c261ea376d67161b473cfb6e6197244eda00. Durable proof retained. No commit/push needed for validation-only adoption. npm26 used npm12.0.2; Node22/24 used npm10.9.8. Child handoff complete; independent review remains pending.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 20, 2026
@dependabot
dependabot Bot requested a review from amitpaz1 as a code owner September 20, 2026 04:43
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 20, 2026
@dependabot dependabot Bot mentioned this pull request Sep 20, 2026
Closed
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/vitest-5.0.1 branch 2 times, most recently from e44a811 to 51f1158 Compare September 26, 2026 10:01
@amitpaz1 amitpaz1 mentioned this pull request Sep 26, 2026
Merged
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/vitest-5.0.1 branch from 51f1158 to 252290a Compare September 26, 2026 10:28
@dependabot
chore(deps-dev): bump vitest from 4.1.10 to 5.0.1
17860b7 
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.10 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
dependabot Bot force-pushed the dependabot/npm_and_yarn/vitest-5.0.1 branch from 252290a to 17860b7 Compare September 26, 2026 11:42
@dependabot @github

dependabot Bot commented on behalf of github Oct 4, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #66.

@dependabot dependabot Bot closed this Oct 4, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/vitest-5.0.1 branch October 4, 2026 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@amitpaz1 amitpaz1 Awaiting requested review from amitpaz1 amitpaz1 is a code owner

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants