docs(changelog): credit the shipped --link-deps feature to release 2026.7.23

Merged
UN
3mo ago
+24-0

Problem

The published CHANGELOG.md never listed --link-deps — mapping issue-body Blocked by / Depends on / Blocks #N references into pm dependency edges — even though it shipped in npm 2026.7.23. pm-github-wpit was mis-sectioned the same way.

Cause: the last regeneration ran with stale local tags and before pm-github-hdai was closed, so the item was invisible to the generator and the v2026.07.23 boundary did not exist yet.

Both items closed before that tag, so both belong under ## 2026.7.23:

itemclosed_atvs tag v2026.07.23 (2026-07-23T06:12:30Z)
pm-github-hdai — --link-deps2026-07-22T23:10:49Zbefore ✅
pm-github-wpit — merge-reconcile docs2026-07-22T19:41:58Zbefore ✅

A user reading the changelog to find out when dependency linking became available currently finds nothing at all.

Change

Regenerated with complete tag history (git fetch --tags --force first):

  • adds the missing ### Added entry for --link-deps under ## 2026.7.23 - 2026-07-23
  • moves pm-github-wpit out of ## Unreleased into the same release
  • new ## Unreleased entry for pm-github-px45, the tracker for this fix

No source changes.

Verification

  • npm run changelog:check → "Changelog is up to date"
  • full test suite → green (0 failures)
  • Not a pm-changelog defect: the local (unreleased) build and the installed published build produce byte-identical output for this repo, which is how the gap was found — a fleet-wide parity audit across all 17 sibling packages.

pm items

itemstatus
pm-github-px45 — CHANGELOG omits the shipped --link-deps feature and mislabels 2026.7.23 work as Unreleasedclosed

🤖 Generated with Claude Code


Summary by cubic

Fix CHANGELOG.md: credit the shipped --link-deps feature to release 2026.7.23 and move pm-github-wpit into that release. Add an Unreleased entry for pm-github-px45; docs-only.