forked from beakerbrowser/beaker
-
-
Notifications
You must be signed in to change notification settings - Fork 0
Dev doc: New release process
Alexander Frick edited this page Feb 5, 2024
·
1 revision
To make a new release of beaker, follow these steps:
- Run the tests. Always gotta run the tests.
- Create and publish a new releases page on beakerbrowser.com.
- Update app/package.json to the new version number.
- Update the builtin start page to reference the new version number and its release page.
- Commit, tag, and push. (The pushed tag will trigger appveyor's build process.)
- Create a new release draft off of the tag.
- Build on OSX. Add
latest-mac.yml
, the.dmg
, and the.zip
to the release draft. - Build on Linux. Add
latest-linux.yml
and the.appimage
to the release draft. - When appveyor finishes, download
latest.yml
and the.exe
and add them to the release draft. - Publish the new release.
- Update the links on beakerbrowser.com's install page and publish.