Skip to content

chore(runtime): Node 26 runtime and type cutover (#34) - #91

Merged
jusso-dev merged 6 commits into
mainfrom
chore/node-26-runtime-34
Jul 28, 2026
Merged

chore(runtime): Node 26 runtime and type cutover (#34)#91
jusso-dev merged 6 commits into
mainfrom
chore/node-26-runtime-34

Conversation

@jusso-dev

Copy link
Copy Markdown
Owner

Summary

Closes #34. Full coordinated Node 24 → 26 cutover (not the isolated Dependabot PRs #1 / #8).

Area Before After
Docker build node:24-bookworm-slim node:26-bookworm-slim
Distroless runtime nodejs24-debian13 nodejs26-debian13 (published)
CI + security Node 24 Node 26
Compose mocks Node 24 Node 26
engines.node >=24.0.0 >=26.0.0
@types/node ^24 / 24.13.3 ^26.1.1 + lockfile

Support policy: docs/operations/node-26-upgrade-deferral.md (now the live support policy doc).

Test plan

  • CI quality green on Node 26 (pnpm install --frozen-lockfile, suite)
  • release-security jobs green
  • Local @muster/mcp unit tests still pass under host Node (engine warning only)
  • Do not merge until all required checks are green

Supersedes Dependabot #1 and #8.

Coordinated Node 24 → 26 upgrade for engines, @types/node, CI, Compose
mocks, Docker build image, and distroless runtime. Records support policy
and closes the #34 rollup that Dependabot PRs #1 and #8 could not land alone.
@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@jusso-dev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 744b20df-8451-4584-b5b5-2cb559408228

📥 Commits

Reviewing files that changed from the base of the PR and between 318294f and 2118ddc.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (46)
  • .dockerignore
  • .github/workflows/ci.yml
  • .github/workflows/security.yml
  • CONTRIBUTING.md
  • Dockerfile
  • README.md
  • apps/agent-gateway/package.json
  • apps/mcp-server/package.json
  • apps/web/package.json
  • apps/worker/package.json
  • deploy/docker/docker-compose.homelab.yml
  • docker-compose.yml
  • docs/operations/node-26-upgrade-deferral.md
  • docs/operations/release-homelab.md
  • package.json
  • packages/agent-harness/package.json
  • packages/agents/package.json
  • packages/audit/package.json
  • packages/contracts/package.json
  • packages/database/migrations/0022_messy_proteus.sql
  • packages/database/migrations/0022_operational_knowledge.sql
  • packages/database/migrations/meta/0022_snapshot.json
  • packages/database/migrations/meta/_journal.json
  • packages/database/package.json
  • packages/event-protocol/package.json
  • packages/integrations/package.json
  • packages/mcp/package.json
  • playwright.clean.config.ts
  • playwright.config.ts
  • playwright.homelab.config.ts
  • scripts/generate-screenshots.sh
  • tests/alfie-research.spec.ts
  • tests/clean-install.spec.ts
  • tests/connectors-governance.spec.ts
  • tests/global-setup.ts
  • tests/helpers.ts
  • tests/homelab/critical-product.spec.ts
  • tests/homelab/message-send.spec.ts
  • tests/homelab/real-integrations.spec.ts
  • tests/jessie-hunt.spec.ts
  • tests/messaging.spec.ts
  • tests/muster.spec.ts
  • tests/rooms-governance.spec.ts
  • tests/screenshots.spec.ts
  • tests/slack-settings.spec.ts
  • turbo.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/node-26-runtime-34

Comment @coderabbitai help to get the list of available commands.

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
@jusso-dev

Copy link
Copy Markdown
Owner Author

CI performance changes (this push)

Change Effect
Concurrency cancel-in-progress on PRs New push cancels stale runs
Drop MinIO service from quality ~30–60s + less flake
Turbo .turbo GHA cache Faster lint/typecheck/test/build on warm cache
Single turbo run lint typecheck test build Shared package graph
container parallel with quality Wall-clock ≈ max(quality, image) not sum
Security workflow no longer rebuilds image on PR Removes second full Docker build (was ~4–10+ min)
Dockerfile lockfile-first + BuildKit caches Better layer hits when only code changes
.dockerignore trims tests/docs/node_modules Smaller context upload

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.
@jusso-dev
jusso-dev merged commit 645bc4a into main Jul 28, 2026
8 checks passed
@jusso-dev
jusso-dev deleted the chore/node-26-runtime-34 branch July 28, 2026 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

P1: Plan Node 26 runtime and type-definition upgrade

1 participant