ci: post release summaries to Slack#28
Merged
Merged
Conversation
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.
Adds a
notifyjob to the release workflow that posts the changelog to Slack whenever a version ships.Design notes:
needs: [release-please, publish], i.e. only after the PyPI publish succeeds — the channel never sees a release that failed to ship.on: releaseworkflow, which would never fire: release-please creates the GitHub Release withGITHUB_TOKEN, and events from that token don't trigger other workflows (GitHub's recursion guard).gh release viewand converts release-please's markdown to Slack mrkdwn (headings/bold/links), truncated at 3500 chars.SLACK_WEBHOOK_RELEASESrepo secret exists, so merging is safe before the secret is set.Setup required after merge: add the incoming-webhook URL as repo secret
SLACK_WEBHOOK_RELEASES.