summaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorLibravatar Vijay A <vraravam@users.noreply.github.com>2023-10-02 21:42:39 +0530
committerLibravatar Vijay A <vraravam@users.noreply.github.com>2023-10-02 21:42:39 +0530
commitb7d721db1f7008216fdf6183a0edaea12a1aa0fb (patch)
treed5dfd998b655cd8ef1ed5415a8e519feaacca4ae /CONTRIBUTING.md
parent6.5.0-nightly.21 [skip ci] (diff)
downloadferdium-app-b7d721db1f7008216fdf6183a0edaea12a1aa0fb.tar.gz
ferdium-app-b7d721db1f7008216fdf6183a0edaea12a1aa0fb.tar.zst
ferdium-app-b7d721db1f7008216fdf6183a0edaea12a1aa0fb.zip
Bump up version to the next nightly.0; Update Contributing doc to detail out more steps while releasing
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md11
1 files changed, 9 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8a6268274..ffda7acb9 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -186,8 +186,15 @@ git merge --no-ff nightly --no-verify
186# <run the build script for your OS from the `scripts` folder> 186# <run the build script for your OS from the `scripts` folder>
187# <add all pertinent changes to git> 187# <add all pertinent changes to git>
188# <create commit> 188# <create commit>
189# <create tag> 189git push upstream release
190git push 190# Note: Do NOT allow the GHA release process to create the tag automatically, since that will be at the SHA in the develop branch and not on the release branch - which is logically incorrect
191git tag v$(node -p 'require("./package.json").version')
192git push upstream --tags
193# Note: GHA will automatically build with publish since its the release branch
194# Note: Once the GHA action is completed, verify the builds (there should be 32 assets before publishing)
195gco develop
196# <If its a public release, manually bump to next nightly.0 version in package.json>
197# <If its a public release, manually fix homebrew-ferdium PR>
191``` 198```
192 199
193This will automatically trigger the build, as part of which, a new, draft release will be created [here](https://github.com/ferdium/ferdium-app/releases/). Once all the assets are uploaded (19 assets in total), publish the release (you will need elevated permissions in GitHub for doing this). The last commit of the `release` branch will be tagged. 200This will automatically trigger the build, as part of which, a new, draft release will be created [here](https://github.com/ferdium/ferdium-app/releases/). Once all the assets are uploaded (19 assets in total), publish the release (you will need elevated permissions in GitHub for doing this). The last commit of the `release` branch will be tagged.