2.2 KiB
id, title, status, assignee, created_date, updated_date, labels, dependencies, references, priority
| id | title | status | assignee | created_date | updated_date | labels | dependencies | references | priority | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TASK-139 | Cut patch release v0.5.3 for unsigned Windows release builds | Done |
|
2026-03-09 00:00 | 2026-03-09 00:00 |
|
|
|
high |
Description
Publish a patch release from the unsigned Windows release-build change by bumping the app version, generating committed changelog artifacts for v0.5.3, and pushing the release-prep commit.
Acceptance Criteria
- #1 Repository version metadata is updated to
0.5.3. - #2
CHANGELOG.mdandrelease/release-notes.mdcontain the committedv0.5.3section and consumed fragments are removed. - #3 New
v0.5.3release-prep commit is pushed toorigin/main.
Implementation Plan
- Bump
package.jsonfrom0.5.2to0.5.3. - Run
bun run changelog:buildso committed changelog artifacts match the new patch version. - Run changelog/typecheck/test verification.
- Commit the release-prep change set and push
main.
Implementation Notes
Bumped package.json from 0.5.2 to 0.5.3, ran bun run changelog:build, and committed the generated release artifacts. That prepended the v0.5.3 section to CHANGELOG.md, regenerated release/release-notes.md, and removed the consumed changes/unsigned-windows-release-builds.md fragment.
Verification before push: bun run changelog:lint, bun run changelog:check --version 0.5.3, bun run typecheck, and bun run test:fast.
Final Summary
Prepared patch release v0.5.3 so the unsigned Windows release-build change is captured in committed release metadata on main. Version metadata, changelog output, and release notes are aligned with the new patch version.
Validation: bun run changelog:lint, bun run changelog:check --version 0.5.3, bun run typecheck, bun run test:fast.