Repository navigation
👷 ci: remove finalize-github-release workflow - #297
Merged
Merged
Conversation
The recovery path in this workflow fails with a 403 when it publishes the GitHub release. Releases go through the normal release workflow instead, so this workflow has no remaining purpose.
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.
The
finalize-github-releaseworkflow was added in #295 and #296 to finish releases whose GitHub release step hit a 403. That recovery path fails with the same 403, and the maintainer chose normal releases instead, so the workflow has no purpose left.Nothing else references it. Releases continue through the existing release workflow, which this change leaves untouched.