-
Notifications
You must be signed in to change notification settings - Fork 449
The Release Process
Robert Spencer edited this page May 10, 2024
·
6 revisions
-
Verify that the
master
branch has a clean build - https://github.com/ChurchCRM/CRM/actions/workflows/build-test-package.yml?query=branch%3Amaster -
Download the artifact from the latest successful clean build.
- Unzip
ChurchCRM.x.y.z-files
and confirm the presence of a.zip
file.
-
Start a new release on GitHub by visiting https://github.com/ChurchCRM/CRM/releases/new
-
Ensure to select the same commit ID for the release as the one from the downloaded build above.
-
Automatically generate release notes using the provided
Generate release notes
functionality.
-
Upload the
.zip
file to the release. -
Complete the release process on GitHub.
-
Close the previous milestone by visiting https://github.com/ChurchCRM/CRM/milestones.
Looking for the old, deprecated release process? see https://github.com/ChurchCRM/CRM/wiki/Release-Procedure