v0.36.0

Release Notes

Latest Release: v0.36.0 (June 16, 2026)

Empty-Workspace Evidence Parity and Governance Hardening

This patch release aligns CLI evidence with Workspai dashboard expectations: empty workspaces stay actionable instead of blocked, autopilot and workspace-run artifacts use stable paths, and mirror/intelligence reports carry the metadata extensions need to render governance cards without gaps.

What's New:

• 🚀 Autopilot evidence alias

  • Writes autopilot-release-last-run.json (canonical) and autopilot-release.json (dashboard/--output alias).
  • Adds enterpriseControls and artifacts.aliasEvidencePath.

• 🏃 Workspace run evidence

  • enterpriseControls.evidencePath on workspace-run-last.json.

• 📋 Bootstrap transparency

  • profile_requested and bootstrap_note in workspace.json when create falls back from Python-dependent profiles.

• 🪞 Mirror inventory

  • mirror-ops.latest.json payloads include config/lock/artifact counts.

Improvements:

• Analyze — zero projects → warn, not fail; scaffold-first next actions.
• Impact — empty-workspace git/validation noise softened across profiles.
• Readiness — workspace-scoped Python env gate when no projects registered.
• Workspace run — --strict respects skipped gates; empty runs exit cleanly.

Upgrade:

npm install -g rapidkit@0.36.0

📖 Full Release Notes

v0.35.0

Release Notes

Latest Release: v0.35.0 (June 16, 2026)

Adoption, Frontend Scaffold, and Workspace Intelligence

This release adds in-place project adoption, official create frontend generators, and workspace intelligence commands (model, context, snapshot, verify, diff, impact) so teams can govern polyglot workspaces from the CLI alone.

What's New:

• 🔗 rapidkit adopt

  • Link existing local projects into a workspace without moving source files.
  • Adoption metadata at .rapidkit/adopt.json and .rapidkit/adopt-readiness.json.

• 🎨 rapidkit create frontend

  • Official generators for Next.js, Remix, Vite variants, Nuxt, Angular, Astro, and SvelteKit.
  • Non-interactive flags for extension and CI scaffold flows.

• 🧠 Workspace intelligence

  • workspace model, context, snapshot, verify, diff, and impact with JSON contracts.
  • Registry/contract sync includes adopted and imported external projects.

• 🩺 Doctor and detection

  • Frontend framework probes and richer project-scoped evidence.
  • Improved Node framework detection before generic fallbacks.

• 🏗️ Enterprise / polyglot

  • Expanded infra stack catalog, lifecycle probes, and runtime executor coverage.

Upgrade:

npm install -g rapidkit@0.35.0

📖 Full Release Notes

v0.34.0

Release Notes

Latest Release: v0.34.0 (June 14, 2026)

CLI Governance Pipeline and Enterprise Release Gates

This minor release completes the npm-wrapper governance loop so teams can run bootstrap → sync → doctor → analyze → readiness → autopilot entirely from the CLI, without depending on the VS Code extension for verify evidence.

What's New:

• 🔗 rapidkit pipeline

  • One command runs sync, doctor, analyze, readiness, and autopilot audit.
  • Writes .rapidkit/reports/pipeline-last-run.json with stage verdicts and exit codes.
  • Flags: --json, --strict, --skip-verify, --skip-analyze, --skip-autopilot.

• 🩺 Doctor CI gates

  • --strict: exit 1 on errors or warnings.
  • --ci: exit 1 on errors, exit 2 on warnings.

• 🚦 Readiness improvements

  • New analyze gate reads analyze-last-run.json.
  • Verify gate falls back to CLI workspace contract verify when extension artifacts are absent.
  • --skip-verify for pipelines that verify elsewhere.

• 🚀 Bootstrap and sync

  • Post-success bootstrap auto-syncs registry + contract.
  • --compliance-only with --json for compliance-only CI (skips init).
  • workspace sync --json for machine-readable registry sync output.

• 🤖 Autopilot

  • Adds analyze stage between doctor and readiness.
  • Uses doctor --ci / --strict based on mode.

Upgrade:

npm install -g rapidkit@0.34.0

📖 Full Release Notes

v0.33.2

Release Notes

Latest Release: v0.33.2 (June 12, 2026)

Windows Workspace Launcher and Core Resolver Hardening

This patch makes global, npx, and workspace-local command flows behave consistently when RapidKit Core is installed inside a workspace, via pipx/user-local locations, or behind a generated workspace launcher.

What's Fixed:

