chore(deps): Consolidate Bun workspace dependency bumps#147
Merged
Conversation
Bundle the five mutually-conflicting Dependabot lockfile PRs (#140, #142, #143, #145, #146) into a single root bun.lock regeneration. Dashboard bundle: react-router 7.17.0 -> 8.0.1 (major; the v8 react-router-dom re-export removal does not affect the dashboard, which already imports from react-router) and lucide-react 1.18.0 -> 1.21.0. Dev/build tooling: typescript-eslint 8.61.0 -> 8.61.1 (dashboard + endpoint-manager), @types/node 25.9.3 -> 26.0.0 (dashboard), and vite 8.0.11 -> 8.0.16 (samples/portal-host, the workspace member sync-bun-lock does not watch). No user-facing behaviour change.
This was referenced Jun 22, 2026
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.
Consolidates the five mutually-conflicting Dependabot lockfile PRs into a single root
bun.lockregeneration. All five touch the workspace-rootbun.lock, so merging them individually would force a rebase-and-CI cycle on each survivor; bundling them keeps the lockfile coherent in one pass.Supersedes
vite8.0.11 → 8.0.16(samples/portal-host)lucide-react+typescript-eslint(src/dashboard)@types/node25.9.3 → 26.0.0(src/dashboard)react-router7.17.0 → 8.0.1(src/dashboard)typescript-eslint8.61.0 → 8.61.1(packages/endpoint-manager)Bumps
Dashboard bundle:
react-router7.17.0 → 8.0.1,lucide-react1.18.0 → 1.21.0.Dev / build tooling:
typescript-eslint8.61.0 → 8.61.1(dashboard + endpoint-manager),@types/node25.9.3 → 26.0.0(dashboard),vite8.0.11 → 8.0.16(samples/portal-host).react-router 7 → 8 (major)
The only hard breaking change in v8 is the removal of the
react-router-domre-export. The dashboard already imports everything fromreact-routerand uses the declarative<Routes>/<Route>API (nocreateBrowserRouter/RouterProvider/ loaders), so it is unaffected. Every imported symbol (BrowserRouter,Navigate,Route,Routes,NavLink,Outlet,useNavigate,useLocation,Link,useParams) is still exported and behaviourally unchanged.Security
Resolves both open vite advisories on
samples/portal-host— GHSA-fx2h-pf6j-xcff (high,server.fs.denybypass on Windows alternate paths) and GHSA-v6wh-96g9-6wx3 (medium, launch-editor NTLMv2 hash disclosure) — both patched invite 8.0.16. The vulnerable dependency lives only in the demo sample workspace; it ships in no released artifact (Docker image, NuGet SDK, or dashboard bundle).Why a single hand-rolled lockfile (vs.
samples/portal-hostauto-sync)sync-bun-lock.ymlwatchessrc/dashboard/package.jsonandpackages/*/package.jsonbut notsamples/*, so #140's vite bump never regenerated the root lockfile and died on CI'sbun install --frozen-lockfile. Regenerating once locally covers all members.Verification (local)
bun install --frozen-lockfile— cleanbun run lint,bun run typecheck,bun run build— all pass