Repository navigation
Announce installer releases in Change Log discussions - #62
Merged
Merged
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
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.
After a Windows installer is uploaded and its release is published, automatically announce it in Change Log Discussions with a direct EXE download link, a brief plain-text overview, published documentation links, and changed files with diff previews. Full diffs and patches link to immutable commit comparisons; the announcement includes no PR links.
Select the correct published documentation pages through
Documentation:lines in the merged engine PR description. Require an explicit mapping orDocumentation: nonefor changes without a docs update. Copy the engine PR's labels to the Discussion and synchronize them on reruns.Retries update the existing announcement for the release. Failed uploads never announce; announcement or label failures leave the release available and can be repaired by rerunning publication. Add the required Discussions permission and document configuration, preview limits, and recovery.
Validation: all 21 release automation tests pass; actionlint v1.7.7 passes for all workflows; git diff --check passes. Read-only GitHub API checks confirm category discovery, Discussion label queries, and commit comparisons work. No live announcement was posted during testing.
Documentation: none