docs(release): document manual publish + actions allowlist gotchas#106
Merged
Conversation
The GitHub Release does not auto-trigger maven-publish: release.yml creates the release with the default GITHUB_TOKEN, and GitHub does not fire workflow triggers for GITHUB_TOKEN-raised events. So the deploy to Packages must be dispatched manually with `gh workflow run maven-publish.yml -f tag_version=v<version>`. Also document the Actions allowlist gotcha (a bumped/non-allowlisted action makes workflows fail at startup_failure), and correct the release diagram/steps to reflect the manual publish.
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.
Summary
Corrects the Release flow docs in
CLAUDE.mdto match reality:maven-publish.yml, becauserelease.ymlcreates the release with the defaultGITHUB_TOKENand GitHub doesn't fire workflow triggers forGITHUB_TOKEN-raised events. Documents the requiredgh workflow run maven-publish.yml -f tag_version=v<version>step and a suggested permanent fix.startup_failurewith no jobs. Documents how to diagnose/fix.Why
A tagged release currently publishes nothing to Packages unless someone manually dispatches the publish — that surprised us (v1.12.0 sat un-published). This documents the trap so the next person doesn't lose time.