[zimeg]

Changelog

No user-facing changes.

Summary

This pull request sets errors: true on the Slack release announcement in the notify job, so a rejected post (e.g. a revoked webhook) fails the job instead of only logging.

• notify is already its own job, so a red X there leaves the release green and signals gh run rerun <id> --failed. Nothing else changes.
• Same change as the split notify jobs in bolt-js, node-slack-sdk, slack-github-action and slack-skills-plugin. Motivated by this suggestion on the python release-notify PRs.
• zizmor .github/workflows/release.yml reports the same two findings as main (github-app at line 25, cache-poisoning at line 39), both outside the notify job.

Testing

After merge, the next release run should show notify posting the announcement. A failed post now marks notify red.

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[mwbrooks]

✅ Thanks @zimeg! A red notify job makes a missed CLI release announcement easy to spot and rerun.

[zimeg]

📣 Thanks for the kind review @mwbrooks! A missed announcement will finally show up as a red job to rerun.