• 🪟 Windows launcher shadowing

  • Generated rapidkit.cmd launchers now forward to a non-local npm wrapper when the workspace virtualenv is missing.
  • Forwarded calls set RAPIDKIT_LOCAL_LAUNCHER_BYPASS=1 so the npm wrapper cannot recurse back into the same local launcher.

• 🧭 Workspace-local Core discovery

  • The npm bridge now detects workspace Core installs from both default .venv paths and .rapidkit-workspace metadata.python.venvPath.
  • Workspace Python version metadata is honored from the marker when available.

• 🐍 User-local / pipx fallback

  • The bridge now scans deterministic user-local Core launcher paths even when pipx/Python script directories are not on PATH.
  • Generated launchers fall back to user-local Core executables after checking the npm wrapper path.

• ✅ Regression coverage

  • Added Windows launcher, POSIX launcher, user-local Core, workspace marker, and multi-OS resolver coverage.
  • The Windows bridge E2E workflow now runs the focused resolver regression suite before native smoke tests.

Upgrade:

npm install -g rapidkit@0.33.2

📖 Full Release Notes

v0.33.1

Release Notes

Latest Release: v0.33.1 (June 10, 2026)

Core Bridge Forwarding Fix for Module Lifecycle and --dry-run

This patch fixes npm-to-core command routing so module maintenance and dry-run previews reach Python core reliably, while workspace create/import flows stay on the npm wrapper.

What's Fixed:

• 🔁 Module lifecycle forwarding

  • rollback, uninstall, upgrade, diff, and checkpoint now forward to core even when --dry-run is present.
  • Prevents silent no-op behavior from the Workspai dashboard and terminal maintenance flows.

• 🧭 Workspace vs core boundary

  • Bare workspace names like my-workspace --dry-run no longer mis-route to Python core.
  • create workspace, create project, and npm-owned generator flows remain on the wrapper.

• 🐍 Python context delegation

  • In-project delegation now covers pip, poetry, venv, pipx, and python engines — not pip alone.

Upgrade:

npm install -g rapidkit@0.33.1

📖 Full Release Notes

v0.33.0

Release Notes

Latest Release: v0.33.0 (June 10, 2026)

Workspace Infra Sidecar, Module Layout Contract, and Foundation Ensure

This minor release adds contract-driven local dev infrastructure for polyglot workspaces, canonical module layout verification, and a foundation ensure command for workspace governance files.

What's New:

• 🐳 Infra sidecar (rapidkit infra)

  • plan discovers Postgres, Redis, Mailpit, MinIO, and related services from modules, .env.example, workspace contract env, and overrides.
  • up|down|status manage a generated stack at .rapidkit/infra/docker-compose.yml without touching the workspace's main compose file.
  • Emits .rapidkit/reports/infra-plan.json and connection env previews aligned with project defaults.

• 📐 Module layout contract

  • Added contracts/module-layout.v1.json and doctor workspace module-path audits.
  • workspace contract verify --strict --module-paths checks canonical src/modules/free/ placement.

• 🧱 Workspace foundation ensure

  • npx rapidkit workspace foundation ensure reconciles workspace.json, policies, toolchain lock, and foundation artifacts.

• 🪺 NestJS kit alignment

  • NestJS standard templates now use the canonical module root and TS path mapping expected by Core modules.

Upgrade:

npm install -g rapidkit@0.33.0

📖 Full Release Notes

v0.32.2

Release Notes

Latest Release: v0.32.2 (June 8, 2026)

Multi-OS Workspace Init and Deterministic Package Release Hardening

This patch closes first-use reliability gaps across Linux, macOS, and Windows. It improves Python bridge selection when the default interpreter is incomplete, keeps mixed-runtime workspace initialization moving when an optional runtime is missing, and makes package/release scripts deterministic without Unix-only shell assumptions.

What's New:

• 🧩 Mixed-runtime workspace init reliability

  • workspace run init now continues across remaining projects when an extended-runtime project, such as .NET, cannot initialize because its SDK is missing.
  • FastAPI and NestJS projects in the same workspace are no longer skipped just because another runtime needs setup.
  • Added regression coverage for mixed workspace initialization.

• 🐍 Python bridge fallback hardening

  • The bridge now tries explicit Python overrides, local core virtual environments, versioned Python commands, and platform defaults before failing.
  • If one Python command exists but cannot create a virtual environment, RapidKit falls through to the next valid interpreter.
  • Release scripts now probe real venv support before selecting Python.

• 📦 Cross-platform release scripts

  • Replaced Unix-only npm scripts with Node wrappers for drift guard, scenario matrix execution, and distribution size reporting.
  • npm pack --json now remains parseable when Husky is disabled.
  • prepack validates the committed embeddings artifact offline instead of depending on npx downloads during release.

