From 491604075bc3cd2d05277a38ce34f311d5a3d6da Mon Sep 17 00:00:00 2001 From: MattIPv4 Date: Sat, 25 Jan 2025 23:45:14 +0000 Subject: [PATCH] Determine new version as first step --- RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 0b5707f..b27923b 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -1,5 +1,7 @@ # Releasing a new version on Twitch +First and foremost, we need to establish the new version number. Compare `main` to the most recent tagged version in the repository and decide if the release is a minor (new features) or patch (bug fixes) release. The commit being submitted to Twitch should be tagged via git with `git tag v` if you're currently at the commit being used, or `git tag v ` if not. Once the tag is created, push it with `git push origin v`. + ## Local test All new versions start in local test where the base URI is `https://localhost:8080/`, allowing a locally run version to be tested. @@ -14,8 +16,6 @@ Once local testing is complete, a build can be created with `pnpm build`, the fi With the assets hosted on Twitch, install the extension version on a test channel and verify that everything is working as expected when running from Twitch. -At this point, the commit being submitted to Twitch should be tagged via git. Do so with `git tag v` if you're currently at the commit being used, or `git tag v ` if not. Once the tag is created, push it with `git push origin v`. - ## Submit for review With the extension installed on a test channel, submit the extension for review, providing the URL for the channel to use for testing.