-
Notifications
You must be signed in to change notification settings - Fork 480
feat(cicd): Add Slack message on Manual SDK Release #35461
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
KevinDavilaDotCMS
wants to merge
3
commits into
main
Choose a base branch
from
feat/sdk-slack-notification-on-manual-release
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+33
−1
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
33ac630
feat(cicd): add Slack notification to manual SDK release workflow and…
KevinDavilaDotCMS 648d680
fix(cicd): address Claude bot review suggestions on SDK Slack notific…
KevinDavilaDotCMS 0f2e1cf
fix(cicd): add continue-on-error to SDK Slack step in manual release …
KevinDavilaDotCMS File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @KevinDavilaDotCMS — nice addition, having the originating PR in the SDK announcement will be really useful. I think there's one edge case worth addressing here before merge.
GitHub Actions runs
run:steps withbash --noprofile --norc -eo pipefail {0}by default. On this line:PR_NUMBER=$(echo "$COMMIT_MSG" | grep -oP '#\K[0-9]+' | head -1)if
grepfinds no matches, it exits with status1. Withpipefailenabled, that non-zero status propagates through the pipeline and the whole step fails before reaching theif [ -n "$PR_NUMBER" ]check, so the SHA fallback in theelsebranch never gets a chance to run.This matters in two scenarios:
pushwhose head commit message simply has no#NNNreference.github.event.head_commit.messageis empty — e.g., theworkflow_dispatchpaths incicd_4-nightly.ymlandcicd_8-manual-deploy.yml, which also call this reusable workflow withpublish-npm-sdk-libsenabled.Since the next Slack step is gated on
if: success() && steps.sdks_publish.outputs.published == 'true', the practical effect is that no Slack notification is sent at all in those cases — the opposite of what the fallback is meant to do.Minimal fix to let the fallback work as intended:
Thanks for picking this up!