releases
Forma v0.1.0-alpha.17
Internal alpha that aligns the VS Code extension with an explicitly installed, verified Forma CLI.
Purpose
Publish the coordinated CLI lifecycle completed after releases/forma-v0.1.0-alpha.16. The extension must no longer report a stale or incompatible CLI as ready, and users must be able to install the exact matching release binary explicitly inside the local or remote Extension Host.
Scope
- Require exact VS Code extension and Forma CLI version equality during the coordinated Alpha line.
- Resolve an explicit machine-level
forma.pathfirst, a verified managed binary second, and the Extension HostPATHlast. - Offer an explicit, cancellable installation command that downloads the matching GitHub Release binary and checksum into versioned extension storage without modifying
PATH. - Publish standalone editor-managed binaries and sibling SHA-256 files for macOS arm64/x64, Linux glibc arm64/x64, and Windows x64 while retaining the existing archives.
- Distinguish CLI and Explorer command failures from the absence of a Forma workspace, and record the resolved binary source in Forma Output.
- Prevent stale runtime refreshes and cancelled install flights from winning later work.
- Make interrupted response cleanup and Windows executable replacement recoverable without reporting a successful replacement as failed solely because a backup remains locked.
- Keep Restricted Mode free from downloads, CLI selection, and CLI execution.
- Verify that the packaged extension opens the native Markdown Preview rather than merely accepting a Preview command.
Release Gates
CI=true mise run checkpasses locally after the aligned version update.mise run version:check -- v0.1.0-alpha.17passes.- Forma config, content checks, and workspace health pass.
- Focused managed-install tests cover checksum, size, timeout, cancellation, single-flight retry, cleanup, and Windows replacement/rollback behavior.
- Restricted Mode tests invoke both managed CLI recovery commands and observe neither execution nor download.
- A packaged
forma-0.1.0-alpha.17.vsixinstalls in an isolated profile and opens real native Markdown Preview tabs for supported Views. - Tag CI validates the exact five-platform release matrix, builds the CLI and extension, runs Extension Host and packaged VSIX smoke tests, and publishes every archive, standalone binary, VSIX, and sibling checksum.
- The published macOS arm64 standalone binary and VSIX pass downloaded checksum, binary-version, and manifest-identity verification.
- The extension completes one real managed installation from the published Alpha 17 assets before tasks/manage-vscode-forma-cli-lifecycle moves to
done.
Known Boundaries
- Managed installation is always user initiated; there is no silent download or automatic update.
- Linux musl/Alpine, Marketplace publication, signing, and notarization remain out of scope.
- Local workspaces remain the release gate. Remote placement uses the remote Extension Host and its
globalStorageUri, but a live SSH, Dev Container, or WSL environment is not currently available for end-to-end validation. - Graph rendering remains a separate focused project.
Validation
- The remediation review identified and closed cancelled-flight reuse, stale refresh overwrite, Windows backup cleanup, Windows
code.cmdlaunch, packaged Preview false-positive, Restricted Mode command-entry, release-matrix, and test temporary-directory gaps. - Focused extension validation passed 114 Vitest tests, 15 Node release/script tests, TypeScript checks, and the Restricted Mode suite in an isolated profile using the installed official VS Code application.
- Existing leaked
forma-managed-cli-*andforma-download-*test directories were removed; the new cleanup fixture leaves zero matching directories after the focused suite. CI=true mise run checkpassed locally with aligned0.1.0-alpha.17versions, 128 TypeScript tests, 15 release/script tests, 234 Rust tests, formatting, lint, type checks, and production builds.- Forma config inspection and workspace health passed with zero diagnostics.
forma-0.1.0-alpha.17.vsixinstalled and activated in an isolated profile under the installed official VS Code 1.128.0 application. The smoke suite verified navigation and editable source behavior, then observed a newly created native Markdown Preview Tab for every list, table, kanban, and Graph View.- The local VSIX manifest reports
choral-io.forma@0.1.0-alpha.17, and its SHA-256 is36d7bfec8a1a9573af87979b04476491ad5a1b7c39821ddf30db1a7f26e95553. - Main CI run 29240867866 passed Knowledge, Web, Rust, Extension Host, and VSIX packaging, then exposed that the newly strengthened packaged Preview smoke was launching VS Code without an X server. Both CI and Release workflows now run that smoke under
xvfb-run, with a static regression assertion; the complete local gate passed again after the correction. - Main CI run 29241421341 passed Knowledge, Web, Rust, Extension Host, package inspection, VSIX packaging, and the strengthened packaged Preview smoke under Xvfb.
- Release run 29241622846 passed version validation, all five CLI target builds, Extension Host and packaged VSIX smoke tests, and GitHub Release publication.
- GitHub Release v0.1.0-alpha.17 is a prerelease with the expected 22 assets: five archives, five standalone managed binaries, one VSIX, and a sibling SHA-256 file for each payload.
- The downloaded
forma-macos-arm64checksum passed, and the executable reportedforma 0.1.0-alpha.17. Its SHA-256 isbe8aa8417676386e14e4a74aea606d29a039849a87fbaf9b24efccacf2eadb5f. - The downloaded VSIX checksum passed and its manifest reports
choral-io.forma@0.1.0-alpha.17with VS Code^1.110.0. The published VSIX SHA-256 is65e4d33d89bf05caa0e70cc9ef66128b7317d4f07c6b9e33c840565f36295fe4. - The extension's production managed-install implementation downloaded the published macOS arm64 binary and checksum into versioned managed storage, verified and installed the binary, and executed it successfully as
forma 0.1.0-alpha.17.
Release Notes
Forma
v0.1.0-alpha.17makes the VS Code extension and CLI lifecycle explicit and predictable. It rejects incompatible CLI versions, can install the exact checksum-verified release binary into local or remote extension storage on request, preserves user-managed configuration precedence, and improves diagnostics when CLI-backed Explorer operations fail.
Rollback Plan
Do not move or overwrite the Alpha 17 tag after publication. If internal testing finds a release blocker, stop distributing Alpha 17, record the failure, and publish a new aligned prerelease after correction.
Post-Release Follow-Up
- Validate one representative Remote SSH, Dev Container, or WSL workspace when an environment is available.
- Define a bounded policy for retaining older managed CLI versions after enough internal upgrade experience exists.
- Consider stronger signed provenance independently from the current sibling-checksum trust model.