Conversation
Review:
|
| Surface | File | Old | New | Status |
|---|---|---|---|---|
| Workspace Cargo | Cargo.toml |
0.6.0 |
0.7.0 |
✓ |
| webtau-macros pin | crates/webtau/Cargo.toml |
=0.6.0 |
=0.7.0 |
✓ |
| webtau npm | packages/webtau/package.json |
0.6.0 |
0.7.0 |
✓ |
| webtau-vite npm | packages/webtau-vite/package.json |
0.6.0 |
0.7.0 |
✓ |
| create-gametau npm | packages/create-gametau/package.json |
0.6.0 |
0.7.0 |
✓ |
| base template (webtau) | templates/base/package.json |
^0.6.0 |
^0.7.0 |
✓ |
| base template (webtau-vite) | templates/base/package.json |
^0.6.0 |
^0.7.0 |
✓ |
| pixi template | templates/pixi/package.json |
^0.6.0 |
^0.7.0 |
✓ |
| three template | templates/three/package.json |
^0.6.0 |
^0.7.0 |
✓ |
| base commands Cargo | templates/base/src-tauri/commands/Cargo.toml |
0.6.0 |
0.7.0 |
✓ |
| base wasm Cargo | templates/base/src-tauri/wasm/Cargo.toml |
0.6.0 |
0.7.0 |
✓ |
Stale-reference sweep: Grepped the entire repo for 0.6.0 across all Cargo.toml and package.json files — zero hits. Clean.
Examples unaffected (correct): All four examples (counter, pong, battlestation, electrobun-counter) use path deps for Rust crates and workspace:* for npm — they inherit the workspace version automatically and don't need explicit bumps.
Changelog review ✓
[Unreleased]section retained and empty — correct Keep a Changelog form.[0.7.0] - 2026-03-06dated to today.- Added section expanded to cover Battlestation runtime lanes and the hybrid WGPU showcase path — this was missing from the prior
Unreleasedtext and is a good addition. - Changed section adds the CI/release-gate requirement for
Electrobun Hybrid + GPU Smoke— accurately reflects what changed between v0.6.0 and now. - Content is consistent with the commit history (
#167,#168) that landed the Battlestation GPUWindow and Electrobun doc rebaseline work.
Scope ✓
Single commit, +18/−14, 11 files. No code changes, no logic changes, no test changes — pure version + changelog metadata. Exactly what a release-prep PR should be.
PR description ✓
Root cause → fix → validation → milestone context. The note about bun run vitest run vs bun run test is helpful for future codex runs against this repo.
One non-blocking nit
Mixed line endings: The commit introduces LF-only lines into files whose existing lines are CRLF (Cargo.toml, CHANGELOG.md both report ASCII text, with CRLF, LF line terminators). There is no .gitattributes in the repo to normalize. The local core.autocrlf=true setting handles checkout, but the codex agent that authored the commit likely ran with a different setting. This is cosmetic and won't cause functional issues, but could produce diff noise in future edits. Consider adding a root .gitattributes with * text=auto as a follow-up — not a blocker for this PR.
Summary: All publishable version surfaces are aligned at 0.7.0, no stale references exist, the changelog accurately reflects the v0.6.0→v0.7.0 delta, and the scope is appropriately minimal. Ready to merge, close #162, and tag.
— Claude Opus 4.6 (1M context)
Summary
This PR is the dedicated
v0.7.0release-prep step after the Electrobun milestone feature work landed and the follow-up doc rebaseline merged in#168.The user-facing goal here is not new functionality. It is to make the repository publishable and reviewable as the
0.7.0release line by aligning the package/crate/template version surfaces and by turning the currentUnreleasednotes into a concrete0.7.0changelog entry.Root cause
After the Electrobun workstream merged, the repo still had a split state:
v0.7.0surface0.6.00.6.0package lineUnreleased, which is not the right state for a release-prep PRWithout this prep step, the next tag would not line up with the published manifest versions or the generated-template dependency expectations.
Fix
This PR:
0.6.0to0.7.0webtau->webtau-macrosdependency pin to=0.7.00.7.0webtau/webtau-vite^0.7.0UnreleasedElectrobun entry into a dated0.7.0changelog sectionv0.6.0and todayValidation
I validated this PR with:
cargo checkbun run testgit diff --checkNote: an initial
bun run vitest runattempt failed because this repo does not expose a rootvitestscript; I then reran the correct repo-level test entrypoint withbun run test, which passed.Milestone context
Refs
#162.At this point milestone
11is down to the umbrella tracker only. This PR is the release-prep step that follows the completed feature/docs work.