Release Binaries

Verified: January 2022

When making a new release, the binaries should be uploaded to the GitHub Releases page in addition to the workshop page(s).

Version Numbers

Before building, some files need updating (in addition to the Changelogs) and committing to master:

• /TLM/SharedAssemblyInfo.cs:
  • AssemblyVersion
  • AssemblyCopyright (if necesasry)
• /TLM/TLM/UI/WhatsNew/WhatsNew.cs
  • CurrentVersion

If the game version has changed, you'll also need to update:

• /TLM/TLM/Util/VersionUtil.cs
  • EXPECTED_GAME_VERSION_U - set to value of BuildConfig.APPLICATION_VERSION
  • ExpectedGameVersion - see CurrentGameVersion for where to get the values
• /README.md
  • Update version in cities: skylines lozenge

Build & Verify

Choose build config as applicable:

• RELEASE - STABLE releases
• RELEASE TEST - TEST releases

Test in game, in particular the What's New panel should popup. Check the TMPE.log to make sure Expected C:SL and Actual C:SL versions match.

Release tag

On the Draft a new release screen:

• Tag = Version number (eg. 11.6.4.0; don't prefix with v)
  • If it's a hotfix, you can postfix the verison with something like -hotfix-1 etc.
• Release title = Same as Tag
• Description = Changelog
  • You can usually find the changelog in the description of the Milestone associated with the release
• Attach binaries = zipped binaries
  • TEST, STABLE, or both, depending on which workshop pages are getting updated
  • Remember: TEST and STABLE are two separate builds, one using RELEASE TEST and the other RELEASE
• If it's a TEST-only release, tick This is a pre-release

Save the release tag, it should automatically add the source code of current master branch.

Upload build .zip files to workshop as necessary.