• 🔷 ASP.NET scaffold stability

  • Generated ASP.NET projects now suppress missing XML documentation warnings while keeping other warnings as errors.
  • The generated dev launcher now uses stable dotnet run behavior across Linux, macOS, and Windows.

Upgrade:

npm install -g rapidkit@0.32.2

📖 Full Release Notes

v0.32.1

Release Notes

Latest Release: v0.32.1 (June 8, 2026)

Runtime Command Surface Parity and Windows Go Launcher Hardening

This patch closes a product-surface drift gap between the npm CLI and companion tooling by adding a shared runtime command contract. It also hardens generated Go workspace launchers on Windows so users can run project lifecycle commands without requiring GNU Make.

What's New:

• 🧭 Runtime command surface contract

  • Added a shared contract for lifecycle commands, module mutation commands, global commands, scaffold kits, runtime tiers, and module marketplace boundaries.
  • Added regression coverage so command-surface drift is caught before release.
  • Extended parity sync tooling to verify both import stack parity and runtime command surface parity.

• 🪟 Windows Go launcher hardening

  • Generated Go/Fiber and Go/Gin rapidkit.cmd launchers now use native Go commands for dev, build, test, format, and docs flows.
  • Windows users no longer need GNU Make just to run generated Go workspace commands.
  • Added generator coverage to lock this behavior.

Upgrade:

npm install -g rapidkit@0.32.1

📖 Full Release Notes

v0.32.0

Release Notes

Latest Release: v0.32.0 (June 7, 2026)

🧪 Runtime Acceptance Matrix, Release Evidence, and Audit Hardening

This release strengthens RapidKit npm as the workspace-level verification surface. It adds local runtime acceptance evidence for workspace/project commands, makes release reports survive temporary workspace cleanup, and tightens the security workflow around npm audit findings.

What's New:

• 🧪 Runtime acceptance matrix

  • Added local acceptance coverage for workspace and project command flows across FastAPI, FastAPI DDD, NestJS, Go/Fiber, Go/Gin, Spring Boot, ASP.NET Core, and observed runtimes.
  • Keeps the expensive matrix out of GitHub Actions by default while preserving it as explicit local release evidence.
  • Documents the release rule for using the matrix before publishing multi-runtime CLI changes.

• 🧾 Stable release evidence paths

  • Runtime matrix reports now default to a stable system temp report directory.
  • Reports are no longer removed when the temporary generated workspace is cleaned up.
  • --report <file> still supports explicit repository or artifact evidence paths.

• 🔒 Security and dependency hardening

  • The security workflow now fails on moderate-or-higher npm audit findings.
  • Refreshed vulnerable transitive dependency locks, including the Vitest toolchain.
  • Verified the release with a clean audit and full local validation.

Upgrade:

npm install -g rapidkit@0.32.0

📖 Full Release Notes

v0.31.0

Release Notes - v0.31.0

v0.31.0 (June 2, 2026)

🧭 Workspace Contract Registry, Portable Archives, and CLI Ownership Hardening

This release packages the workspace sharing, contract registry, and npm command ownership work delivered after v0.30.0. It is a minor release because it adds new user-facing CLI capabilities while also hardening install and execution behavior for global and npx users.

Highlights

• Portable workspace archive flow

  • Export, inspect, verify, doctor, and hydrate workspace archives through the npm CLI.
  • Preserve workspace handoff metadata for reliable team sharing and Workspai extension import flows.
  • Harden archive hydration with destination containment checks and cross-platform path normalization.

• Workspace Contract Registry

  • Capture workspace topology as a canonical contract: services, ports, dependencies, events, and ownership.
  • Generate and verify contract graph data before sharing, packaging, or release.
  • Detect unsafe or malformed contract/archive state before it reaches another user.

• CLI ownership hardening

  • Keep npm-owned commands inside the npm wrapper instead of accidentally bridging into Python Core.
  • Improve behavior for Windows users where rapidkit.exe resolution order can pick the wrong executable.
  • Add package CLI verification and publish contract coverage for wrapper entrypoints.

Notable Commits

• ab73e40 fix(cli): keep npm-owned commands in wrapper
• dbe441a feat: add portable workspace archive flow
• e71cca5 feat: harden workspace archive handoff
• f7c1cfd feat: add workspace contract registry
• 7b5ca1c feat: harden workspace contracts and archives
• ff52340 fix: harden workspace archive and contract validation
• f1c9454 fix: harden archive hydrate path containment

Upgrade

npm install -g rapidkit@0.31.0

Recommended Validation

Before publishing:

npm run typecheck
npm run test
npm run build
npm run verify:package-cli
npm audit --audit-level=moderate