Skip to content

fix(docker-release): consolidate pre-releases in CHANGELOG.md#11

Merged
JSisques merged 1 commit into
mainfrom
fix/changelog-consolidate-prereleases
Jun 26, 2026
Merged

fix(docker-release): consolidate pre-releases in CHANGELOG.md#11
JSisques merged 1 commit into
mainfrom
fix/changelog-consolidate-prereleases

Conversation

@JSisques

Copy link
Copy Markdown
Contributor

Problem

CHANGELOG.md only ever showed alpha entries. Stable (and beta) sections came out empty even though the GitHub Release notes were correct.

Root cause: the Generate CHANGELOG.md (full history) step ran git-cliff with --tag but without --ignore-tags. git-cliff groups commits per tag, and in this release model all real commits land on develop (the alpha channel). Promotions to staging/main carry no new commits, so git-cliff had nothing to attribute to the beta/stable tags and omitted those sections.

The Generate release body fragment step already consolidates pre-releases on stable (--ignore-tags '.*-(alpha|beta|rc).*'), but that only feeds the GitHub Release body — not the committed CHANGELOG.md. This PR closes that inconsistency.

Fix

Pass --ignore-tags '.*-(alpha|beta|rc).*' to the full-history CHANGELOG.md generation so alpha/beta/rc work collapses into a single stable section per version.

File Change
.github/workflows/docker-release.yml Add --ignore-tags to the CHANGELOG.md git-cliff step + explanatory comment

Effect

A version's entire body of work now lands under its stable ## [X.Y.Z] entry instead of being scattered across -alpha.N sections.

Test Plan

  • git-cliff args mirror the already-proven release-notes fragment step
  • Validated on next stable release of a consuming repo (e.g. cookidoo-mcp)

🤖 Generated with Claude Code

The full-history CHANGELOG.md step grouped commits per tag without ignoring
pre-release tags, so every change landed under its alpha entry and stable
sections came out empty (graduation commits carry no new changes). Pass
--ignore-tags '.*-(alpha|beta|rc).*' so alpha/beta/rc work collapses into a
single stable section, matching the release-notes fragment behaviour.
@JSisques JSisques merged commit 7a7dc1f into main Jun 26, 2026
2 checks passed
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