3.6 KiB
id, title, status, assignee, created_date, updated_date, labels, dependencies, references, priority, ordinal
| id | title | status | assignee | created_date | updated_date | labels | dependencies | references | priority | ordinal | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TASK-169 | Cut minor release v0.7.0 for stats and runtime polish | Done |
|
2026-03-19 17:20 | 2026-03-19 17:31 |
|
|
|
high | 108000 |
Description
Prepare the next release cut as v0.7.0, keeping 0-ver semantics by rolling the accumulated stats/dashboard, launcher, overlay, and stability work into the next minor line instead of a 1.0.0 release.
Acceptance Criteria
- #1 Repository version metadata is updated to
0.7.0. - #2 Root release-facing docs are refreshed for the
0.7.0release cut. - #3
CHANGELOG.mdandrelease/release-notes.mdcontain the committedv0.7.0section and consumed fragments are removed. - #4 Public changelog/docs surfaces reflect the new release.
- #5 Release-prep verification is recorded.
Implementation Plan
- Bump
package.jsonto0.7.0. - Refresh release-facing docs: root
README.md, release guide versioning note, and public docs changelog summary. - Run
bun run changelog:build --version 0.7.0to commit release artifacts and consume pending fragments. - Run release-prep verification (
changelog, typecheck, tests, docs build if docs-site changed). - Update this task with notes, verification, and final summary.
Implementation Notes
Bumped package.json from 0.6.5 to 0.7.0 and refreshed the root release-facing copy in README.md so the release prep explicitly calls out the new stats/dashboard line plus the background stats daemon commands. Updated docs/RELEASING.md with the repo's 0-ver versioning policy and an explicit --date reminder after the changelog generator initially stamped 2026-03-20 from UTC instead of the intended local release date 2026-03-19.
Ran bun run changelog:build --version 0.7.0, which generated CHANGELOG.md and release/release-notes.md and removed the queued changes/*.md fragments for the accumulated stats, launcher, overlay, JLPT, and stability work. Added a curated v0.7.0 summary to docs-site/changelog.md so the public docs changelog stays aligned with the committed root changelog while remaining user-facing.
Verification:
bash .agents/skills/subminer-change-verification/scripts/classify_subminer_diff.shbun run changelog:lintbun run changelog:check --version 0.7.0bun run verify:config-examplebun run typecheckbun run test:fastbun run test:envbun run buildbun run docs:testbun run docs:build
Final Summary
Prepared minor release v0.7.0 as the next 0-ver major line. Version metadata, root changelog, generated release notes, README release copy, release-guide policy, and the public docs changelog are now aligned for the release cut.
Docs update required: yes. Completed in README.md, docs/RELEASING.md, and docs-site/changelog.md.
Changelog fragment required: no new fragment for this task. Existing pending release fragments were consumed into the committed v0.7.0 changelog section and release/release-notes.md.
Release-prep verification passed across changelog validation, config-example verification, typecheck, fast/env tests, full build, and docs-site test/build.