Improve release workflow reliability with auth, retry logic, and marker update fix #91
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
This PR fixes issues in the release pipeline:
Add GitHub token authentication to API requests - Prevents rate limiting from unauthenticated GitHub API calls
Move release marker update to end of build workflow - Previously,
.current-releasewas updated incheck_release.ymlbefore the build ran. If the build failed, the marker was already updated, so retries wouldn't trigger. Now the marker is only updated after a successful build.Add retry logic for git push - If main branch moves forward during the build, the push will retry with rebase to handle race conditions.
Downgrade
release_versionto last successful build.Changes
check_release.yml: AddGH_TOKENauth, remove premature marker update, pass secrets to called workflowcreate_release.yml: AddGH_TOKENauth, add release marker step at end, add push retry with rebaseTesting
These changes have been tested in a fork where releases are being built successfully: https://github.com/vakesz/Apollo