Release-procedure

Updated 5 Days AgoPublic

Actions

In this document, "lily" refers to the git remote at r.lily-is.land .

• Make release branch from lily/servant
• Modify the version variables in CMakeLists.txt paying special notice to SOVERSION
• Run https://r.lily-is.land/the-kazv-project/release-utils/src/branch/servant/collect-changelog.perl under the root of the repository
• Paste the result into CHANGELOG.md
• For kazv only, modify moe.kazv.mxc.kazv.appdata.xml to add the new release
• Commit, with the title being Release vX.Y.Z
• Push and make a merge request on Forgejo, write a short statement describing the changes into the body of the merge request (the Summary part). This will be used in the release notes.
• After CI passes, merge the MR
• Tag the release with vX.Y.Z on the new lily/servant
• Make a Forgejo Release on the tag
• In https://r.lily-is.land/the-kazv-project/kazv.pg.kazv.moe add the changelog for the release
• When tag pipeline passes, download the artifact (AppImage) from the prod build
• Add the corresponding versions to craft-blueprints-project-kazv repo ( https://r.lily-is.land/the-kazv-project/craft-blueprints-project-kazv )
• Sign and upload the artifact to the package registry
• Add the links to the registry to the release
• For kazv flatpak build, add --gpg-sign=KEY to the commands