[bulk] Enable release automation process (2026-03-12-001)#104
Open
camara-release-automation[bot] wants to merge 1 commit intomainfrom
Open
[bulk] Enable release automation process (2026-03-12-001)#104camara-release-automation[bot] wants to merge 1 commit intomainfrom
camara-release-automation[bot] wants to merge 1 commit intomainfrom
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
tanjadegroot
approved these changes
Mar 18, 2026
Collaborator
tanjadegroot
left a comment
There was a problem hiding this comment.
LGTM from Release Management
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enable release automation for NetworkSliceBooking
TL;DR: This PR adds the release automation workflow and prepares the CHANGELOG structure for NetworkSliceBooking.
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 releaseChanges
.github/workflows/release-automation.yml@ra-v1-rc)CHANGELOG.mdCHANGELOG/README.mdWhat to do next
If
release-plan.yamlwas updated before this workflow was installed, you may need to trigger the workflow manually once to create the initial Release Issue:Release lifecycle overview
release-plan.yamlwith target release tag, type, and API versions/statusesmainbranch with version fields set towip/create-snapshoton the Release Issue to generate a Release PR/publish-release --confirm rX.Yto finalize the releaseIf issues arise: use
/discard-snapshot(during review) or/delete-draft(during draft phase) to return to planned state and make corrections onmain.More details: Release Lifecycle
Documentation
📖 Release Management Documentation
📖 Release Lifecycle
📖 The release-plan.yaml File