From 1be7adf70497493e49de7b5aa6d373c68564cc74 Mon Sep 17 00:00:00 2001 From: YoshiRulz Date: Wed, 27 Nov 2024 23:54:57 +1000 Subject: [PATCH] Updated Release checklist (markdown) --- Release-checklist.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Release-checklist.md b/Release-checklist.md index 391b27f..fcf41ca 100644 --- a/Release-checklist.md +++ b/Release-checklist.md @@ -13,7 +13,7 @@ Note that some of these can be done concurrently. 1. Update the `release` branch to point to `master` - [GitLab CI](https://gitlab.com/TASVideos/BizHawk/-/pipelines?page=1&scope=all&ref=release) will build the `release` branch shortly after pushing it. 1. Check for AV false positives - - Separately upload the release archive and `EmuHawk.exe` alone to [VirusTotal](https://www.virustotal.com/gui/home/upload). A false positive from the Microsoft engine is the only one that really matters. + - Separately upload the release archive and `EmuHawk.exe` alone to [VirusTotal](https://www.virustotal.com/gui/home/upload). A false positive from the Microsoft engine is the only one that really matters. (And there's no need to check the Linux release since bad AV isn't a concern there.) - If it does happen... add a random `` to the assembly or something and try again idk ¯\\\_(ツ)\_/¯ 1. Create a "Release" on GitHub - Check the date—if it's April 1st or thereabouts, ABORT MISSION. Seriously, it's just not worth it.