chore(runtime): Node 26 runtime and type cutover (#34) - #91
Conversation
|
Warning Review limit reached
Next review available in: 1 minute Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (46)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Official node:26-bookworm-slim no longer ships corepack on PATH. Replace hand-written migrations 0022/0023 with drizzle-kit output so the committed-migrations CI check stays clean.
Drop browser E2E specs, Playwright configs/deps, and CI steps. Muster is the Hermes MCP control plane; unit/package tests and homelab shell checks remain.
- Cancel in-progress PR runs - Drop MinIO from quality (unit tests mock object storage) - Turbo local cache on GHA - Parallel quality + container (container no longer waits on quality for PRs) - Remove duplicate full image build from security workflow on PR/push (weekly schedule retains deep Trivy pass) - Dockerfile: manifest-first layers + pnpm/turbo BuildKit caches - Tighter .dockerignore for smaller build context
CI performance changes (this push)
PR path: one image build (container) + Trivy there. Weekly schedule still does dedicated security image scan. |
GHA buildx rejects --parents on dockerfile:1.7. Use explicit per-package manifest COPY lines so the lockfile-first layer cache still works.
Summary
Closes #34. Full coordinated Node 24 → 26 cutover (not the isolated Dependabot PRs #1 / #8).
node:24-bookworm-slimnode:26-bookworm-slimnodejs24-debian13nodejs26-debian13(published)engines.node>=24.0.0>=26.0.0@types/node^24/ 24.13.3^26.1.1+ lockfileSupport policy:
docs/operations/node-26-upgrade-deferral.md(now the live support policy doc).Test plan
qualitygreen on Node 26 (pnpm install --frozen-lockfile, suite)release-securityjobs green@muster/mcpunit tests still pass under host Node (engine warning only)Supersedes Dependabot #1 and #8.