chore(release): prepare v0.3.0 - #280
Merged
Merged
Conversation
Bump the four workspace crates 0.2.0 -> 0.3.0 and generate the 0.3.0 changelog section with git-cliff. Ship plugin bundles for all three targets that CI already builds green: plugin-release.yml gains linux-aarch64 and windows-x86_64 alongside linux-x86_64, mirroring the matrix in ci.yaml. Windows has no `zip` binary, so packaging splits into a Compress-Archive step there. Docs caught up with what actually shipped since 0.2.0: - both READMEs: 12 stages (tremolo was missing), per-stage bypass and reordering, plugin no longer labelled experimental, per-platform download table with honest hand-tested/CI-only status - README.zh-CN.md still claimed the plugin was unreleased and source-build only; ported the full plugin section across - CLAUDE.md: the per-slot plugin params pitfall described state that REV-4 deleted, and the standalone no longer panics on a missing JACK server (#277). Added a Releasing section documenting the tag -> dist -> `release: published` -> plugin-release.yml chain - `make changelog` now requires TAG; without it git-cliff files the commits being released under `[unreleased]` rather than the version
Contributor
There was a problem hiding this comment.
Pull request overview
Prepares the repository for the v0.3.0 release by bumping crate versions in lockstep, updating release/docs/changelog text to match the current state (12 stages, plugin no longer “experimental”), and expanding the plugin release workflow to publish bundles for Linux x86_64, Linux aarch64, and Windows x86_64.
Changes:
- Bump
rustortion-core,rustortion-ui,rustortion-standalone, andrustortion-pluginfrom0.2.0→0.3.0(plus correspondingCargo.lockupdates). - Update READMEs (EN + zh-CN) and CLAUDE.md to reflect the 12-stage chain and current plugin/release behavior; add platform download/install guidance.
- Update
plugin-release.ymlto build and attach plugin zips for three native runner targets, with OS-gated dependency install and packaging.
Reviewed changes
Copilot reviewed 10 out of 11 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| rustortion-ui/Cargo.toml | Version bump to 0.3.0. |
| rustortion-standalone/Cargo.toml | Version bump to 0.3.0. |
| rustortion-plugin/Cargo.toml | Version bump to 0.3.0. |
| rustortion-core/Cargo.toml | Version bump to 0.3.0. |
| Cargo.lock | Aligns locked package versions with 0.3.0 crate versions. |
| CHANGELOG.md | Adds the 0.3.0 release entry. |
| README.md | Updates stage count and plugin distribution/platform instructions. |
| README.zh-CN.md | Brings zh-CN docs up to date with the current plugin distribution and stage count. |
| CLAUDE.md | Updates command/release guidance and clarifies plugin parameter exposure/pitfalls. |
| Makefile | Makes make changelog require TAG and uses git-cliff --tag. |
| .github/workflows/plugin-release.yml | Expands release bundling/upload to three native targets; OS-specific packaging/install steps. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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 v0.3.0 — the code gate has been clear since #275–#279; this is mechanics plus doc catch-up.
Version
Bumps
rustortion-core,-ui,-standalone,-pluginfrom 0.2.0 → 0.3.0 (lockstep).xtaskstays 0.1.0 and remainsdist = false.Plugin ships for three platforms now
#274 proved the plugin builds natively green on aarch64 Linux and Windows x86_64, but those bundles only ever landed as expiring CI run artifacts.
plugin-release.ymlnow mirrors ci.yaml's matrix, so all three attach to the release:Rustortion-linux-x86_64.zipRustortion-linux-aarch64.zipRustortion-windows-x86_64.zipThis also closes the asymmetry where cargo-dist shipped the standalone for aarch64 but the plugin had no Pi build. Windows has no
zipbinary, so packaging splits into aCompress-Archivestep; the apt block is gated onrunner.os == 'Linux'.Docs
cargo run --releaseno longer panics without JACK (fix(standalone): report a missing JACK server instead of panicking #277). Added a Releasing section documenting the load-bearingrelease: publishedtrigger.make changelognow requiresTAG— baregit-clifffiles the commits you are releasing under[unreleased]instead of the version being cut, which is a quiet way to ship an empty changelog section.Verification
make lintclean under the full CI gate (-D warnings -D clippy::all -D clippy::pedantic -D clippy::nursery);make test= 308 passed, 0 failed. Includes #273's dependency bump, merged first so the lockfile is verified here rather than at tag time.Tag
v0.3.0goes on main once this lands.