[gh-worker-campaigns-3e9aa4]

This repins the slack-notifier image to the current build:

• noble: v146002689-ab6722e-sdm-gbi-noble
• jammy: v146002692-ab6722e-sdm-gbi-jammy

The build this repo pins today falls into one of two groups:

• Built before Feb 20: email2slackid reads the SDS humans table, which
  we're planning to retire in favor of Directory Service. Moving now means author
  pings keep working whenever that happens.
• Built Feb 20 to Oct 20: email2slackid uses Directory Service but exits
  non-zero, with no output, for an email that has no identity (bot accounts,
  the Conductor user, external co-authors). On 2026-10-19 this failed most dd-go
  staging releases. ddoghq/images#12169 makes it return an empty Slack ID
  instead, as the old version did.

What else changes. Where CI pinned the image in a variable or a job's
image:, the pin now lives in .gitlab/slack-notifier.engraver_versions.yaml,
which your CI includes, and jobs use $SLACK_NOTIFIER_IMAGE as before. A
Dockerfile that copied binaries straight from a pinned image now does it
through a named slack-notifier stage. Both let us send future slack-notifier
updates as one-line Campaigner PRs instead of hand-made ones.

This PR is labeled auto-merge: once you approve it and CI passes, it merges
on its own. If you'd rather merge it yourself, remove the label.

If this repo bakes slack-notifier into its own CI image (COPY --from), that
image needs a rebuild after merging to pick up the change, and persistent GitLab
runners need their dd-source Helm tag bumped. We're happy to help with either.

Tracking: EENG-7274, EENG-7073. Questions or concerns: #humans-sunset.

[datadog-prod-us1-3]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 45.87% (+0.04%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: a9a0fad | Docs | View more details | Give us feedback!}