Skip to content

Conversation

@ronneseth
Copy link
Contributor

Summary

Removes the channel field from the Slack webhook payload. Incoming webhooks post to the channel configured in the webhook URL, so the channel field is not needed.

Changes

  • Removed "channel": "#release" from the payload JSON
  • Kept SLACK_WEBHOOK_TYPE: INCOMING_WEBHOOK (correct for webhook URLs)

Technical Details

The webhook URL format (https://hooks.slack.com/services/...) indicates this is an incoming webhook, which posts to the channel configured when the webhook was created. The channel field in the payload is not used by incoming webhooks.

Related

  • DEVEX-693

Testing

  • Verify Slack notification posts to the correct channel (configured in webhook URL) on next production deployment

Remove the channel field from the Slack webhook payload as incoming webhooks post to the channel configured in the webhook URL. The SLACK_WEBHOOK_TYPE: INCOMING_WEBHOOK is correct for webhook URLs.

DEVEX-693
@ronneseth ronneseth requested a review from a team as a code owner January 3, 2026 20:56
@ronneseth ronneseth requested a review from aspencer January 3, 2026 20:56
Andreas Ronneseth added 4 commits January 3, 2026 14:00
Make the APM link conditional - only show it when apm_url is explicitly provided. This fixes issues where workflows that don't provide apm_url were getting broken or inappropriate links.

DEVEX-693
Replace slackapi/slack-github-action with direct curl command to avoid action parsing errors. This matches the working curl example and should resolve the 'channel: command not found' CI errors.

DEVEX-693
Revert all DEVEX-693 changes and restore the workflow to its original state before DEVEX-693 work began. The webhook URL in GitHub secrets should be updated to point to the #release channel instead.

DEVEX-693
Fix potential security issue where JIRA ticket description content could be interpreted as shell commands:

1. Only request 'status' field from JIRA API instead of full ticket (avoids processing description)
2. Use temporary file to safely store curl response instead of direct variable assignment
3. Use printf instead of echo when processing user-controlled content (PR body, commit messages)
4. Use HTTP status codes for error checking instead of parsing JSON error messages
5. Properly quote all variables and use jq with error handling

This prevents ticket descriptions containing shell-like text from being executed as commands.

DEVEX-693
@ronneseth ronneseth merged commit f4c44c2 into main Jan 3, 2026
1 check passed
@ronneseth ronneseth deleted the devex-693-deploy-slack-updates branch January 3, 2026 21:35
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.

2 participants