Skip to content

ci: announce release outcome to DingTalk - #25

Merged
Fiona2016 merged 2 commits into
publishfrom
feat/notify-second-dingtalk-group
Aug 24, 2026
Merged

ci: announce release outcome to DingTalk#25
Fiona2016 merged 2 commits into
publishfrom
feat/notify-second-dingtalk-group

Conversation

@Fiona2016

@Fiona2016 Fiona2016 commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

These release workflows had no DingTalk notification at all, so a successful or failed release went unannounced. This adds the same notification steps the other SDK repositories already use.

  • Success is announced to two DingTalk robots: the original one (DING_TALK_TOKEN / DING_TALK_SECRET) and a second one (DING_TALK_TOKEN_2 / DING_TALK_SECRET_2).
  • Failure is announced to the original robot only.

All four secrets are configured on this repository.

Add success and failure notification steps to the publish job, matching the other SDK repositories. Success is sent to both the original and the second DingTalk robot; failure is sent to the original robot only.
@Fiona2016
Fiona2016 marked this pull request as ready for review August 24, 2026 03:28
These notification steps run inside the publish job, so an outage on the notification endpoint would mark an otherwise successful release as failed. Mark them continue-on-error.
@Fiona2016
Fiona2016 merged commit 9f2ea32 into publish Aug 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant