Skip to content

GitHub Release backfill and changelog sync

Choose a tag to compare

@cursor cursor released this 29 Aug 23:22
bc30bf2

All 72 documented app versions now have matching GitHub Release tags (v{VERSION}), and release prepare requires a pull request reference so future versions stay aligned with GitHub.

Changes

  • Backfill GitHub Releases and tags for v0.1.0 through v0.31.6 mapped to their merge commits on main.
  • Add scripts/local/map-release-commits.mjs and scripts/local/backfill-github-releases.mjs with dry-run, resume, and batch support.
  • Require --pr on myapes:changelog-prepare so every new release cites its merging pull request.
  • Show a GitHub Release link in the Change Log Hub Source section for staff and admin viewers.
  • Document GitHub Release tag parity and the deploy SHA versus version introduction commit distinction in README and ship-gate guidance.

Affected areas

  • GitHub Releases and tags
  • Release metadata workflow
  • Change Log Hub staff references
  • Agent ship-gate documentation

Version rationale

Patch release: aligns external GitHub versioning with in-app semver and tightens release metadata hygiene without changing production application behaviour.

References

MyAPES Core 0.31.9 (2026-08-29) · stable · patch