-
-
Notifications
You must be signed in to change notification settings - Fork 52
Release process
This is the process I go through to create a release, once the 'main' branch is ready.
- Ensure main is up to date:
git checkout main
git pull
- Bring release up to date
git checkout release
git merge main
- Edit release info. Normally, we do not update the readme to the new version until release time (because people check out the github page and don't understand that 'main' is a development branch).
-
Add release date to changelog.md. Enumerate changes (since they might be displayed to users upon version change).
-
Update Readme.md to release version
-
Update system.json to release version:
"version": "0.15.5",
-
Update system.json to point to specific release download (which I assume is driven by the tag):
"download": "https://github.com/crnormand/gurps/archive/0.15.5.zip",
-
Commit and push the release branch, and then create the pull request to merge to main. I usually copy and paste the changelog section for that release as the commit comment.
-
Draft a new release
-
Create a new tag (e.g. '0.15.5')
-
Select the 'release' branch as the Target
-
Use the tag name (e.g. '0.15.5') as the release name
-
Paste the changelog section into the description
-
Click the Publish release button.
**And finally, I go to the main branch https://github.com/crnormand/gurps, and it should notify you that the "release" branch has a commit that can be merged, so I merge it. **
Current users will be notified of the version update, since all of our releases are using the same manifest:
"manifest": "https://github.com/crnormand/gurps/releases/latest/download/system.json",
However, they can get a specific version of they want by using the release specific manifest: https://raw.githubusercontent.com/crnormand/gurps/0.15.5/system.json
. And this is the manifest that Foundry uses.
Also, new users will only see the version provided by Foundry (and I have to go into the Foundry release manager to create a new entry for our release). However, they can install an older version, and the next time they connect, it will let them know there is an update.
- Home
- Getting Started
- Modifiers and the Modifier Bucket
-
Cool Macros
- Clear All Active Effects
- Last Targeted Roll demo and margin of success
- Fright Check
- Fireball Damage
- Scale Lighting
- Quick Combat
- Manual Damage
- Quick-Draw and Shoot
- Toggle Reeling or Exhausted
- Roll Attack and Critical Hit
- Create and Toggle Active Effect
- Bad Footing Active Effect
- Spell Damage
- Major Healing
- Missile Spell Handler Template
- Melee Spell Strike Handler Template
- Alternate Form
- Multiple Quick Contests
- Open/Close Helmet Visor
- Advanced Features
- Useful OTFs
- User Recommended Modules