Prepare the 0.2.0 release record - #54
Merged
Merged
Conversation
Bring the unreleased 0.2.0 changelog entry up to date with everything that landed since it was drafted: the local-first woj CLI, the retired wasm-oj-collection bin, and the Java WASI toolchain. Correct the package counts to seven code packages and six toolchain packages, and date the entry to the day its contents were finalized. List @wasm-oj/toolchain-java in the independent toolchain release section, which still enumerated only five packages, and ignore the release-tarballs directory the documented pack step writes into the repository root. Claude-Session: https://claude.ai/code/session_01PHk8gF2Y12sSzyTGaFUi68
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release prep for the first
0.2.0publish. No code or version changes —CODE_VERSION, the root manifest, and all seven code manifests are already0.2.0, and the six toolchain packages are already0.1.0.CHANGELOG
The
0.2.0entry was drafted on 2026-08-12 and never released; ~25 commits landed after it. Brought it up to date:CLIadded to the list.wojCLI entry — local/offline boundary, browser-approved authorization stored only in the OS credential store, exit codes 0–7 as public contract.wasm-oj-collectionexecutable from@wasm-oj/organizer.docs/releasing.md
The independent-toolchain section still enumerated five packages after the header was corrected to six; added
@wasm-oj/toolchain-java..gitignore
release-tarballs/— the directory the documentedpack-library.mjsstep writes into the repository root (199 MB locally) — was untracked and unignored.Verification
pnpm install --lockfile-only— lockfile unchangedpnpm run library:build/library:verify— 13 packages built and verifiedpnpm run ci:verify— 178 test files, 883 tests passingpnpm run docs:verify— passesNote on the actual publish
The tag-driven release cannot run yet. None of the 13 package names exist on npm, and both workflows publish only through OIDC trusted publishing, which npm allows a maintainer to configure only after a package name exists. Per
docs/releasing.md, each name needs a one-time owner-authenticated bootstrap publish plus trusted-publisher configuration beforev0.2.0is tagged. Pushing the tag first would half-fail at a version that must never be reused.https://claude.ai/code/session_01PHk8gF2Y12sSzyTGaFUi68