Improve release workflow with human-curated notes #303
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
- Add manual workflow to create draft releases with editable notes - Update release workflow to publish draft releases when PR is merged - Add step to review merged PRs since last release - Ensure curated release notes are published before emails go out Co-authored-by: Amp <[email protected]> Amp-Thread-ID: https://ampcode.com/threads/T-99dc31fc-f060-481a-b490-7c7c10691358
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.
Problem
Currently, releases are automatically published with auto-generated notes, then manually updated afterward. This means release notification emails go out with placeholder content before the curated notes are ready.
Solution
This PR introduces a two-stage release process:
Changes
New Workflow
Benefits