- Have all of the 6 core Cro projects
- cro-core
- cro-tls
- cro-http
- cro-websocket
- cro-webapp
- cro as well as the website (cro-website) checked out in a folder.
- Ensure the
fezprogram is available and you are logged in and are a member of thecroorg. - Ensure all the clones of each project have a remote called
originthat allows writes. - Change the version numbers in
versions.jsonto the versions you want to release. Keep the versions of modules you don't want to release unchanged. - Run
release.raku --preparein the parent folder of of the above mentioned repos. This will then automatically do the following:git pullin all the repos- Create a commit and push in
crothat bumps the OCI image version. - For each distro that has a changed version number in
versions.json:- Update the
versionandapiinMETA6.json. - Update all the
dependsversions of the other Cro distros inMETA6.json. - Update the version in the
Changesfile. - Create a commit and push.
- Update the
- Create and push a release tag in all updated distros.
- Add a skeleton release announcement section to
cro-website/docs/releases.md.
- Complete the pre-generated release notes in
cro-website/docs/releases.md. - Commit, push and publish the release announcement.
- Commit and push the changes to the
versions.jsonfile.
-
Notifications
You must be signed in to change notification settings - Fork 0
croservices/release
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
About
A tool to help the Cro maintainers make Cro releases
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published