-
Notifications
You must be signed in to change notification settings - Fork 107
How to release a new version
Tom edited this page Aug 4, 2024
·
5 revisions
The process for maintainers.
-
Try to give any downstreams (Web, iPad) a heads-up in advance.
-
If minor version: merge release into master. Remove all version guards.
-
Update versions in Rogue.h, Info.plist, variants, and seed catalog dungeon version.
-
Delete test recordings if outdated.
-
Run
tools/bullet-points changes/*.md
, fix formatting, rephrase, and add entry to CHANGELOG.md. -
Delete changes files.
-
Commit and push to gha-build branch.
-
Download artifacts from gha-build Action. Test with
tools/gha-release
or equivalent. -
Make version tag.
-
Merge gha-build into release.
-
If minor version: merge master into release.
-
Push all above.
-
{summary} <details> <summary>Changes</summary> {changelog} </details>
-
Post to /r/brogueforum.
Adventurers, An update for Brogue CE is now available! [Download for Windows, Mac, and Linux](https://github.com/tmewett/BrogueCE/releases) {summary} {changelog}
-
Post to roguelikes Discord.
-
If minor version: cross-post to /r/roguelikes.