feat(ci): one-click releases that auto-trigger lab-backend#445
Merged
Conversation
Add a cut-release workflow that computes the next version and publishes the GitHub release, and make the release workflow dispatch a frontend-release event to lab-backend once assets are uploaded, so the backend release no longer needs to be run by hand afterwards. Claude-Session: https://claude.ai/code/session_01MW57Wwhb2PA4rjwP7PBv1b
One workflow now handles both entry points: workflow_dispatch computes the next tag and creates the release itself (with GITHUB_TOKEN, since nothing needs to trigger off the publish event anymore), and a manually published release picks up at the build step as before. 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 release workflow now has a workflow_dispatch entry point: pick a patch/minor/major bump and it computes the next tag, publishes the GitHub release, builds the frontend, and attaches the archives — all in one run. Publishing a release by hand still works; the release event enters the same workflow at the build step. Once assets are uploaded, it sends a
frontend-releasedispatch to lab-backend with the new tag, so the backend release runs automatically instead of being tagged by hand. The flow is documented in RELEASING.md.The dispatch uses the existing
EPOBOT_TOKENsecret (same pattern as contributoor → contributoor-installer); release creation only needsGITHUB_TOKEN. Pairs with ethpandaops/lab-backend#68, which receives the dispatch.https://claude.ai/code/session_01MW57Wwhb2PA4rjwP7PBv1b