diff --git a/docs/team/Making-A-Release.html b/docs/team/Making-A-Release.html index cbc9a75..c110d92 100644 --- a/docs/team/Making-A-Release.html +++ b/docs/team/Making-A-Release.html @@ -6,14 +6,13 @@ title: Making A Release

Prepare

    -
  1. Update the version numbers in scripts/git/pre-commit, src/backend/app/loot_version.cpp.in, src/resource.rc and scripts/installer.iss.
  2. +
  3. Update the version numbers by running node scripts/set_version_number.js <version>.
  4. Make sure that the version histories in docs/api/changelog.rst, docs/app/changelog.rst and docs/metadata/changelog.rst have the correct changelogs for the new release and that its release date is set.

If the new release makes metadata syntax changes:

    -
  1. For each masterlist, create a new version branch for that release.
  2. -
  3. For each masterlist, set the default repository branch on GitHub to the new branch.
  4. +
  5. Run lomad using lomad -t <github personal access token> -a -b <branch name> to (for all masterlists) create a branch for that release and make it the default.
  6. Update the default masterlist branch settings for each game in src/backend/game/game_settings.cpp and add the old default branch to LootSettings::oldDefaultBranches in src/backend/app/loot_settings.cpp.
@@ -28,5 +27,5 @@ title: Making A Release
  1. Post an announcement in the official forum thread.
  2. -
  3. Update the "update released" message version check in each masterlist's default branch.
  4. +
  5. Update the release notification message for all masterlists using lomad -t <github personal access token> -a -n <new version>.