feat(slack-deploy-notification): include version + diff since last prod release

[pdodgen-revparts]

Summary

Enriches the shared prod-deploy Slack message with two things:

1. Deployed image tag on its own line in the message body (previously only surfaced via the accessory button, easy to miss on a quick scan)
2. View changes since <prev> link that opens a GitHub compare view between the previous prod release and the current one

Rendered example (mrkdwn)

Before:

internal_api deployed by patrickdodgen
View the Deployment
View the Service APM

After:

internal_api deployed by patrickdodgen
Version: `v4.7.6`
View the Deployment
View the Service APM
View changes since v4.7.5

Design

• Scope: prod only. Every consumer already calls this shared workflow with `if: inputs.environment == 'prod'`, so no new input is required. Verified via `gh search code` across encodium/*.
• Previous release detection: `gh release list --exclude-drafts --exclude-pre-releases` → filter out the current tag → sort by `publishedAt` desc → pick top. Matches the RT v2 promotion semantic (`prerelease=false` = shipped to prod).
• Compare URL: `${{ github.server_url }}/${{ github.repository }}/compare/${PREV}...${CURRENT}`
• Edge cases:
  • First-ever prod release: diff line omitted gracefully (no compare against nothing)
  • Same tag redeployed (rollback or manual redeploy): filters self out, uses the next most recent
  • No releases API access: fails the notify step, but the deploy itself already succeeded — cosmetic-only impact

Blast radius

Every consumer of `slack-deploy-notification.yaml` picks up the change on next prod deploy. Callers observed via cross-repo search: 20+ repos including internal_api, radmin, prices-api, laravel-api-template, reporting-app, suppliers-api, payment_api, pub_buyer_api, etc.

Verification

Once merged, the next prod deploy for any consumer will emit an enriched message. The compute step also `echo`s the previous tag + compare URL to the workflow run log for debugging.

Follow-ups

• Jellyfish deploy notification (`jellyfish-deploy-notification.yaml`) untouched — team plans to remove that path entirely per today's conversation.

Related

• DEVEX-1653 (RT v2)

[cursor]

PR Summary

Low Risk
CI notification-only change; deploys are unaffected if release lookup fails, aside from a failed notify step.

Overview
Prod deploy Slack notifications from the shared slack-deploy-notification workflow now show the deployed image_tag on its own line in the message body, not only on the accessory button.

A new step resolves the prior production release via gh release list (non-draft, non-prerelease, excluding the current tag) and appends a View changes since <prev> link to a GitHub compare URL. If there is no earlier prod release, that line is omitted.

^{Reviewed by Cursor Bugbot for commit c2ec023. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit c2ec023. Configure here.}

[cursor]

Multiline output breaks Slack JSON

High Severity

The diff_line step output is written with a multiline GITHUB_OUTPUT block that includes an extra echo after printf, so the stored value ends with a real newline. That output is pasted raw into the Slack payload JSON text field, which produces invalid JSON and can cause the notification step to fail on prod deploys.

Additional Locations (1)

• .github/workflows/slack-deploy-notification.yaml#L85-L86

 

^{Reviewed by Cursor Bugbot for commit c2ec023. Configure here.}