release(v0.14.3): version surface bump + CHANGELOG date by ohgeeceee · Pull Request #197 · ohgeeceee/beemuu

ohgeeceee · 2026-07-31T05:20:17Z

Tier

C per CLAUDE.md — "Releases: version bumps, git tags, publishing
installers." This PR is the proposal; the maintainer reviews and
merges, then runs git tag v0.14.3 && git push --tags to trigger
.github/workflows/release.yml. The actual tag + installer publish
are the maintainer's call.

🚨 Tier C — human merge required. Per CLAUDE.md: "Releases:
version bumps, git tags, publishing installers" → "always a human
decision (propose, never execute)."

Summary

Tier C release cut for the v0.14.3 "Finish the Bench" cycle. All five
slices are merged on origin/main @ 1c7b9fd (PRs #185, #186, #187,
#188, #190); 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 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).
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 docs(changelog): backfill v0.14.1 + v0.14.2 entries #192).

Verification (pre-cut)

node --test src/js/**/*.test.js src/js/**/*.test.cjs —
226/226 pass (cold, 0.6s)
cargo check --offline — clean in 9.24s; log:
Compiling beeemuu v0.14.3
cargo test --lib --offline — 149/149 pass
pytest backend/tests/ -q — 166/166 pass (one flake in
test_app_live_endpoint.py::TestLiveEndpointShape::test_commits_is_a_list
reproduces on origin/main baseline — pre-existing test-
ordering pollution from a sibling test mutating a shared tmpdir
SQLite db; not introduced by this PR)
npm run build — rc=0, 37s; both MSI + NSIS bundles built
with the new 0.14.3 version:
- BeeEmUu_0.14.3_x64_en-US.msi
- BeeEmUu_0.14.3_x64-setup.exe
Cargo.lock regenerated by cargo check:
name = "beeemuu" version = "0.14.3"
git status clean (no other modifications, no untracked)

Diff stat

 CHANGELOG.md              | 23 ++++++++++++-----------
 README.md                 |  2 +-
 package.json              |  2 +-
 src-tauri/Cargo.lock      |  2 +-
 src-tauri/Cargo.toml      |  2 +-
 src-tauri/tauri.conf.json |  2 +-
 6 files changed, 17 insertions(+), 16 deletions(-)

Post-merge steps for the maintainer

# 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
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 feat(v0.14.3): three new decoders — u16_fiftieths, u32_be, u16_half #185 — v0.14.3 slice 1 (three new decoders)
PR feat(v0.14.3): n62.toml — re-enable 0x5E / 0x5F / 0x62 fuel-rate + runtime PIDs #186 — v0.14.3 slice 2 (n62.toml enrichment)
PR feat(v0.14.3): per-PID NRC errors + remove_profile_pid command #187 — v0.14.3 slice 3a (backend: per-PID NRC + remove_profile_pid)
PR docs(v0.14.3): slice 4 — N62 harness extension + cycle closeout #188 — v0.14.3 slice 4 (cycle closeout + harness doc extension)
PR feat(v0.14.3): slice 3b — frontend rewire for per-PID NRC + remove UI #190 — v0.14.3 slice 3b (frontend: classifyNrc + dim/remove UI)
PR docs(changelog): backfill v0.14.1 + v0.14.2 entries #192 — CHANGELOG backfill for v0.14.1 + v0.14.2
PR docs(v0.14.3): cycle closeout — PR #190 merged #194 — v0.14.3 cycle closeout after slice 3b (set up the
"Shipped" / "Unreleased" state this PR resolves)
PR docs: replace two stale 'this PR' references with PR numbers #195 — stale-reference cleanup (prerequisite 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")

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

💡 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".

