Skip to content

ci: release-please + helm push to GHCR OCI#8

Merged
hbrombeer merged 1 commit intomainfrom
feat/release-pipeline
Apr 26, 2026
Merged

ci: release-please + helm push to GHCR OCI#8
hbrombeer merged 1 commit intomainfrom
feat/release-pipeline

Conversation

@hbrombeer
Copy link
Copy Markdown
Member

Summary

  • release-please-config.json (release-type: helm, pre-major bumps, no component-in-tag)
  • .release-please-manifest.json seeded 0.0.0
  • .github/workflows/release.yml — release-please → helm package → helm push to oci://ghcr.io/groundsgg/charts

Test plan

  • release-please action wires up; release-PR will be opened on next conventional commit on main
  • First v0.1.0 release blocked on T10 (plugin-agones #36 merge + velocity image bump). Workflow correctness verified by the next dev tag.

Plan: grounds-platform/docs/plans/2026-04-26-platform-vcluster-template.md (T9)

release-please-config.json: type=helm, bump-minor-pre-major, no
component-in-tag.

release.yml: on push to main, release-please runs; if release_created,
the helm-push job packages the chart and pushes to
oci://ghcr.io/groundsgg/charts. Tag/version mismatch is a hard fail
(release-please should keep them in sync via the helm release-type's
Chart.yaml version updater).

No v0.1.0 release is cut here — that waits on plugin-agones #36 merge
+ velocity image bump (T10). Until then, only the dev/edge tag flow
exercises the pipeline if a feat/* commit lands on main.
@hbrombeer hbrombeer merged commit 12cd7bd into main Apr 26, 2026
1 check passed
@hbrombeer hbrombeer deleted the feat/release-pipeline branch April 26, 2026 12:01
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