releases

Forma v0.1.0-alpha.14

Immutable internal corrective prerelease record for the post-Alpha 13 core and VS Code extension fixes.

Purpose

Publish the corrective changes merged after releases/forma-v0.1.0-alpha.13 as a new aligned binary and VSIX release without moving or overwriting the Alpha 13 tag.

Scope

  • Correct the VS Code reference-token end boundary so definition and hover lookup do not claim the first character after a reference.
  • Require the canonical <!-- forma:content --> view mount and return an actionable migration diagnostic for legacy <!-- forma-view --> markers.
  • Include the reviewed VSIX output naming and Extension Host test-environment fixes.
  • Expand released-package smoke coverage for workspace discovery, supported link forms, source opening, and list/table/kanban/Graph preview commands.
  • Remove the obsolete Foam recommendation now that Forma supplies the workspace navigation path used by this repository.

Graph remains intentionally deferred. This release does not add a graph renderer or widen the editor-extension feature scope.

Validation

Required gates:

  1. CI=true mise run check passes locally.
  2. Forma config, content checks, and workspace health pass.
  3. The VSIX package contents and Extension Host tests pass.
  4. PR and merged-main CI pass.
  5. Tag v0.1.0-alpha.14 points to the verified merge commit.
  6. The Release workflow publishes all binary archives, the VSIX, and sibling checksum files.
  7. Downloaded checksums pass; the binary and VSIX both report 0.1.0-alpha.14.

Current result:

  • Version consistency passed for v0.1.0-alpha.14; Cargo metadata accepted the locked dependency graph.
  • Focused VS Code reference/client tests passed 12 tests, and the remediation script suite passed 3 tests.
  • CI=true mise run check passed pnpm checks, lint, tests, production builds, Rust formatting/checks, and the full Rust test suite.
  • VSIX package contents resolve to forma-0.1.0-alpha.14.vsix with the expected manifest, README, changelog, license, and bundled extension entrypoint.
  • forma check --json and forma workspace health --json passed with zero diagnostics.
  • PR #4 merged at 39d44ebaa0d869969d9303d724ac5a3f1c890ca3 after Knowledge, Web, Rust, and VS Code Extension passed in CI run 29161560547; the thread-aware merge gate reported zero review threads on the final HEAD.
  • The same four jobs passed for the merged main commit in CI run 29161647142.
  • Annotated tag v0.1.0-alpha.14 points to the verified merge commit. Release run 29161734834 passed version validation, five binary builds, VS Code Extension Host tests, VSIX packaging, checksum generation, and GitHub Release publication.
  • GitHub prerelease v0.1.0-alpha.14 contains five platform archives, the VSIX, and a sibling checksum for every payload.
  • All six downloaded payload checksums passed. The released macOS arm64 binary reports forma 0.1.0-alpha.14; the VSIX SHA-256 is 4e8915439802ce6ea6911ef3da618cbc54d2006bf8b116ad499442226a1dfec4, and its manifest reports choral-io.forma@0.1.0-alpha.14, Forma for VS Code, https://forma.choral.io, and VS Code ^1.110.0.

Rollout Plan

  1. Prepared and validated the release on codex/alpha14-release.
  2. Merged PR #4 after the required checks and review-thread gate passed.
  3. Confirmed merged-main CI before creating tag v0.1.0-alpha.14.
  4. The tag-triggered Release workflow built and published all artifacts.
  5. Downloaded and verified the published payloads before internal distribution.

Release Notes

Forma v0.1.0-alpha.14 publishes the reviewed corrections made after Alpha 13. It tightens VS Code reference-token boundaries, enforces the canonical source-backed View mount with a migration diagnostic for the legacy marker, and strengthens released-VSIX validation across navigation and View preview commands.

Rollback Plan

Do not move or overwrite either published prerelease tag. If internal testing finds a release blocker, stop distributing Alpha 14, record the failure, and publish a new version after the correction is verified.

Post-Release Follow-Up

  • Continue internal testing in real VS Code configurations and remote workspaces where available.
  • Keep Graph implementation as a separate focused project.