fix(ci): remove the duplicate release workflow - #102
Merged
Conversation
release.yml fails on every release and publishes nothing that release-please.yml has not already published. The most recent run failed at "Push to NuGet, with Conflict — release-please.yml had already pushed". The release itself succeeded regardless: release-please.yml packs and pushes every package in this repo, and the current manifest version is on NuGet for all of them. So release.yml can only ever fail — it either re-pushes a package that already exists or re-creates a release that already exists — and leaves a red run on every release. That is worse than useless: a release that always shows failures is a release nobody reads, which is exactly when a genuine failure needs to be visible. Deleting rather than repairing, because a working release.yml would double-publish what release-please.yml already pushes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
release.ymlfails on every release and publishes nothing thatrelease-please.ymlhas not already published.Most recent run failed at: Push to NuGet, with Conflict — release-please.yml had already pushed
The release still succeeded.
release-please.ymlpacks and pushes every package in this repo, and the current manifest version is live on NuGet for all of them. Verified before opening this.So
release.ymlcan only ever fail — it either re-pushes a package that already exists (Conflict) or re-creates a GitHub release that already exists. Every release shows red while working perfectly, which is how a genuine release failure gets missed.Deleting rather than repairing: a working
release.ymlwould double-publish whatrelease-please.ymlalready pushes, so there is no version of this file that earns its place.Same change as ZeroAlloc.Saga#99, which found the pattern.
🤖 Generated with Claude Code