feat(ci): auto-release on lab frontend dispatch with exact version pin - #68
Merged
Conversation
The release workflow now also triggers on a frontend-release dispatch from ethpandaops/lab (and on workflow_dispatch), computing the next tag and pushing it itself, so backend releases no longer need a manual tag. The embedded frontend release is resolved once in the workflow and pinned exactly through the Makefile, goreleaser ldflags, Docker build args, an image label, and the release notes header, fixing the empty frontend_version in production images. Claude-Session: https://claude.ai/code/session_01MW57Wwhb2PA4rjwP7PBv1b
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
1 participant
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.
The goreleaser workflow (renamed to
release) now also triggers on afrontend-releaserepository dispatch from ethpandaops/lab and on manual workflow_dispatch: it computes the next tag, pushes it, and releases — no more tagging by hand after every frontend release. The embedded frontend release is resolved once in the workflow and pinned exactly through the Makefile (FRONTEND_TAG), goreleaser ldflags, the Docker build, anio.ethpandaops.frontend.versionimage label, and a release-notes header. This also fixesfrontend_versionbeing empty in production, since it was read from.tmp/frontend-version.txtat runtime, which never exists in the image. Alpha frontend tags (fusaka-v0.0.3) produce suffixed prereleases (v1.3.45-fusaka) via the existingRELEASE_SUFFIXmachinery, now driven byprerelease: autoin the goreleaser config instead of appending to a copy of it.No new secrets needed: the dispatch is received with the default
GITHUB_TOKEN, and tags it pushes don't re-trigger the tag-push path. Pushing a tag manually still works as before.https://claude.ai/code/session_01MW57Wwhb2PA4rjwP7PBv1b