1
0
mirror of https://github.com/RipMeApp/ripme.git synced 2025-09-25 21:29:23 +02:00

Add new release instructions

metaprime
2025-01-07 14:33:04 -08:00
parent 6ec4916ffa
commit 4ce41baa6c

@@ -1,3 +1,43 @@
# Publishing a New Release
(These instructions are a work in progress.)
## Create the Release
edit draft release `develop build main` the following way:
1. create a new tag with version from ripme filename, e.g. 2.1.12-7-d0b97acd
1. set the title to same name
1. set previous tag to release tag before, e.g. 2.1.11-20-ca96ce88
1. press `generate release notes` button
1. edit release text as appropriate
1. save
Another version of instructions that worked for @metaprime:
- Push latest-main to the version you will want to publish, and wait a few minutes for automation to finish running the build
- Go to https://github.com/RipMeApp/ripme/releases
- Find development build main
- Click the "Edit" button
- Note the version in the filename for the .jar
- Push a tag with that version number
- Update the tag on the release to that version numbered tag that matches the .jar's name
- Change the title on the release to match
- Uncheck "set as a pre-release"
- Check "set as the latest release"
- Click "publish release"
## Publish the JSON update so the update check will pick up the new release
then, prepare the repo for update check, and next release:
1. edit ripme.json, enter new hash, version and short description, and commit
1. Get the hash by downloading the file and computing a sha256 hash
1. set the base tag for next release verison calculation, e.g. 2.1.13 on this commit
1. push tag and commit
1. remove old base tag, not needed any more, e.g. 2.1.12
---
# Previous Instructions (2018 and before)
Note: To make a new ripme release you must have write access to ripmeapp/ripme and have a github api token
Step 1: Update your local copy of ripme with `git pull origin master`