Skip to content

chore(release): v1.2.1#65

Merged
vxcozy merged 1 commit into
mainfrom
chore/release-1.2.1
Apr 19, 2026
Merged

chore(release): v1.2.1#65
vxcozy merged 1 commit into
mainfrom
chore/release-1.2.1

Conversation

@vxcozy
Copy link
Copy Markdown
Owner

@vxcozy vxcozy commented Apr 19, 2026

Summary

Patch-level bump to 1.2.1 + CHANGELOG entry.

Shipping in v1.2.1

Fixed (CLI-97):

  • Sakura + heartbeat visualisers now react at normal listening volume. Same class of amplitude-scaling bug as the v1.2.0 bar-family fix, caught three viz later during live-testing. Both now flow through scaling.rs AGC helpers (SpectrumScaler for sakura's magnitude-domain intensity; new SampleScaler for heartbeat's bipolar sample domain).

Added (CLI-95):

  • Homebrew tap auto-bumps on every release. release.yml gained a homebrew-tap job that pushes the updated formula to vxcozy/homebrew-tap after the build matrix + release step succeed. RC tags skip the tap-bump. No more 15-minute "release shipped but `brew upgrade` is a no-op" window.

Removed:

  • Firework visualiser (23 → 22 entries). Onset-triggered particle bursts duplicated pulse's niche. Deletion confirmed during the CLI-97 live-test when all three black-screen viz were found in the same amplitude-math family. p × 2 from the default carousel position now lands on the fixed sakura.

⚠️ Must be cut as `v1.2.1-rc1` first

release.yml changed in PR #63 (the tap-bump automation). No tag push has exercised the new full pipeline yet — workflow_dispatch validated the tap-bump job in isolation, but build + release + tap-bump chained success path is untested.

Per the pre-push CI parity rule, the first tag after any release.yml change must be an RC dry run. After this PR merges:

  1. Cut `v1.2.1-rc1`
  2. Watch release.yml — expect 6 green jobs: 4 build targets, release, tap-bump skipped via `if: !contains('-rc')`
  3. If green, cut real `v1.2.1` tag
  4. Watch release.yml again — now 6 green jobs including tap-bump actually running
  5. `brew upgrade clitunes` lands v1.2.1 automatically

Release-sensitivity check

File class Changed since v1.2.0?
`release.yml` ✅ yes (PR #63) — owes RC
`rust-toolchain.toml` no
`Cargo.toml` structural no (only version bump in this PR)
`Cargo.lock` structural no
Workspace members no

Test plan

  • cargo fmt --check
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test --workspace --all-features
  • After merge: cut `v1.2.1-rc1`, confirm release.yml green (5 jobs + tap-bump skipped)
  • After RC green: cut `v1.2.1`, confirm release.yml green (6 jobs, tap-bump commits to homebrew-tap)
  • After tap-bump commit: `brew update && brew upgrade clitunes` reports 1.2.1 without manual intervention

Patch release: sakura + heartbeat AGC fixes, firework removal,
release.yml auto-bumps the Homebrew tap.

First tag after release.yml changed in PR #63 — must be cut as
v1.2.1-rc1 first to exercise the full tag-push pipeline (build ×4,
release, and the new homebrew-tap job) before cutting v1.2.1.

Closes CLI-97 (viz AGC), CLI-95 (tap automation) on the release side.
@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@vxcozy vxcozy merged commit 83cbcd9 into main Apr 19, 2026
12 checks passed
@vxcozy vxcozy deleted the chore/release-1.2.1 branch April 19, 2026 05:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant