Skip to content

fix: use slack mrkdwn in release notifications - #107

Merged
JMatej merged 1 commit into
masterfrom
claude/slack-release-notifications-x2br7c
Jul 30, 2026
Merged

fix: use slack mrkdwn in release notifications#107
JMatej merged 1 commit into
masterfrom
claude/slack-release-notifications-x2br7c

Conversation

@JMatej

@JMatej JMatej commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Summary

Release notifications were written in standard markdown, which Slack doesn't render — bold showed up as literal **.

  • Bold uses single asterisks.
  • --- in the headline is now an en dash.
  • Each changed file path is backticked, list stays on one line.

@JMatej
JMatej force-pushed the claude/slack-release-notifications-x2br7c branch from e71b1e9 to 6674dca Compare July 29, 2026 11:33
@JMatej JMatej changed the title Refactor Slack notifications to use Block Kit for better formatting fix: use slack mrkdwn in release notifications Jul 29, 2026
Slack bolds with single asterisks, so `**bold**` showed up verbatim in
the release messages. Also swaps `---` for an en dash and backticks each
changed file path.

Changelog formatting is left as it was.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NWZHQdzP5BHDBaietpWtxW
@JMatej
JMatej force-pushed the claude/slack-release-notifications-x2br7c branch from 6674dca to 5fd5089 Compare July 29, 2026 11:35
@JMatej JMatej self-assigned this Jul 29, 2026
@JMatej
JMatej marked this pull request as ready for review July 29, 2026 11:43
@JMatej
JMatej merged commit b5314e4 into master Jul 30, 2026
10 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.

5 participants