Release v0.3.0 #10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release/0.3.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ships 0.3.0 — one PR with everything since 0.2.0.
Headline (from 0.3.0-rc1)
soundy-bits render …): preset → H.264/Opus MP4, no window. Hardware NVENC on NVIDIA (~7× real-time @1080p60) with a multi-threaded software fallback. Flags:--encoder,--bitrate,--quality,--speed,--software.Release engineering (new in this PR)
just release/bumpretired..DS_Store.Finalizes
0.3.0-rc1 → 0.3.0. Merge → I tagv0.3.0→ the pipeline ships all five artifacts (incl.-nvenc) as clean bundles. Subsumes #8 and #9.Replace the manual `just release` (local bump + tag + push, which fought the PR-only trunk flow) with release-plz's Release-PR model: - release-plz.yml (on push to master) opens/updates a Release PR that bumps Cargo.toml + CHANGELOG from Conventional Commits; merging that PR pushes the vX.Y.Z tag, which release.yml builds + publishes. No hand tagging. `--forge gitea`, GIT_TOKEN from FORGEJO_TOKEN. - release-plz.toml: publish=false (app, never crates.io), git_tag_name="v{{version}}" (matches release.yml's tag trigger), git_release_enable=false (release.yml still creates the release + attaches artifacts). - justfile: drop `release`/`bump`/`bump-pre`; keep `unstable` (ad-hoc test cuts) + `re-release`. CLAUDE.md "Release process" rewritten. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>