sudacode
48f10dbb03
- Move completed tasks (85, 117, 118, 155) to backlog/completed/ - Delete superseded task files (166 verification, 172 drilldown) - Add stats dashboard milestone m-1 - Add new tasks (190, 194) - Update task metadata across remaining backlog items - Add changelog fragments for stats, mpv args, and subtitle filtering
3.5 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-149 | Cut patch release v0.5.5 for character dictionary updates and release guarding | Done |
|
2026-03-09 01:10 | 2026-03-18 05:28 |
|
|
|
high | 39500 |
Description
Prepare and publish patch release v0.5.5 after the failed v0.5.4 tag by aligning package version metadata, generating committed changelog output from the pending release fragments, and hardening release validation so a future tag cannot ship with a mismatched package.json version.
Acceptance Criteria
- #1 Repository version metadata is updated to
0.5.5. - #2
CHANGELOG.mdcontains the committedv0.5.5section and the consumed fragments are removed. - #3 Release validation rejects a requested release version when it differs from
package.json. - #4 Release docs capture the required version/changelog prep before tagging.
- #5 New
v0.5.5release-prep commit and tag are pushed toorigin/main.
Implementation Plan
- Add a regression test for tagged-release/package version mismatch.
- Update changelog validation to reject mismatched explicit release versions.
- Bump
package.json, generate committedv0.5.5changelog output, and remove consumed fragments. - Add a short
docs/RELEASING.mdchecklist for the prep flow. - Run release verification, commit, tag, and push.
Implementation Notes
Added a regression test in scripts/build-changelog.test.ts that proves changelog:check --version ... rejects tag/package mismatches. Updated scripts/build-changelog.ts so tagged release validation now compares the explicit requested version against package.json before looking for pending fragments or the committed changelog section.
Bumped package.json from 0.5.3 to 0.5.5, ran bun run changelog:build --version 0.5.5 --date 2026-03-09, and committed the generated CHANGELOG.md output while removing the consumed task fragments. Added docs/RELEASING.md with the required release-prep checklist so version bump + changelog generation happen before tagging.
Verification: bun run changelog:lint, bun run changelog:check --version 0.5.5, bun run typecheck, bun run test:fast, and bun test scripts/build-changelog.test.ts src/release-workflow.test.ts. bun run format:check still reports many unrelated pre-existing repo-wide Prettier warnings, so touched files were checked/formatted separately with bunx prettier.
Final Summary
Prepared patch release v0.5.5 after the failed v0.5.4 release attempt. Release metadata now matches the upcoming tag, the pending character-dictionary/overlay/plugin fragments are committed into CHANGELOG.md, and release validation now blocks future tag/package mismatches before publish.
Docs now include a short release checklist in docs/RELEASING.md. Validation passed for changelog lint/check, typecheck, targeted workflow tests, and the full fast test suite. Repo-wide Prettier remains noisy from unrelated existing files, but touched release files were formatted and verified.