Repository navigation
fix(release): authenticate installer checks on shared runners - #57
Merged
Merged
Conversation
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.
Fixes #56.
The
installmatrix inrust-release.ymlcalled the GitHub release API anonymously on shared runner IPs. This occasionally fails with HTTP 403 despite a successful build, particularly on macOS. The regularinstallers.ymlalready passesGH_TOKENtoinstall.sh.GH_TOKEN: ${{ github.token }}to the release-install job.contents: read; the upstream build job retains its release-write permission.Validation: compared existing
install.shGH_TOKEN usage andinstallers.ymlworkflow. A release tag is required for actual end-to-end validation; no release was triggered and no installer run is claimed.