Chris Tate
401338f437
* feat(compiler): add native LLVM object emission - ship the pinned macOS arm64 LLVM helper and platform package - add assembly/object CLI outputs, caching, diagnostics, and runtime ABI checks - validate helper artifacts through CI, packaging, docs, and differential coverage * fix(compiler): harden native LLVM emission * fix(compiler): harden LLVM helper packaging * fix(compiler): stabilize LLVM helper package size * fix(compiler): harden native helper validation * fix(compiler): harden LLVM helper verification * fix(compiler): harden native object emission
3.3 KiB
Releasing
Releases are manual, single-commit affairs. The maintainer controls the changelog voice and format. The four npm packages — @scriptc/runtime, @scriptc/llvm-darwin-arm64, @scriptc/compiler, and scriptc — always publish together at the same version.
To prepare a release:
- Bump the version in
packages/cli/package.json - Run
node scripts/sync-versions.mjsto stamp the same version intopackages/runtime,packages/llvm-darwin-arm64, andpackages/compiler, thenpnpm manifestto restamppackages/compiler/surface-manifest.jsonwith the new version, and commit both (the test suite's staleness guard fails on a version drift) - Fold the
## Unreleasedsection ofCHANGELOG.mdinto a new## <version>entry (newest first, below## Unreleased), and leave## Unreleasedempty for the next cycle - Wrap the new entry in
<!-- release:start -->and<!-- release:end -->markers; this marked block is also the GitHub release body - Remove the
<!-- release:start -->and<!-- release:end -->markers from the previous release entry; only the latest release should have markers - With Zig on
PATH, runSCRIPTC_CROSS=1 pnpm exec vitest run tests/harness/library-cross.test.tsand require the cross-target library conformance lane to pass - Commit to
main
CI (.github/workflows/release.yml) compares the version in packages/cli/package.json to what scriptc has on npm. If it differs, it builds the workspace, verifies all four package versions match (a mismatch fails with a hint to run scripts/sync-versions.mjs), and publishes to npm in dependency order — @scriptc/runtime, @scriptc/llvm-darwin-arm64, @scriptc/compiler, then scriptc — so each package's dependencies are resolvable the moment it lands. After the publish succeeds, a separate job creates the git tag v<version> and the GitHub release with the marked changelog entry as its body, and attaches surface-manifest.json — the machine-readable listing of the surface the static tier compiles at that version (stable per-entry ids, so two releases diff mechanically; see packages/compiler/src/coverage/surface-manifest.ts for the schema). The job regenerates the manifest from the tree and fails on any byte difference from the committed file before attaching, so the asset is always the manifest of the code being released. The same file ships inside the @scriptc/compiler package as @scriptc/compiler/surface-manifest.json.
The release job runs on macOS arm64, builds and strips the pinned LLVM helper,
and publishes its constrained platform package before @scriptc/compiler.
Executable/runtime compilation still uses the user's local clang; the helper
owns only assembly/object code generation. The npm package's best-effort
postinstall warms runtime, TLS, and engine caches against that exact local
toolchain. The GitHub release remains a tag, release notes, and the manifest
asset; the npm publish never waits on the GitHub release.
Publishing uses npm trusted publishing (OIDC) — there is no npm token secret.
Each of the four packages must have a GitHub Actions trusted publisher for
release.yml and the Release environment. A missing configuration fails
before upload. Re-runs skip package versions already present on npm, so a
partially published release can be resumed safely.