Repository navigation
Conversation
release.yml's last job, after github-release, mints a release-bot App token and sends repository_dispatch `api-release` with the tag to service-api-standard and service-api-chain; their bump-api.yml opens the go.mod bump. GITHUB_TOKEN can't dispatch across repositories. Both services are tried even if one fails, and since everything else has published by then, a failure is re-run alone. Part of #90; needs #89 for the App credentials. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 tasks
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.
Summary
Part of #90.
release.ymlgains a final job,dispatch-services,needs: [github-release]. It:GITHUB_TOKENcan't sendrepository_dispatchto another repository.api-releasewithclient_payload.versionset to the tag to both services. Theirbump-api.yml(Bump metacensus/api automatically when it releases service-api-standard#14, and Bump metacensus/api automatically when it releases service-api-chain#27 in progress) opens the bump PR.Because it runs last, a service is only told about a version that has fully published. If it fails, re-running this job alone is the recovery, as the comment beside it says. AGENTS.md's "Releasing" now mentions it.
Safe to merge before the App exists
Only the next release would notice. Until #89 creates
RELEASE_BOT_APP_IDandRELEASE_BOT_PRIVATE_KEY, this job fails at "Mint the release-bot token". The module, npm package and GitHub release are already published by then, so nothing is lost, but that release's run would show red. Merge this once #89 is done, or accept one red run.Testing
actionlintv1.7.7 is clean on every workflow.GH_DEBUG=apiagainst an unreachable host, so nothing was sent:{"client_payload": {"version": "v0.8.0"}, "event_type": "api-release"}, which is whatbump-api.ymlreads (github.event.client_payload.version).bump-apirun for that version.🤖 Generated with Claude Code