Skip to content

chore(release): bump aggregator + README install snippets on release cut#71

Merged
DemchaAV merged 1 commit into
developfrom
chore/release-script-readme-bump
May 29, 2026
Merged

chore(release): bump aggregator + README install snippets on release cut#71
DemchaAV merged 1 commit into
developfrom
chore/release-script-readme-bump

Conversation

@DemchaAV
Copy link
Copy Markdown
Owner

Summary

  • cut-release.ps1 now bumps aggregator/pom.xml alongside the library pom and the inherited children, so all four version sites move together.
  • Adds Update-ReadmeInstallVersion: rewrites the README Maven + Gradle JitPack install snippets (vX.Y.Z) in the release commit, and stages README.md + aggregator/pom.xml.

Why

After #69 the version lives in the library pom, the aggregator, and the children's <parent> refs. The release script skipped the aggregator and never touched the README — so a cut would have failed the #70 version guard at the verify gate and shipped a stale README snippet. Flipping the README at release-execution time (not earlier) matches the release skill's Phase 2.3.

Test plan

After the aggregator-reactor change (#69) the version lives in the library
pom, the aggregator, and the children's inherited <parent> refs — but
cut-release.ps1 bumped only three POMs (skipping the aggregator) and never
touched the README JitPack snippets. A cut would have failed the new
version guard (#70) and shipped a stale README install snippet.

cut-release.ps1 now also bumps aggregator/pom.xml and rewrites the README
Maven + Gradle install snippets to the release tag in the same release
commit (Phase 2.3: README version flips at release-execution time), and
stages both files.
@DemchaAV DemchaAV merged commit 7a87aad into develop May 29, 2026
9 checks passed
@DemchaAV DemchaAV deleted the chore/release-script-readme-bump branch May 29, 2026 01:49
DemchaAV added a commit that referenced this pull request May 29, 2026
release.yml fires on vX.Y.Z tag pushes: it re-runs `mvnw clean verify -pl .`
against the tagged commit as a green-build gate, then creates (or updates)
a GitHub Release whose body is that version's CHANGELOG section. Pre-release
tags (e.g. v1.7.0-rc.1) ship as GitHub pre-releases.

Removes the manual "create a GitHub Release" step from the release
checklist. The version-consistency guard passes by construction because
cut-release.ps1 bumps every version site in the release commit (#71).
DemchaAV added a commit that referenced this pull request May 29, 2026
…ase.yml (#74)

Updates the release runbook to match the v1.6.5 plumbing (#69 #70 #71 #72 #73):

- README install snippets now flip in the release commit (cut-release.ps1),
  enforced by VersionConsistencyGuardTest — replaces the old "stay pinned to
  the previous tag, flip post-release" model that contradicted the guard.
- Version lives in four sites (library pom, aggregator, inherited
  examples/benchmarks parents); the script bumps all four + README in one pass.
- GitHub Release is created automatically by release.yml on tag push; the
  manual gh release create is now the documented fallback.
- Adds VersionConsistencyGuardTest to the pre-release guard-suite gate, and a
  v1.6.5 lesson that supersedes the v1.6.0 graphcompose.version property note.

The graphcompose-release-engineer skill (local config, Claude + Codex copies)
was aligned in lockstep.
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