Skip to content

ci: post release announcement to slack channel#2877

Merged
zimeg merged 2 commits intomainfrom
zimeg-release-notification
Apr 22, 2026
Merged

ci: post release announcement to slack channel#2877
zimeg merged 2 commits intomainfrom
zimeg-release-notification

Conversation

@zimeg
Copy link
Copy Markdown
Member

@zimeg zimeg commented Apr 22, 2026

Summary

This PR posts a release announcement to a Slack channel for more celebrations 🎉

Requirements

@zimeg zimeg added this to the 4.8.0 milestone Apr 22, 2026
@zimeg zimeg self-assigned this Apr 22, 2026
@zimeg zimeg requested a review from a team as a code owner April 22, 2026 17:12
@zimeg zimeg added semver:patch release github_actions Pull requests that update GitHub Actions code labels Apr 22, 2026
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 22, 2026

🦋 Changeset detected

Latest commit: ba3d879

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@slack/bolt Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.59%. Comparing base (c24faff) to head (ba3d879).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2877   +/-   ##
=======================================
  Coverage   93.59%   93.59%           
=======================================
  Files          44       44           
  Lines        7855     7855           
  Branches      687      687           
=======================================
  Hits         7352     7352           
  Misses        498      498           
  Partials        5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Member Author

@zimeg zimeg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 A few notes on these changes in experiment!

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📣 note: This is from earlier PR #2853 before we introduced changesets. I'm adding this now for upcoming releases and testing!

echo "message=$(echo "$PUBLISHED_PACKAGES" | jq -r '.[] | "\(.name)@\(.version)"' | paste -sd ', ' -)" >> "$GITHUB_OUTPUT"
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
PUBLISHED_PACKAGES: ${{ steps.changesets.outputs.publishedPackages }}
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🐢 note: This isn't beautiful parsing but I believe it's stable enough for decent outputs we expect:

  • publishedPackages - A JSON array to present the published packages. The format is [{"name": "@xx/xx", "version": "1.2.0"}, {"name": "@xx/xy", "version": "0.8.9"}]

🔗 https://github.com/changesets/action#outputs

@zimeg
Copy link
Copy Markdown
Member Author

zimeg commented Apr 22, 2026

🗣️ I'll now merge this so we can follow up with findings from actual test soon!

@zimeg zimeg merged commit 54f3577 into main Apr 22, 2026
26 checks passed
@zimeg zimeg deleted the zimeg-release-notification branch April 22, 2026 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

github_actions Pull requests that update GitHub Actions code release semver:patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant