-
Notifications
You must be signed in to change notification settings - Fork 514
The Release Process
-
Verify that the
masterbranch 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-filesand confirm the presence of a.zipfile.
-
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 notesfunctionality.
-
Upload the
.zipfile 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?
- Installation Guide ← Start here!
- First Run Setup
- Features Overview
Day-to-day usage of ChurchCRM
- User Documentation
- People Management
- Groups & Events
- Tools
- Finances
Server management & configuration
- User Management
- System Maintenance
- Configuration
- Troubleshooting
- Localization
Contributing to ChurchCRM
- Quick Start
- Testing & CI/CD
- Code & Architecture
- Localization
- Release & Security