releases
Forma v0.1.28
Corrective release for cross-platform canonical-doc parsing and stable release gates.
Scope
Publish the complete releases/forma-v0.1.26 feature cutline through a new immutable tag after releases/forma-v0.1.27 corrected the Windows WebApp shell incompatibility but exposed later release gates. The candidate retains the static publishing, resolved workspace operations, runtime performance, Agent Skill, CLI, WebApp, VS Code, Zed, and compatible dependency changes prepared for the preceding attempts.
Included Changes
- Parse canonical-document frontmatter through the same line-oriented implementation used by Forma runtime Markdown, accepting both LF and CRLF without maintaining a divergent build-only parser.
- Cover LF, CRLF, and body-thematic-break boundaries with focused Core regression tests.
- Retry a complete 50-sample warm VSIX performance distribution only when its first p95 exceeds the accepted budget; fail when the repeated distribution also breaches the budget so deterministic regressions remain blocked.
- Add an exact Windows release-binary build to main CI so cross-platform build failures are rejected before a commit can become a tagged release candidate.
- Carry forward the complete
v0.1.26andv0.1.27Public Preview scope because neither immutable tag reached GitHub Release or Marketplace publication.
Validation
- Focused Core frontmatter, release-contract, extension type, format, and lint gates pass.
mise run version:check -- v0.1.28andCI=true mise run checkpass from the exact candidate.- Forma content checks and workspace health pass.
- The matching
forma-0.1.28.vsixpackages and passes its isolated installation, activation, functional navigation, and repeated-breach performance smoke gate. - The complete candidate is pushed and main CI passes for its exact commit, including the new Windows release build, before tagging.
- The tag-triggered Release workflow builds every supported CLI asset and the VSIX.
mise run release:verify -- v0.1.28verifies the published asset inventory, checksums, CLI version, VSIX identity, and managed CLI installation.
Rollout Plan
- Create an annotated
v0.1.28tag only after exact-source local and main gates pass. - Let the protected Release workflow publish GitHub assets and the verified VSIX to Marketplace.
- Keep the failed
v0.1.26andv0.1.27tags immutable and do not create releases from them.
Migration Or Operations Notes
- Existing Forma workspace content does not require migration.
- Consumers who did not receive
v0.1.26orv0.1.27should upgrade directly fromv0.1.25tov0.1.28. - Main-branch static-site deployment remains independent from the versioned CLI and editor-extension release.
Release Notes
Forma
v0.1.28publishes the full static-site, runtime-performance, resolved-workspace, and Agent Skill update with release gates hardened against Windows line endings and transient shared-runner scheduling pauses.
Release Evidence
- Immutable tag:
v0.1.28at candidate commit3bf6bb43d164677c1cf2f795bc9416a298a08a61. - Candidate main CI: run 30441907347 passed for that exact commit, including the Windows release build.
- Final GitHub Release, published-release verification, and Marketplace publication: run 30442370720 passed. The Marketplace job published the smoke-tested VSIX through GitHub OIDC.
- Published release: Forma v0.1.28 is non-draft, non-prerelease, and has the expected 22 assets.
mise run release:verify -- v0.1.28passed on macOS ARM64:forma-macos-arm64reportsforma 0.1.28with SHA-25682db77ad1b0497f038a1451823fc7d0fd458a93cfaa1b8a555653b29d1c12723;choral-io.forma@0.1.28reports engine^1.110.0with SHA-256be2886cfc173f8464acab73577f80b2aeef0c78caec0ff114d2028e28b209389; managed install also executedforma 0.1.28.- The Release workflow's Linux Extension Host and packaged-VSIX smoke passed. A separate local attempt to launch VS Code from Codex aborted in macOS application registration before extension loading, so it is recorded as a local GUI-launch boundary rather than product evidence.
- Remote SSH, Dev Container, WSL, signing, and notarization remain untested.
Rollback Plan
Do not move or overwrite v0.1.26, v0.1.27, v0.1.28, Marketplace versions, or verified release assets. If publication or post-release verification finds another blocker, publish a higher coordinated version after remediation.
Post-Release Follow-Up
- Continue the planned WebApp code-splitting work for the largest generated chunks.