Skip to content

fix(ledger): release-created rows carry tag/sha again (regressed in #349) - #351

Merged
linhdmn merged 1 commit into
mainfrom
devagent/TASK-mtyvor19-fix349
Sep 12, 2026
Merged

linhdmn merged 1 commit into
mainfrom
devagent/TASK-mtyvor19-fix349

Conversation

@linhdmn

@linhdmn linhdmn commented Sep 12, 2026

Copy link
Copy Markdown
Member

Restores Tag/SHA that PR #349 silently dropped from the record release ledger literal (rows were persisting "tag":""/"sha":""), adds a CLI-level regression test pinning the row shape, and regenerates docs/PRD.html to match docs/PRD.md (which was missing #349's build-revision footer line). gofmt/build/go test ./internal/cli/... green locally.

)

PR #349 added a Revision field to the Go ReleaseRecord but dropped Tag/SHA
from the `record release` literal while still printing "(tag @ sha)" to
stdout, so every Go-written release row persisted empty tag/sha — the exact
Q24 fields the record exists to carry. No test covered the CLI write site, so
it shipped green.

- restore Tag/SHA in the ReleaseRecord literal (actions_ledger.go)
- add internal/cli/actions_release_test.go pinning the CLI row shape
  (proven red on the regressed literal, green after)
- update docs/PRD.md footer + regenerate docs/PRD.html (pandoc) so the styled
  mirror matches PRD.md and gains #349's build-revision line too
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant