Repository navigation
ci: announce PyPI releases in Slack - #12
Merged
Merged
Conversation
After publish.yml uploads a tagged release to PyPI, post the tag, its GitHub Release and its PyPI page to the release channel webhook. The step is non-blocking: a failed or unconfigured post never fails the release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
artiom
approved these changes
Nov 16, 2026
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.
Summary
Releases go to PyPI without telling anyone. This adds a final step to the
publishjob inpublish.yml. After the upload succeeds, it posts the tag, a link to its GitHub Release and a link to its PyPI page to the team's release channel webhook (theSLACK_RELEASES_WEBHOOKrepository secret). Other Browserless packages already post releases the same way.continue-on-error: true, so a failed post never marks a release as failed.jqand every value comes from environment variables, so nothing from a ref name is pasted into the script.curlretries 3 times, with a 30-second limit for each attempt.The manual TestPyPI dry run (
workflow_dispatch) does not post.Related issues
None.
Type of change
Checklist
ruff format --check .(no Python changes)ruff check .(no Python changes)mypy(no Python changes)pytest -m "not e2e"(no Python changes)python scripts/codegen.pyleaves no difftype: summary)Notes for reviewers
How this was checked:
--offline) reports no findings. Both are the versions and checksums CI uses.TAG=v0.3.0. It sent oneapplication/jsonPOST with this text::package: *<https://github.com/browserless/bap-py/releases/tag/v0.3.0|v0.3.0>* of browserless-bap published to <https://pypi.org/project/browserless-bap/0.3.0/|PyPI>.The exit code was 0.This is a
ci:change, so it does not trigger a release. The first real post will come from the next release.🤖 Generated with Claude Code
Summary by CodeRabbit