ci: publish every release to the Bend hub by name - #55
Merged
Merged
Conversation
release-please.yml gains a publish job: when release-please cuts a release, the shared publish workflow (Emerging-Patterns/actions 0fb03f8) sends the tag to the hub under this repo's hub name, after the proof gate and the LICENSE and name checks. publish.yml becomes the manual retry, with a dry-run that checks everything and uploads nothing. 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
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.
Adds a publish job after release-please (shared Emerging-Patterns/actions publish.yml @0fb03f8, hub name set in the caller, BEND_HUB_KEY repo secret) and turns publish.yml into a manual retry with dry-run.
🤖 Generated with Claude Code