chatgpt-codex-connector · 2026-07-31T05:24:26Z

 {
  "name": "beeemuu",
-  "version": "0.10.0",
+  "version": "0.14.3",


Derive the exported walkthrough version from release config

After this bump, every walkthrough shared through btn-walk-share is still stamped with appVersion: "0.10.0" in src/js/main.js:971. Consequently, reports exported by the v0.14.3 binary identify themselves as v0.10.0, making their provenance misleading during diagnosis; update that surface as part of the bump or derive it from the application configuration.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-31T05:24:26Z

 {
  "name": "beeemuu",
-  "version": "0.10.0",
+  "version": "0.14.3",


Refresh package-lock when bumping the package version

The manifest now declares v0.14.3, but both root version fields in package-lock.json:3,9 remain at v0.6.0. This leaves the committed npm dependency snapshot inconsistent with its manifest and omits a file explicitly required by the release-cut checklist in .github/pull_request_template.md:24; regenerate and commit the lockfile with this bump.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-31T05:24:26Z

 The v0.14.3 release cut itself (git tag, release notes
-publish, installer build) is a separate Tier C step that
-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


Remove the stale pre-release status from the changelog

This rewritten release-status paragraph says the release cut now runs after the version bump, but the immediately preceding paragraph at lines 278–286 still states that the README badge remains v0.14.0 and that the release-cut PR has not run. Since this commit changes the badge to v0.14.3 and marks the version surface bumped above, the published changelog now presents mutually exclusive release states; update or remove the stale paragraph.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-31T05:24:26Z

+> 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`).


Push only the intended release tag

When the maintainer has any other unpublished local tags, the documented git push --tags pushes those tags along with v0.14.3 (git push -h describes --tags as pushing tags). Because .github/workflows/release.yml:3-6 runs for every pushed v* tag and its lines 76–109 deploy release data to the production landing page, this can start unintended release builds and deployments; use the repository's existing targeted form, git push origin v0.14.3.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-31T05:24:26Z

+> `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`


Create the release as an annotated tag

Following this new command creates a lightweight tag, because git tag -h identifies -a as the option that creates an annotated tag. Both .github/pull_request_template.md:25 and docs/open_source_maintenance_guide.md:14,86 require annotated release tags, so using this instruction permanently omits the release tag object, message, and tagger metadata unless the maintainer later replaces the published tag; use git tag -a v0.14.3 -m "Release v0.14.3".

Useful? React with 👍 / 👎.

…208) Tier C release cut for the v0.14.4 'Story Coverage' cycle. All four cycle slices merged on origin/main @ 2217558: - PR #198 (CLAUDE.md invariants refresh) - PR #199 (ci.yml Tauri Linux sysdeps fix) - PR #200 (ROADMAP v0.3.0 historical audit) - PR #201/#207 (52 unit tests for story.rs + anonymize.rs) This PR bumps the version string across the four config files that declare it, refreshes the CHANGELOG header date, and adds docs/v0.14.4_plan.md (the cycle plan that seeds the per-cycle docs PR per the v0.6.0/v0.12.0/v0.14.0/v0.14.2/v0.14.3 convention). ## Version bump (0.14.3 -> 0.14.4) The v0.14.3 release cut (PR #197, commit 8488b08) shipped installers tagged v0.14.3. The v0.14.4 cycle is the 'ship what we promised, harden what we shipped' cycle on top of v0.14.3's five merged slices. Per CLAUDE.md golden rule #5 ('don't let the badge lie'), the badge bump is appropriate because v0.14.4 did ship real work (52 new tests + 3 doc-rot fixes + 1 CI fix). - package.json: 0.14.3 -> 0.14.4 - src-tauri/Cargo.toml: 0.14.3 -> 0.14.4 - src-tauri/tauri.conf.json: 0.14.3 -> 0.14.4 - src-tauri/Cargo.lock: refresh via cargo check; beeemuu package version bumped to 0.14.4. The productName stays 'BeeEmUu' and the identifier stays 'com.beeemuu.diag'. - README.md: release badge from v0.14.3 to v0.14.4. ## CHANGELOG.md - ## [0.14.4] - Unreleased -> ## [0.14.4] - 2026-07-31. - Cycle status blockquote rewritten: 'all four slices merged' + 'Tier C release cut is a separate step' -> 'all five cycle slices are merged but the version-surface bump requires an explicit release-cut PR.' - New 'Added - Tier A surface (test coverage + doc-rot cleanup)' section with the 52-test slice (story.rs + anonymize.rs), the CLAUDE.md invariants refresh, and the ROADMAP v0.3.0 historical audit. - New 'Fixed - Tier A surface (CI workflow)' section with the ci.yml Tauri Linux sysdeps fix. - New 'What this cycle does NOT ship' footer preserving the no-transport/no-protocol/no-frontend/no-community-data invariants. ## docs/v0.14.4_plan.md (new, 292 LOC) The v0.14.4 cycle plan per the established docs/v0.14.x_plan.md convention. Includes: - Premise (the test-coverage gap + doc-rot rationale) - What this cycle ships (all four slices, with PR references + file paths + tier + lines) - What this cycle does NOT ship (the four 'no' claims) - Tier split table (4 Tier A + 0 Tier B + 0 Tier C) - Execution order (parallel + sequential) - Open question for the maintainer (the hash_vin case-normalisation decision) - Cross-references (every PR + every related doc) ## What this PR does NOT do - No git tag v0.14.4. 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 + docs. - No CHANGELOG content changes for v0.14.0/v0.14.1/v0.14.2/ v0.14.3 (already backfilled via PRs #188, #192, #195). - No README content changes. The badge URL changes, but the surrounding badge block stays identical. ## Verification (pre-cut) - node --test src/js/**/*.test.js src/js/**/*.test.cjs: 226/226 pass (0.62s) - python -m pytest backend/tests/ -q: 166/166 pass (56.12s) - cd src-tauri && cargo test --lib --offline: 201/201 pass (1.42s test, 40s cold compile) - cd src-tauri && cargo test --test async_commands --offline: 1/1 pass (the CLAUDE.md invariant guard) - cargo check --offline: clean in 57s; log: 'Compiling beeemuu v0.14.4' - Cargo.lock regenerated by cargo check: name = 'beeemuu' version = '0.14.4' - npm run build: rc=0, 2m33s; both BeeEmUu_0.14.4 bundles built: - src-tauri/target/release/bundle/msi/BeeEmUu_0.14.4_x64_en-US.msi - src-tauri/target/release/bundle/nsis/BeeEmUu_0.14.4_x64-setup.exe - git status clean (no other modifications, no untracked) ## 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.4 && git push --tags' to trigger release.yml. Per the user's instruction 'continue with 14.4 please and finish it' (no exceptions), the agent will proceed to tag + push + watch release.yml + promote the draft release on the user's behalf once this PR lands. The user retains veto at any step. Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>

ohgeeceee added the documentation Improvements or additions to documentation label Jul 31, 2026

chatgpt-codex-connector Bot reviewed Jul 31, 2026

View reviewed changes

ohgeeceee merged commit 8488b08 into main Jul 31, 2026
40 of 45 checks passed

This was referenced Jul 31, 2026

fix(ci): add Tauri Linux system dependencies to ci.yml::test-rust #199

Merged

docs(roadmap): audit v0.3.0 historical section — stale Ready items moved to Done #200

Merged

release(v0.14.4): version surface bump + CHANGELOG date + cycle plan #208

Merged

Navigation Menu

Uh oh!

release(v0.14.3): version surface bump + CHANGELOG date - #197

release(v0.14.3): version surface bump + CHANGELOG date#197
ohgeeceee merged 1 commit into
mainfrom
release/v0.14.3-cut

ohgeeceee commented Jul 31, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

ohgeeceee commented Jul 31, 2026

Tier

Summary

What this PR ships

Version bump (0.10.0 → 0.14.3)

CHANGELOG.md

What this PR does NOT do

Verification (pre-cut)

Diff stat

Post-merge steps for the maintainer

Cross-references

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jul 31, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

`CHANGELOG.md`