Repository navigation
ci: retry the GitHub release step so a transient API failure cannot strand a published package - #21
Merged
Merged
Conversation
…trand a published package
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Released as v1.1.1 — https://github.com/Tharga/Communication/releases/tag/1.1.1 |
This branch had an error being deployed
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.
The package is pushed to nuget.org before the GitHub release is created, so a transient GitHub API failure leaves a published package with no tag. The next build then recomputes the same version, pushes a duplicate that --skip-duplicate swallows silently, and the version after it never ships. Observed three times on 2026-08-17 during a GitHub incident.
Retries the release step five times and treats an already-created release as success, so a re-run is safe. Applied to both the release and the pre-release job.
The identical change is already merged in Cache, Crawler, MongoDB and Team.