-
-
Notifications
You must be signed in to change notification settings - Fork 536
The Release Process
George Dawoud edited this page May 2, 2026
·
9 revisions
Fully automated release workflow with one-click publishing.
-
Check master build: Verify green build at build-test-package.yml
-
Trigger release: Run Release & Start Next workflow:
- Enter
next_version(e.g., 7.2.4, 7.3.0) - Check
prereleaseif RC/beta, otherwise leave unchecked - Leave
draft: trueto review before publishing
- Enter
-
Review & publish: Go to Releases, review draft, click "Publish release"
-
Auto-triggered: When published, the Release: Changelog, Milestones & Marketing workflow runs:
- Generates changelog entry in
changelog/<tag>.md - Updates
CHANGELOG.md - Generates social media posts
- Closes release milestone (stable releases only)
- Moves pending issues/PRs to next version (stable releases only)
- Generates changelog entry in
-
Merge version bump: Merge the auto-opened "Start release" PR
| Workflow | When | What |
|---|---|---|
release-publish.yml |
Manual dispatch | Creates GitHub Release from latest build |
release-prepare.yml |
Auto (by publish) | Bumps version, opens PR |
sync-changelog.yml |
Auto (on publish) | Changelog + milestones (skip for pre-releases) |
Updated: 2026-05-02 — Fully automated workflow (was manual process)
- Home
- Wiki → Docs links — User & admin manuals moved to docs.churchcrm.io
→ docs.churchcrm.io for installation & setup
- Installation ← Start here!
- First Run Setup
- Features Overview
→ docs.churchcrm.io for user manuals
- User Guide (docs)
- People Management — docs
- Groups & Events
- Tools
- Finances
→ docs.churchcrm.io for admin manuals
- User Management
- System Maintenance
- Configuration
- Troubleshooting
- Localization
Contributing to ChurchCRM
- Quick Start
- Testing & CI/CD
- Code & Architecture
- Localization
- Release & Security