README_RELEASE_PROCESS.md

When you are about to do a release, and not before:

For automated release process:

1. Ensure you run `npm run tojson' to copy the data out of levelDB files and into JSON, since LevelDB files are not checked in
2. Merge all changes into main
3. Commit version.txt File with new release version number in it (no 'v')
4. GitHub Action will automatically create a draft release
5. Edit draft release notes and title
6. Publish the release

For manual release process:

1. Ensure you run `npm run tojson' to copy the data out of levelDB files and into JSON, since LevelDB files are not checked in
2. Merge in all changes to main
3. Update system.json to change the version number at the top
4. Update system.json to change the zipfile path at the bottom (you have to guess the path, because you haven't created release yet)
5. Update system.json to change the manifest path at the bottom (you have to guess the path, because you haven't created release yet)
6. Create a release in Github with new version number
7. Go through commits since last release and use them to create release notes
8. Publish the release
9. Update Foundry admin with new release paths for both download and manifest