From 4e101465484df2b40f03f0b76bcd268c78efc937 Mon Sep 17 00:00:00 2001 From: jLynx Date: Sat, 6 May 2023 08:05:55 +1200 Subject: [PATCH] Updated Creating a prod stable release (markdown) --- Creating-a-prod-stable-release.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Creating-a-prod-stable-release.md b/Creating-a-prod-stable-release.md index ccfaa7a..8ca6133 100644 --- a/Creating-a-prod-stable-release.md +++ b/Creating-a-prod-stable-release.md @@ -1,12 +1,15 @@ **This is intended for maintainers only** +## Setting up the repo To create a prod/stable release, first go to https://github.com/eried/portapack-mayhem/tree/next/.github/workflows and edit the `past_version.txt` and the `version.txt` files * `past_version.txt` needs to be the current release (I.E if you are creating a new release and the old/current stable release is `v1.0.0` and you want the new version to be `v1.1.0`, then past version needs to be `v1.0.0`) * `version.txt` needs to be the version you want for your new release. So from the example above, that would be `v1.1.0` +## Running the pipeline +Once that is done then you need to create the draft stable release. You can do this by running the stable release pipeline on `next` branch https://github.com/eried/portapack-mayhem/actions/workflows/create_stable_release.yml -Once that is done then you need to create the draft stable release. You can do this by running the stable release pipeline https://github.com/eried/portapack-mayhem/actions/workflows/create_stable_release.yml - +This then create a draft release that you should be able to see in releases at the top https://github.com/eried/portapack-mayhem/releases +## Finishing off Once all is done, create a PR to merge the `next` branch into the `master` branch \ No newline at end of file