Skip to content

How to release a new version

Tom edited this page Aug 4, 2024 · 5 revisions

The process for maintainers.

  1. Try to give any downstreams (Web, iPad) a heads-up in advance.

  2. If minor version: merge release into master. Remove all version guards.

  3. Update versions in Rogue.h, Info.plist, variants, and seed catalog dungeon version.

  4. Delete test recordings if outdated.

  5. Run tools/bullet-points changes/*.md, fix formatting, rephrase, and add entry to CHANGELOG.md.

  6. Delete changes files.

  7. Commit and push to gha-build branch.

  8. Download artifacts from gha-build Action. Test with tools/gha-release or equivalent.

  9. Make version tag.

  10. Merge gha-build into release.

  11. If minor version: merge master into release.

  12. Push all above.

  13. Make release on GitHub.

    {summary}
    
    <details>
    <summary>Changes</summary>
    
    {changelog}
    
    </details>
    
  14. 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}
    
  15. Post to roguelikes Discord.

  16. If minor version: cross-post to /r/roguelikes.

Clone this wiki locally