Repository navigation
chore(deps): bump vitest from 5.0.3 to 5.0.5 - #452
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
dependabot
Bot
added
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
dependabot
Bot
force-pushed
the
dependabot/bun/vitest-5.0.4
branch
5 times, most recently
from
October 17, 2026 21:37
f48ebe9 to
3113def
Compare
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/bun/vitest-5.0.4
branch
11 times, most recently
from
October 21, 2026 13:39
9d06db2 to
ffabc73
Compare
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 5.0.3 to 5.0.5. - [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.5/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.4 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
force-pushed
the
dependabot/bun/vitest-5.0.4
branch
from
October 21, 2026 17:27
ffabc73 to
ccfa6ef
Compare
dbtlr
added a commit
that referenced
this pull request
Oct 24, 2026
…perseding Dependabot #449-#453 (MMR-593) (#514) Five Dependabot PRs (#449 to #453) had sat open for a week, and more updates had piled up behind them: Bun 1.4.4, vite-plus 1.4, and patch releases across the CLI, MCP server, console, and toolchain. This PR lands them all at once. Everything outdated is now on its latest release except Loom. Loom 0.15.0 carries about 40 breaking migrations, which makes it a framework move rather than a bump, so it gets its own task (MMR-594). The security overrides move to the newest release in their current major. `brace-expansion` and `fast-uri` stay on 2.x and 3.x because the overrides force those lines on every consumer. The update surfaced one hidden problem. `@loomcli/core` 0.14.0 declares `@types/node` 22.20.5 as an exact runtime dependency. Once `bun-types` changed, a fresh resolve hoisted that copy over the 25.x line the repo had been using, and type-checking broke in four packages (`ChildProcess.once`, `events.once`, and `node:path`'s `join`). The root now pins `@types/node` 26.6.5, matching Bun 1.4.4's Node 26.3 runtime. The pin is filed upstream as LM-s36. Smaller changes: - oxlint 1.89 flagged two new findings, both fixed in place: a `String.raw` with the identical string value, and a key-order swap. - `bun install` marks every workspace `bin` target executable, so `packages/cli/src/main.ts` is now committed as 100755, matching `packages/bin/src/main.ts`. Without it, every install left the tree dirty. Verification: - `bun run verify` passes: zero warnings, 5,064 bun tests, and 1,069 Vitest tests. - `test:pwa` (2/2) and `test:host` (7/7, including the container build on `oven/bun:1.4.4`) pass. - A compiled `dist/mimir` was smoked in a throwaway directory. Project, initiative, task, start, done, search, seed, and doctor all ran against its own SQLite store. An MCP stdio handshake succeeded, listed 50 tools, and answered `overview`. Supersedes #449, #450, #451, #452, #453. Changes made by Claude Opus 5.5 in Claude Code.
Owner
|
Superseded by #514, which landed this update (or a newer one) on main. |
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 5.0.3 to 5.0.5.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
7a825dbchore: release v5.0.5 (#11609)6621a72fix: abort all running tests on cancel (#11606)e9c3d72fix: release mocks of finished test files (#11607)8dd67c2fix(browser): run global setup once with instances (#11596)6c5a447fix: run hook cleanups when a later hook fails (#11605)9697b38fix: keep the import frame in native loader errors (#11599)6498b66fix(browser): wait 30s for the browser to close (#11601)f161e6dfix(browser): drop late connections of closed sessions (#11600)fe86a64fix: skip builtin loading in async leak detector (#11598)6ae8e89fix(reporter): end reason'failed'on worker crash (#11568)