chore: remove release-please, use tag-based releases #205
+22
−114
Conversation
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
Release-please added complexity without value since versions need to be manually specified anyway to stay in sync with Fable. Replaced with a simpler workflow that triggers on GitHub release publish events. - Replace release-please workflow with publish-on-release workflow - Remove release-please-config.json and .release-please-manifest.json - Clean up duplicate entries in CHANGELOG.md - Simplify RELEASING.md with new process Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
release-please-config.jsonand.release-please-manifest.jsonCHANGELOG.mdcaused by release-pleaseRELEASING.md— releases are now created via the GitHub UIRelease-please added complexity without value since versions need to be manually specified anyway (via
Release-As:) to stay in sync with Fable. The new workflow is: create a GitHub release with a version tag → NuGet package is built and published automatically.Test plan
🤖 Generated with Claude Code