Repository navigation
Automate release preparation and centralize release notes - #260
Merged
Merged
Conversation
Deploying showcode with
|
| Latest commit: |
f6336c0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d1388540.showcode.pages.dev |
| Branch Preview URL: | https://codex-release-automation.showcode.pages.dev |
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.
Release notes currently have to be maintained separately for the changelog, What's New, and desktop releases. Each release now has one Markdown entry with its version, description, optional image, and notes, which supplies all three.
A Prepare release action drafts the entry from commits since the previous release and opens a PR with the package version updates. Merging the reviewed release PR passes its exact commit to the desktop build workflow. Ordinary feature merges do not start desktop releases.
The existing 3.0.0 notes are migrated without changing their announcement ID or bumping the version. The desktop automation has already merged, and the release bot is configured in both repositories.
Validation: 249 application tests, release-script checks, workflow linting, and the production web build passed.