This is an internally used checklist for releasing a new sonnet version, it is available publicly because there is no reason to hide it, and it makes it convenient for maintainers to find
- Run
codespell - Open new version PR (
dev-unstable->main) - Pass code review on new version PR
- Remove
-devtags from sonnet core modules (cmds and dlibs) - Ensure all updated cmds and dlibs receive new version
- Decide on name for new version
- Locally create toml changelog in sonnet-website repository by referencing new version PR diff and commit history
- Locally update command reference on website using
cmds_to_html.py - Locally update latest version download link on website
- Export changelog without name to draft gh release and PR, using a new git tag for the new version
- Merge PR
- Immediately publish website changes and publish github release with new version name
- Post to sonnet support server that a new version was released
- Update instances we manage, mainly Summit and Remi
- If any bugs occur, create new patch release and thoroughly test before publishing again