ci: make Azure feed + GHCR best-effort; tag only after PyPI publishes#9
Merged
Conversation
The release reached publishing but failed at the private Azure feed step (401 Unauthorized - expired PAT), which skipped the public PyPI publish (publish-pypi needs: release). The Azure feed and GHCR image are UiPath-internal targets and must not gate the public release. - continue-on-error on the Azure feed + the three GHCR steps, so their failure no longer blocks the release job (and thus PyPI). - Move the `v<version>` tag push into a dedicated tag-release job that needs [release, publish-pypi], so the tag lands only after PyPI has actually published -- a failed publish no longer leaves a tag that the re-release guard would block on retry. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Claude finished @uipreliga's task in 1m 34s —— View job PR Review in Progress
|
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.
Problem
The release reached publishing but failed at the private Azure feed step (
401 Unauthorized— expired PAT), which skipped the public PyPI publish (publish-pypineeds: release). The Azure feed + GHCR image are UiPath-internal targets and must not gate the public release.Change
continue-on-error: trueon the Azure feed step + the three GHCR steps → their failure no longer blocks the release job (or PyPI). Public PyPI publishes first; Azure/GHCR are best-effort.v<version>tag push into a dedicatedtag-releasejob (needs: [release, publish-pypi]) so the tag lands only after PyPI has actually published — a failed publish no longer leaves a tag that the re-release guard would block on retry.Net: PyPI-first, resilient release.
🤖 Generated with Claude Code