feat(ci): enhance SDK release workflow #35742
Open
KevinDavilaDotCMS wants to merge 1 commit into
Open
Conversation
… idempotent branch handling - Added Slack notifications for SDK publish failures to alert on unsuccessful attempts. - Implemented idempotent handling for release branches, resetting to main if the branch already exists. - Improved post-release PR creation logic to reuse existing PRs if they were created in previous runs. - Updated Slack notifications for successful SDK releases to include links to the post-release PR for quick review. These changes improve the reliability and transparency of the SDK release process.
Contributor
|
Claude finished @KevinDavilaDotCMS's task in 48s —— View job Rollback Safety Analysis
Result: ✅ Safe to Rollback This PR modifies only two GitHub Actions workflow files:
The changes are CI/CD-only — Slack failure notifications, idempotent branch handling for Label |
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
1 participant
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.
the channel only received success messages.
a previous failed run. Re-triggering the workflow would always fail at that step. Both branches are now handled idempotently: if the branch exists on the remote it is reset to
origin/main and force-pushed; if the post-release PR already exists it is reused instead of re-created.
moved to fire after the PR is created so the link is available.
These changes improve the reliability and transparency of the SDK release process.
Examples of the new messages:
Deploy fail — @next (trunk, cicd_comp_deployment-phase.yml)
🔴 SDK publish FAILED on trunk!
The automated SDK
@nextpublish failed. The packages were not updated on the NPM registry.Commit:
Deploy success — @latest (manual, cicd_manual-release-sdks.yml)
🟢 Attention dotters: SDK libs (Angular, Client, Experiments and React) officially released!
This automated script is happy to announce that a new SDK libs version tagged as:
[
1.3.0 (latest) and 1.3.0-next.12345 (next)] is now available on the NPM registry 📦!Release type:
patch| Triggered by:kevin.davila📝 Please review and merge the post-release PR ASAP:
Deploy success — @next (trunk, cicd_comp_deployment-phase.yml)
🟠 Attention dotters: SDK libs (Angular, Client, Experiments and React) published!
This automated script is happy to announce that a new SDK libs version tagged as:
[
1.3.0-next.12345 (next)] is now available on the NPM registry 📦!Introduced by: <link to PR #456>
Deploy fail — @latest (manual, cicd_manual-release-sdks.yml)
🔴 SDK Release FAILED!
The SDK release workflow failed while trying to publish version
1.3.0.Release type:
patch| Triggered by:kevin.davilaThis PR fixes: #35670