Repository navigation
ci(auto-version): retry the release dispatch and fall back to the release token - #337
Merged
Merged
Conversation
…ease token A tagged version whose dispatch fails is never released: the next run tags past it. The job token shares the repository's installation quota with the scans on every push to main, and a run of merges exhausts it.
Contributor
Vulnetix config planManager
0 to create, 1 to update, 0 to delete, 0 unchanged |
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.
What
The
Dispatch releasestep inauto-version.ymlnow retriesgh workflow run release.ymlthree times (20s/40s/60s backoff) with the job token, then tries once more withPACKAGES_TOKEN. If every attempt fails, the step fails with an error that prints the exact manual dispatch command.Why
The tag is pushed before the dispatch. When the dispatch fails, that version has no release, and the next run tags past it. The job token shares the repository's hourly installation quota with every scan triggered by the push to main. On 2026-11-13 a run of merges spent that quota, and every dispatch after the first failed with
API rate limit exceeded for installation.PACKAGES_TOKENhas its own quota, andrelease.ymlalready publishes with it.How verified
actionlint .github/workflows/auto-version.ymlpasses.main.