Skip to content

[bulk] Enable release automation process (2026-03-09-001)#80

Merged
hdamker merged 2 commits intomainfrom
bulk/release-automation-onboarding-22851668827
Mar 9, 2026
Merged

[bulk] Enable release automation process (2026-03-09-001)#80
hdamker merged 2 commits intomainfrom
bulk/release-automation-onboarding-22851668827

Conversation

@camara-release-automation
Copy link
Copy Markdown
Contributor

Enable release automation for ClickToDial

TL;DR: This PR adds the release automation workflow and prepares the CHANGELOG structure for ClickToDial.

Note: Once merged, the release automation becomes active.
A Release Issue will be created automatically (if not existing yet) when release-plan.yaml is updated on main.

What is this?

The release automation workflow enables slash commands on Release Issues to manage your release lifecycle. Post these as comments on the Release Issue:

  • /create-snapshot — create a snapshot branch (updates versions, changelog entries, and release metadata automatically)
  • /discard-snapshot <reason> — discard a snapshot and return to planned state
  • /delete-draft — delete a draft release
  • /publish-release --confirm rX.Y — publish the release

Changes

File Description
.github/workflows/release-automation.yml Release automation workflow (pinned to @ra-v1-rc)
CHANGELOG.md Added forward-reference note
CHANGELOG/README.md Created index file (with historical reference)

What to do next

  1. Review the file changes above
  2. Merge this PR to activate the release automation

If release-plan.yaml was updated before this workflow was installed, you may need to trigger the workflow manually once to create the initial Release Issue:

Release lifecycle overview
  1. Plan — update release-plan.yaml with target release tag, type, and API versions/statuses
  2. Develop — continue work on main branch with version fields set to wip
  3. Create Snapshot — post /create-snapshot on the Release Issue to generate a Release PR
  4. Review & Merge — review Release PR (includes CHANGELOG entry), obtain approvals, merge it
  5. Publish — post /publish-release --confirm rX.Y to finalize the release

If issues arise: use /discard-snapshot (during review) or /delete-draft (during draft phase) to return to planned state and make corrections on main.

More details: Release Lifecycle

Documentation

📖 Release Management Documentation
📖 Release Lifecycle
📖 The release-plan.yaml File

@camara-release-automation camara-release-automation bot requested a review from a team as a code owner March 9, 2026 11:39
@camara-release-automation camara-release-automation bot added the automated Automated bulk operations from project-administration label Mar 9, 2026
@camara-release-automation camara-release-automation bot added the automated Automated bulk operations from project-administration label Mar 9, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 9, 2026

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 3 0 0.01s
✅ API spectral 1 0 1.79s
✅ GHERKIN gherkin-lint 3 0 1.16s
✅ REPOSITORY git_diff yes no 0.02s
✅ REPOSITORY secretlint yes no 0.83s
✅ YAML yamllint 1 0 0.51s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

Copy link
Copy Markdown
Contributor

@YadingFang YadingFang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hdamker hdamker merged commit 44597b9 into main Mar 9, 2026
2 checks passed
@hdamker hdamker deleted the bulk/release-automation-onboarding-22851668827 branch March 9, 2026 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated bulk operations from project-administration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants