Prepare the v0.1.0 release: publish runnable artifacts and cut the changelog#128
Merged
Conversation
The release workflow previously produced only generated notes — zero runnable artifacts, and the only container image went to a private ECR. Tagging vX.Y.Z now additionally publishes a linux/amd64 image to GHCR (version, MAJOR.MINOR, and latest tags; arm64 deferred until native runners, since an emulated Rust release build exceeds an hour) and attaches poly-book binaries for x86_64-linux and aarch64-darwin to the GitHub release. docs/releasing.md describes the artifacts and the post-release verification step.
Everything under [Unreleased] moves to [0.1.0] - 2026-07-06 with a short release summary; [Unreleased] starts fresh. The version is cut per the checklist in docs/releasing.md; the tag follows once this lands.
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.
Summary
The repo declares Keep-a-Changelog/SemVer and documents a release process that has never been exercised — zero tags, notes-only release workflow, images only in a private ECR. This PR makes
v0.1.0real:v*.*.*tags: alinux/amd64container image toghcr.io/weiminglong/poly-book(version +MAJOR.MINOR+latesttags, GHA build cache), andpoly-bookbinaries forx86_64-unknown-linux-gnuandaarch64-apple-darwinattached to the GitHub release. arm64 images are deferred with the reason documented (emulated Rust release builds exceed an hour on shared runners).[Unreleased]— the entire demo/compose/doctor/notebook/performance/hardening wave plus the earlier V2-compat and hardening work — moves to[0.1.0] - 2026-07-06with a release summary;[Unreleased]starts fresh.docker run ghcr.io/...starts the combined live workstation, which is the image's default command).After merge
Tagging (
git tag v0.1.0 && git push origin v0.1.0) triggers the workflow. I'll confirm before pushing the tag — it publishes a public release and package.