Don't need to check for AV false positives on Linux for reasons too long to explain in this margin

YoshiRulz 2025-01-08 02:41:00 +10:00
parent 4196dcb7e3
commit 6874fd18ec
1 changed files with 1 additions and 1 deletions

@ -13,7 +13,7 @@ Note that some of these can be done concurrently.
1. Update the `release` branch to point to `master` 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. - [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 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. (And there's no need to check the Linux release since bad AV isn't a concern there.) - Separately upload the Windows 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 `<EmbeddedResource/>` to the assembly or something and try again idk ¯\\\_(ツ)\_/¯ - If it does happen... add a random `<EmbeddedResource/>` to the assembly or something and try again idk ¯\\\_(ツ)\_/¯
1. Create a "Release" on GitHub 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. - Check the date—if it's April 1st or thereabouts, ABORT MISSION. Seriously, it's just not worth it.