ci(release): retire chart-releaser, publish the chart from release-please - #179
Merged
Conversation
release-please now creates the tag and the release, and a new reusable workflow packages the chart, attaches the tarball and merges a new entry into the Helm repository index on gh-pages. chart-releaser is deleted in the same commit: leaving it active would put two things on the same graylog-X.Y.Z name. The publish job is a workflow_call from inside the release-please run, not a release- or tag-triggered workflow. Refs created with GITHUB_TOKEN raise no workflow events, so those triggers would never fire. The index is merged, never regenerated. Packages live as release assets, so gh-pages holds no tarballs and regenerating from that directory would drop every historical entry and rewrite every URL. A guard records each (version, url) pair before the merge and fails before pushing if any would disappear or change, exempting the version being published. The artifacthub.io/changes annotation is generated here, before packaging, from the CHANGELOG.md of the tag being published, and is never committed. That is what the removal of the release-PR sync step was waiting on.
alix-graylog
changed the title
alix-graylog
marked this pull request as ready for review
August 27, 2026 19:38
aaronmgn
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retires chart-releaser. Release-please now creates the tag and the release, and a new reusable workflow packages the chart, attaches the tarball to that release, and merges one entry into
index.yamlongh-pages.Changes
.github/workflows/release-graylog.yaml, called fromrelease-please.yamlwhen a release is cut.skip-github-release, so release-please owns the release..github/workflows/release.yaml. Both workflows use the namegraylog-X.Y.Z, so leaving chart-releaser active would put two things on the same tag.Two things not to simplify
The publish job is a
workflow_callfrom inside the release-please run, not a release- or tag-triggered workflow. Refs created withGITHUB_TOKENraise no workflow events, soon: release: publishedand tag pushes never fire.The index is merged, never regenerated. Packages live as release assets, so
gh-pagesholds no tarballs, and regenerating from that directory would drop every historical entry. A step records each version and URL before the merge and fails before pushing if any would disappear or change, exempting the version being published.After merge
Publishing goes live. The next release PR that merges publishes for real. Check that
index.yamlgains one entry and that the 0.1.0 and 1.0.0 URLs are untouched.Rollback is restoring
release.yaml, re-addingskip-github-release, and removing thepublish-chartjob.gh-pagesis an ordinary branch if the index needs reverting.