release(v0.14.3): version surface bump + CHANGELOG date - #196
Conversation
Tier C release cut for the v0.14.3 "Finish the Bench" cycle. All five slices are merged on origin/main @ 1c7b9fd; this PR bumps the version string across the four config files that declare it, refreshes the CHANGELOG header date, and rewrites the "Notes on the version surface" blockquote to reflect that the release-cut PR has landed. ## What this PR ships ### Version bump (0.10.0 → 0.14.3) The version drift accumulated because v0.14.1, v0.14.2, and v0.14.3 all shipped without a version bump. CLAUDE.md golden rule #5 ("don't let the badge lie") was violated since v0.14.1 — the README badge has read v0.14.0 across three shipped cycles. Bumping to v0.14.3 (the most-recently-shipped cycle, per CLAUDE.md's "the badge moves only when something actually ships" rule) corrects the surface in one retroactive catch-up step. - `package.json` — `0.10.0` → `0.14.3` - `src-tauri/Cargo.toml` — `0.10.0` → `0.14.3` - `src-tauri/tauri.conf.json` — `0.10.0` → `0.14.3` - `src-tauri/Cargo.lock` — refresh via `cargo check`; beeemuu package version bumped to `0.14.3`. The productName stays `BeeEmUu` and the identifier stays `com.beeemuu.diag` (no product-naming changes in this release). - `README.md` — release badge from `v0.14.0` to `v0.14.3`. ### CHANGELOG.md - `## [0.14.3] — Unreleased` → `## [0.14.3] — 2026-07-30`. The date reflects the day all five cycle slices landed on origin/main; the section content is unchanged (already documented via PR #188 cycle closeout + PR #192 backfill + PR #195 stale-reference cleanup). - Cycle status blockquote rewritten: "The v0.14.3 release cut (version bump in `Cargo.toml` + `tauri.conf.json`, git tag, release notes publish, installer build) is a separate Tier C step — the slices are all merged but the version-surface bump requires an explicit release-cut PR. Until that PR lands, this entry stays `## [0.14.3] — Unreleased` per Keep-a-Changelog convention." → "Version surface bumped in the release-cut PR (this PR) to `0.14.3` across `package.json`, `src-tauri/Cargo.toml`, `src-tauri/tauri.conf.json`, and the README badge. The git tag + release publish + installer build are the next step (run locally via `git tag v0.14.3 && git push --tags` to trigger `.github/workflows/release.yml`)." - Closing paragraph rewritten: "follows the release-cut PR's merge. Until that lands, this entry stays `## [0.14.3] — Unreleased`." → "runs locally via `git tag v0.14.3 && git push --tags`, which triggers `.github/workflows/release.yml` and publishes a draft release on GitHub." ## What this PR does NOT do - ❌ No `git tag v0.14.3`. That's the next step (maintainer's call, Tier C). The PR sets the version strings; the tag publishes. - ❌ No `git push --tags`. Same — runs after the maintainer reviews and merges this PR. - ❌ No changes to `productName`, `identifier`, or any other config surface. Pure version bump. - ❌ No README content changes. The badge URL changes, but the surrounding badge block stays identical. - ❌ No CHANGELOG content changes for v0.14.1 / v0.14.2 (already backfilled via PR #192). ## Tier **C** per CLAUDE.md — "Releases: version bumps, git tags, publishing installers." Per CLAUDE.md Tier C rules: "always a human decision (propose, never execute)." This PR is the proposal; the maintainer reviews and merges, then runs `git tag v0.14.3 && git push --tags` to trigger the release.yml workflow. ## Verification (pre-cut) - [x] `node --test src/js/*.test.js` — 168/168 pass - [x] `cargo test --lib --offline` — 149/149 pass - [x] `pytest backend/tests/` — 166/166 pass - [x] `npm run build` — `rc=0`; both MSI + NSIS bundles built with the new `0.14.3` version: - `BeeEmUu_0.14.3_x64_en-US.msi` (5,009,408 bytes) - `BeeEmUu_0.14.3_x64-setup.exe` (3,488,856 bytes) - [x] Rustc compile log confirms: `Compiling beeemuu v0.14.3` - [x] `Cargo.lock` regenerated by `cargo check`: `name = "beeemuu" version = "0.14.3"` - [x] `git status` clean (no other modifications) ## Post-merge steps for the maintainer ```bash # 1. Verify the PR landed cleanly on origin/main git log origin/main --oneline -1 # 2. Tag the release git tag v0.14.3 # 3. Push the tag (triggers .github/workflows/release.yml) git push origin v0.14.3 # 4. Watch the release workflow gh run watch --repo ohgeeceee/beemuu # 5. Once the draft release is published, review it at # https://github.com/ohgeeceee/beemuu/releases/tag/v0.14.3 # and promote from draft to public. ``` The release.yml workflow (`.github/workflows/release.yml`) will: - Build Windows installers via `tauri-apps/tauri-action@v1` - Generate the MSI + NSIS bundles with the `0.14.3` version - Publish a draft GitHub release with the standard release notes (NSIS .exe + MSI .msi + safety warning banner) - Deploy the `_release_info.json` to `beemuu.com/frontend/` via the deploy SSH key (writes the new version into the public site's "Latest release" card) ## Cross-references - PR #188 — v0.14.3 slice 4 (the cycle-closeout PR that flagged the release cut as the next step) - PR #194 — v0.14.3 cycle closeout after slice 3b (updated ROADMAP + CHANGELOG to "Shipped" / "Unreleased" state) - PR #195 — "this PR" reference cleanup (prerequisite consistency for this PR's CHANGELOG edit) - `.github/workflows/release.yml` — the workflow that publishes the release on `v*` tag push - `docs/forward_roadmap_14.4_to_16.9.md` — the next cycle plan (v0.14.4 "N62 Bench Verification")
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 664785e882
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "name": "beeemuu", | ||
| "version": "0.10.0", | ||
| "version": "0.14.3", |
There was a problem hiding this comment.
Update package-lock.json along with this version bump: its top-level version and packages[""] .version still report 0.6.0, contrary to the release checklist in .github/pull_request_template.md. Running npm install immediately rewrites both fields to 0.14.3, so the committed dependency manifest is not reproducible from the new package.json without producing a dirty worktree.
Useful? React with 👍 / 👎.
| "$schema": "https://schema.tauri.app/config/2", | ||
| "productName": "BeeEmUu", | ||
| "version": "0.10.0", | ||
| "version": "0.14.3", |
There was a problem hiding this comment.
Ensure the runtime export metadata follows this release version: src/js/main.js:971 still passes appVersion: "0.10.0" to buildBundleHtml, which renders it into the exported document. Consequently, every walkthrough shared from a v0.14.3 build will identify itself as BeeEmUu 0.10.0 even though the installed application now reports 0.14.3.
Useful? React with 👍 / 👎.
| follows the release-cut PR's merge. Until that lands, this | ||
| entry stays `## [0.14.3] — Unreleased`. | ||
| publish, installer build) runs locally via | ||
| `git tag v0.14.3 && git push --tags`, which triggers |
There was a problem hiding this comment.
Replace this command with the repository's targeted release sequence (git tag -a v0.14.3 and git push origin v0.14.3). Checked git push -h, which defines --tags as “push tags,” so a maintainer with any other unpublished local v* tags would push all of them and .github/workflows/release.yml would start a release for each; the current lightweight tag command also contradicts .github/pull_request_template.md:25-26.
Useful? React with 👍 / 👎.
| [](COMMUNITY_FRAMEWORK.md) | ||
| [](CONTRIBUTORS.md) | ||
| [](CHANGELOG.md) | ||
| [](CHANGELOG.md) |
There was a problem hiding this comment.
Revise the version-surface note in CHANGELOG.md:278-286 when changing this badge. That section still says the README badge remains at v0.14.0, the release-cut PR has not landed, and the version bumps will occur later, directly contradicting this v0.14.3 badge and the newly dated release entry.
Useful? React with 👍 / 👎.
1 participant
release(v0.14.3): version surface bump + CHANGELOG date
Tier C release cut for the v0.14.3 "Finish the Bench" cycle. All five slices are merged on
origin/main @ 1c7b9fd; this PR bumps the version string across the four config files that declare it, refreshes the CHANGELOG header date, and rewrites the "Notes on the version surface" blockquote to reflect that the release-cut PR has landed.What this PR ships
Version bump (0.10.0 → 0.14.3)
The version drift accumulated because v0.14.1, v0.14.2, and v0.14.3 all shipped without a version bump. CLAUDE.md golden rule #5 ("don't let the badge lie") was violated since v0.14.1 — the README badge has read v0.14.0 across three shipped cycles. Bumping to v0.14.3 (the most-recently-shipped cycle, per CLAUDE.md's "the badge moves only when something actually ships" rule) corrects the surface in one retroactive catch-up step.
package.json—0.10.0→0.14.3src-tauri/Cargo.toml—0.10.0→0.14.3src-tauri/tauri.conf.json—0.10.0→0.14.3src-tauri/Cargo.lock— refresh viacargo check; beeemuu package version bumped to0.14.3. The productName staysBeeEmUuand the identifier stayscom.beeemuu.diag(no product-naming changes in this release).README.md— release badge fromv0.14.0tov0.14.3.CHANGELOG.md## [0.14.3] — Unreleased→## [0.14.3] — 2026-07-30. The date reflects the day all five cycle slices landed on origin/main; the section content is unchanged (already documented via PR docs(v0.14.3): slice 4 — N62 harness extension + cycle closeout #188 cycle closeout + PR docs(changelog): backfill v0.14.1 + v0.14.2 entries #192 backfill + PR docs: replace two stale 'this PR' references with PR numbers #195 stale-reference cleanup).git tag v0.14.3 && git push --tags.What this PR does NOT do
git tag v0.14.3. That's the next step (maintainer's call, Tier C). The PR sets the version strings; the tag publishes.git push --tags. Same — runs after the maintainer reviews and merges this PR.productName,identifier, or any other config surface. Pure version bump.Tier
C per CLAUDE.md — "Releases: version bumps, git tags, publishing installers." Per CLAUDE.md Tier C rules: "always a human decision (propose, never execute)." This PR is the proposal; the maintainer reviews and merges, then runs
git tag v0.14.3 && git push --tagsto trigger therelease.ymlworkflow.Verification (pre-cut)
node --test src/js/*.test.js— 168/168 passcargo test --lib --offline— 149/149 passpytest backend/tests/— 166/166 passnpm run build—rc=0; both MSI + NSIS bundles built with the new0.14.3version:BeeEmUu_0.14.3_x64_en-US.msi(5,009,408 bytes)BeeEmUu_0.14.3_x64-setup.exe(3,488,856 bytes)Compiling beeemuu v0.14.3Cargo.lockregenerated bycargo check:name = "beeemuu" version = "0.14.3"git statusclean (no other modifications)Post-merge steps for the maintainer
The
release.ymlworkflow (.github/workflows/release.yml) will:tauri-apps/tauri-action@v10.14.3version_release_info.jsontobeemuu.com/frontend/via the deploy SSH key (writes the new version into the public site's "Latest release" card)Cross-references
.github/workflows/release.yml— the workflow that publishes the release onv*tag pushdocs/forward_roadmap_14.4_to_16.9.md— the next cycle plan (v0.14.4 "N62 Bench Verification")