Files
WRNexusJS/docs/releases/2026-10-19-private-release.md
T

39 lines
2.1 KiB
Markdown

# Private release — 2026-10-19
The user authorized committing and pushing all completed framework work,
publishing every package to the WorkRoot private registry, and preparing the
standalone component showcase for VM deployment.
All 58 packages use independent versions. Existing release lines receive the
next unused patch; design-system and design-studio start at 0.1.0. The release
manifest is stored in `docs/releases/2026-10-19-packages.json`. Publication uses
only https://registry.workroot.in/repository/npm/ with restricted access.
The Studio server adds an explicit hosted, export-only integration with a base
path. The default local CLI and handler behavior remains unchanged. Hosted mode
cannot apply designs or run a configured paid provider; previews are ephemeral,
and recoverable drafts remain in browser storage. The standalone showcase adds
VM startup and reverse-proxy instructions for `/design-studio/`.
Validation and publication results will be recorded after completion. Live
PostgreSQL/MySQL tests still require the optional database environment settings.
## Validation
The full `bun run check:production` gate passed after release version changes
and editor bundle regeneration: 2,562 package tests passed, one optional live
database test skipped, plus all example, service and editor checks. Hosted Studio
also passes same-origin, proxy scheme, base-path preview and export-only tests.
All-package staging uses TypeScript 6 declaration options explicitly, including
packages with their own compiler configurations.
The all-package declaration build additionally exposed a missing Bun ambient-type
setting in dev-toolbar; its package tsconfig now explicitly includes Bun types,
and its own typecheck passes. The design release's isolated tarball consumers,
installed declarations, browser bundle and MCP-only installation all pass.
All 58 staged tarballs passed an isolated installation: all 57 non-CLI package
roots import successfully, UI and viewer browser/runtime probes pass, and the
installed CLI starts successfully. The all-package consumer includes React and
React DOM only to exercise the optional adapter, matching its declared peers.