Repository navigation
ci(sync-on-release): open a chart bump PR instead of pushing to protected main - #17
Merged
Merged
Conversation
main is protected (changes through a reviewed PR), so the bump this workflow pushed after every server release was refused (v0.12.3: "GH006: Protected branch update failed"). It now opens a PR from chore/chart-sync-<version>; merging it publishes the chart through helm-release / helm-publish-oci, which run on charts/** pushes to main. - Skips when the chart is already at the version, when it would downgrade, or when an open PR already sets that appVersion (a hand-written release PR). - Checks the server image is published; also bumps the artifacthub image annotation, replaces the changes annotation and adds a CHANGELOG entry. - The dispatch payload goes through env and must be X.Y.Z (it was pasted into the script). - GH_PAT_PACKAGES pushes and opens the PR, so Chart CI runs on it. - dry_run (manual): opens the PR as a draft, then closes it and deletes the branch, to check the path end to end. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
After every Dakera server release,
sync-on-release.ymlpushed the chart bump straight tomain.mainis protected (changes go through a reviewed PR), so for v0.12.3 it failed withGH006: Protected branch update failed. #16 had already done that bump.Now: the workflow opens a PR from
chore/chart-sync-<version>. Merging that PR publishes the chart, becausehelm-releaseandhelm-publish-ocirun oncharts/**pushes tomain(as they did when #16 merged).appVersion(a release PR like release: chart 0.12.3 (Dakera server v0.12.3, dashboard 0.5.2) + hardening #16).ghcr.io/dakera-ai/dakera:<version>is published.version,appVersion, the artifacthub image annotation (the old version left it stale), a freshartifacthub.io/changes, and a CHANGELOG entry.env:and must beX.Y.Z. Before, it was pasted into the script.GH_PAT_PACKAGESpushes the branch and opens the PR, so Chart CI runs. AGITHUB_TOKENPR would not run it, and this repository doesn't let Actions open PRs anyway.dry_runinput (manual runs): runs the whole path, opens the PR as a draft, then closes it and deletes its branch.Tested:
Chart.yamland CHANGELOG.actionlint1.7.7 (with shellcheck) is clean.dry_rundispatch on this branch is recorded below.🤖 Generated with Claude Code