aboutsummaryrefslogtreecommitdiff
path: root/PUBLISH.md
diff options
context:
space:
mode:
authorRemy Raes <raes.remy@gmail.com>2022-09-18 01:01:36 +0200
committerRemy Raes <raes.remy@gmail.com>2022-09-18 01:01:36 +0200
commitc468e59fb9e9c71833165358f96cbc1ae1f18a83 (patch)
treebb70bb59c7eba7aaa917cc8881dfe26928848c1c /PUBLISH.md
parenta33068cef1e973035e801eb2d3299121f54c216a (diff)
downloadViper-c468e59fb9e9c71833165358f96cbc1ae1f18a83.tar.gz
Viper-c468e59fb9e9c71833165358f96cbc1ae1f18a83.zip
docs: update publish documentation
Diffstat (limited to 'PUBLISH.md')
-rw-r--r--PUBLISH.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/PUBLISH.md b/PUBLISH.md
index 761d2fe..f4833be 100644
--- a/PUBLISH.md
+++ b/PUBLISH.md
@@ -8,3 +8,16 @@
6. Build and publish with `npm run publish:[windows/linux]`
- Optionally just use `build/publish.sh`, however that only works on Linux/Systems with a `/bin/sh` file, it also checks whether all files have been localized, and that the version numbers have been updated
7. Edit the draft release message and publish the new release!
+
+## CI release
+
+If you don't want to build releases yourself, you can make GitHub build them for you!
+
+ 1. Make sure your code works!
+ 2. Update `package.json` version
+ 3. Make sure `package.json`'s `repository.url` key references correct repository
+ 4. Ensure application builds correctly with `npm run build:[windows/linux]`
+ 5. Create a prerelease with newest version name
+ - Creating the prerelease will trigger CI, that will build all executables
+ - You can use build time to update release notes :)
+ 6. When all binaries have been uploaded to the prerelease, you can publish it! \ No newline at end of file