Skip to content

Close 1 shipped-but-open trackers so the workspace stops reporting finished work as in flight #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
unbraind merged 3 commits into from
Jul 28, 2026
Merged

Close 1 shipped-but-open trackers so the workspace stops reporting finished work as in flight #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9c0609a
chore(pm): close 1 shipped-but-open trackers
unbraind Jul 28, 2026
446409a
chore(pm): attribute each closed tracker to the release that shipped it
unbraind Jul 28, 2026
fdcfe79
chore(pm): record the exact pm-changelog spec and resolution on the c…
unbraind Jul 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions .agents/pm/chores/pm-github-w7m7.toon
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,18 @@ id: pm-github-w7m7
title: Adopt --respect-item-release in changelog scripts and bump pm-changelog to 2026.7.24
description: "pm-changelog 2026.7.24 adds --respect-item-release, which makes the single-window generation path (--since-previous-tag --until-release-tag, changelog:check, release notes) honour an item's declared release field instead of trusting closed_at. Without it, closing a tracker whose fix shipped in an earlier release dates months-old work as new, which is why shipped-but-unclosed trackers accumulate: closing them corrupts the changelog. Adopting the flag fleet-wide makes late tracker closure safe and keeps every package's generation path in agreement with --all-release-tags."
type: Chore
status: in_progress
status: closed
priority: 2
tags[3]: changelog,fleet-consistency,release-hygiene
created_at: "2026-07-24T21:30:26.518Z"
updated_at: "2026-07-24T21:42:59.772Z"
assignee: claude
updated_at: "2026-07-28T11:30:02.569Z"
closed_at: "2026-07-28T11:14:18.877Z"
author: claude
acceptance_criteria: "changelog, changelog:full, changelog:check and release:notes all pass --respect-item-release; pm-changelog devDependency is ^2026.7.24; npm run changelog:check is green; CHANGELOG.md content is unchanged by the flag for this repo (no item declares a release yet)"
notes[2]{created_at,author,text}:
release: 2026.7.25
notes[3]{created_at,author,text}:
"2026-07-24T21:30:27.187Z",claude,"Verified in this repo: pm-changelog 2026.7.24 installed; npm run changelog:full regenerated CHANGELOG.md with the flag active and produced a ZERO-line diff, confirming the flag is a safe no-op until an item declares a release; npm run changelog:check exits 0."
"2026-07-24T21:42:59.772Z",claude,"Greptile review finding adopted: the daily release workflow invokes pm-changelog DIRECTLY (npx pm-changelog, three times) rather than through the npm scripts, so patching only package.json left the generation path that actually produces the published CHANGELOG.md and RELEASE_NOTES.md without the flag while release:check validated with it. Added --respect-item-release to all three release.yml invocations so generation and validation agree. YAML re-validated."
"2026-07-28T11:30:02.568Z",claude-code,"Correction to the close reason, raised by CodeRabbit on pm-ts-starter#43: the phrase pinned at 2026.7.24 or later is imprecise, because the manifest declares a caret RANGE rather than a pin. Exact verified values for this repo on 2026-07-28: package.json declares pm-changelog ^2026.7.25, the lockfile resolves it to 2026.7.25, and 4 changelog scripts pass --respect-item-release. The substance of the closure is unchanged; only the wording was loose. Original record preserved rather than rewritten."
close_reason: "Shipped and verified 2026-07-28: all four changelog scripts in package.json pass --respect-item-release and pm-changelog is pinned at 2026.7.24 or later. Closing so the tracker stops advertising completed work as in flight."
body: ""
3 changes: 3 additions & 0 deletions .agents/pm/history/pm-github-w7m7.jsonl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,3 +3,6 @@
{"ts":"2026-07-24T21:30:26.857Z","author":"claude","op":"update","patch":[{"op":"replace","path":"/metadata/updated_at","value":"2026-07-24T21:30:26.857Z"},{"op":"replace","path":"/metadata/status","value":"in_progress"}],"before_hash":"bb1bb0e43d550316b058cd96dfba018c4bf13abe4367e877d2d09f74561eccf2","after_hash":"3953df77fd26a1cd3d2d4adcdcaf2bee20f827f948b9fa4a3bcc504112a2cb62"}
{"ts":"2026-07-24T21:30:27.187Z","author":"claude","op":"note_add","patch":[{"op":"replace","path":"/metadata/updated_at","value":"2026-07-24T21:30:27.187Z"},{"op":"add","path":"/metadata/notes","value":[{"created_at":"2026-07-24T21:30:27.187Z","author":"claude","text":"Verified in this repo: pm-changelog 2026.7.24 installed; npm run changelog:full regenerated CHANGELOG.md with the flag active and produced a ZERO-line diff, confirming the flag is a safe no-op until an item declares a release; npm run changelog:check exits 0."}]}],"before_hash":"3953df77fd26a1cd3d2d4adcdcaf2bee20f827f948b9fa4a3bcc504112a2cb62","after_hash":"eeeeb2b27870732e27ea0767ba55f85e05cd59c828ffa54c81f25f74c435e968"}
{"ts":"2026-07-24T21:42:59.772Z","author":"claude","op":"note_add","patch":[{"op":"add","path":"/metadata/notes/1","value":{"created_at":"2026-07-24T21:42:59.772Z","author":"claude","text":"Greptile review finding adopted: the daily release workflow invokes pm-changelog DIRECTLY (npx pm-changelog, three times) rather than through the npm scripts, so patching only package.json left the generation path that actually produces the published CHANGELOG.md and RELEASE_NOTES.md without the flag while release:check validated with it. Added --respect-item-release to all three release.yml invocations so generation and validation agree. YAML re-validated."}},{"op":"replace","path":"/metadata/updated_at","value":"2026-07-24T21:42:59.772Z"}],"before_hash":"eeeeb2b27870732e27ea0767ba55f85e05cd59c828ffa54c81f25f74c435e968","after_hash":"d0e768b06bdcdb640252ab1aed4f4d086f138c8cf0f7035c081455aa0ed8f027"}
{"ts":"2026-07-28T11:14:18.877Z","author":"claude-code","author_source":"asserted","agent_harness":"claude-code","agent_instance":"178aa3540ae0b8aeb5b7ac26","agent_provenance":{"model":null,"effort":{"value":"xhigh","source":"environment"}},"op":"close","patch":[{"op":"remove","path":"/metadata/assignee"},{"op":"replace","path":"/metadata/updated_at","value":"2026-07-28T11:14:18.877Z"},{"op":"replace","path":"/metadata/status","value":"closed"},{"op":"add","path":"/metadata/closed_at","value":"2026-07-28T11:14:18.877Z"},{"op":"add","path":"/metadata/close_reason","value":"Shipped and verified 2026-07-28: all four changelog scripts in package.json pass --respect-item-release and pm-changelog is pinned at 2026.7.24 or later. Closing so the tracker stops advertising completed work as in flight."}],"before_hash":"d0e768b06bdcdb640252ab1aed4f4d086f138c8cf0f7035c081455aa0ed8f027","after_hash":"c7ad2f3735fff80d9484df1766e8383de375daa76e683b3d4bbf9187e107ddcb"}
{"ts":"2026-07-28T11:22:47.536Z","author":"claude-code","author_source":"asserted","agent_harness":"claude-code","agent_instance":"178aa3540ae0b8aeb5b7ac26","agent_provenance":{"model":null,"effort":{"value":"xhigh","source":"environment"}},"op":"update","patch":[{"op":"replace","path":"/metadata/updated_at","value":"2026-07-28T11:22:47.536Z"},{"op":"add","path":"/metadata/release","value":"2026.7.25"}],"before_hash":"c7ad2f3735fff80d9484df1766e8383de375daa76e683b3d4bbf9187e107ddcb","after_hash":"ae563e3eace23cdf8e380c30b7d0df9d762adc8473af293b8bf97aac16371cb6"}
{"ts":"2026-07-28T11:30:02.569Z","author":"claude-code","author_source":"asserted","agent_harness":"claude-code","agent_instance":"178aa3540ae0b8aeb5b7ac26","agent_provenance":{"model":null,"effort":{"value":"xhigh","source":"environment"}},"op":"note_add","patch":[{"op":"add","path":"/metadata/notes/2","value":{"created_at":"2026-07-28T11:30:02.568Z","author":"claude-code","text":"Correction to the close reason, raised by CodeRabbit on pm-ts-starter#43: the phrase pinned at 2026.7.24 or later is imprecise, because the manifest declares a caret RANGE rather than a pin. Exact verified values for this repo on 2026-07-28: package.json declares pm-changelog ^2026.7.25, the lockfile resolves it to 2026.7.25, and 4 changelog scripts pass --respect-item-release. The substance of the closure is unchanged; only the wording was loose. Original record preserved rather than rewritten."}},{"op":"replace","path":"/metadata/updated_at","value":"2026-07-28T11:30:02.569Z"}],"before_hash":"ae563e3eace23cdf8e380c30b7d0df9d762adc8473af293b8bf97aac16371cb6","after_hash":"c8c7fa5b7a6c96db73b1edc44c670963354fe62834c73bdc24a59d8cfd42da37"}
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,10 @@

- Import dies with an unexplained pm list-all failed on any tracker over 1 MiB, and non-atomic --dry-run previews every issue as a create ([pm-github-tn92](https://github.com/unbraind/pm-github/blob/main/.agents/pm/issues/pm-github-tn92.toon))

### Other

- Adopt --respect-item-release in changelog scripts and bump pm-changelog to 2026.7.24 ([pm-github-w7m7](https://github.com/unbraind/pm-github/blob/main/.agents/pm/chores/pm-github-w7m7.toon))

## 2026.7.23 - 2026-07-23

### Added
Expand Down