diff options
| author | 0neGal <mail@0negal.com> | 2022-05-20 21:39:40 +0200 |
|---|---|---|
| committer | 0neGal <mail@0negal.com> | 2022-05-20 21:39:40 +0200 |
| commit | 2ee3f1cf7eb7159ce80ac561318eeff8a0229ef9 (patch) | |
| tree | b3b8e80a826dd9c48a997d5c176faa94227d571b | |
| parent | fa6a75629d0a84bb7cde182bfe63b8d3808c7244 (diff) | |
| download | Viper-2ee3f1cf7eb7159ce80ac561318eeff8a0229ef9.tar.gz Viper-2ee3f1cf7eb7159ce80ac561318eeff8a0229ef9.zip | |
updated PUBLISH.md
It now contains info about `build/publish.sh`
| -rw-r--r-- | PUBLISH.md | 15 |
1 files changed, 8 insertions, 7 deletions
@@ -1,9 +1,10 @@ # Publishing a new release -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. Expose `GH_TOKEN` environment var with your Github token -6. Build and publish with `npm run publish:[windows/linux]` -7. Edit the draft release message and publish the new release!
\ No newline at end of file + 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. Expose `GH_TOKEN` environment var with your Github token (`build/publish.sh` asks for it) + 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! |