Skip to content

Commit

Permalink
πŸ“ [How to release a new version]
Browse files Browse the repository at this point in the history
  • Loading branch information
JulesFouchy committed Nov 2, 2024
1 parent 111cf31 commit 4cc3357
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions _How to release a new version.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,7 @@
- Remove the "WIP" in the version number in *CMakeLists.txt* and in *changelog.md*, and commit with the message "πŸ”– [beta-1] Release" (make sure to replace with the right version number).
- On GitHub create a new release with the exact same name as the COOLLAB_VERSION in the CMake (don't use emojis, it can cause problems on some platforms). Use a new tag with the same name as the version. As a description, use whatever is in the changelog for the new version. (NB: this will trigger a GitHub Action that will build the installers and put them on the release page)
- Increment the version number in *CMakeLists.txt* and add "WIP" to it. Also, create a new section in the changelog with the same name as the version and WIP at the end. Then commit with the message "πŸŽ‰ [beta-1] Started" (make sure to replace with the right version number).
- Update the message in *website/src/components/_Download.md*.
- Put the installers to download on our website (download them from [the GitHub page](https://github.com/CoolLibs/Lab/releases/latest) once the the GitHub workflow has finished creating them, and add them in this repo in *website/static* (keep the same names as what is already in the folder)). Commit with the message "🌐 [Website] New installers to download".
- Update the message in *website/src/components/_Download.md*. Commit with the message "🌐 [Website] New version released".
- Make an announcement on our Discord + thank the contributors if any (ptut, interns, etc.)
- Make a story on our Instagram
- Make a toot on Mastodon

0 comments on commit 4cc3357

Please sign in to comment.