fix(ci): fix configuration for breaking change notification workflow

[jameslamb]

Contributes to rapidsai/shared-workflows#560

Fixes misconfigurations in the GitHub Actions workflow that generates Notifications when PRs are labeled breaking.

Any other changes come from making the configuration for this workflow identical across all RAPIDS repos.

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[jameslamb]

/ok to test

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: ea11189d-f599-4e68-8688-d5dbc06bbc9b

📥 Commits

Reviewing files that changed from the base of the PR and between ffbe51a and f8d482b.

📒 Files selected for processing (1)

• .github/workflows/trigger-breaking-change-alert.yaml

---

📝 Walkthrough

Walkthrough

The pull request updates the breaking change alert workflow by refreshing the copyright header year range to 2025–2026 and modifying the trigger-notifier job to explicitly declare read-only permissions and reference a new Slack webhook secret environment variable.

Changes

Workflow Configuration

Layer / File(s)	Summary
Trigger notifier job permissions and secret wiring .github/workflows/trigger-breaking-change-alert.yaml	Copyright header year updated. Shared workflow call now explicitly grants contents: read permissions and uses NV_SLACK_BREAKING_CHANGE_NOTIFIER_APP secret mapped to the slack-webhook-url input.

---

🎯 2 (Simple) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: fixing the breaking change notification workflow configuration in the CI pipeline.
Description check	✅ Passed	The description is directly related to the changeset, explaining the issue being fixed and the scope of changes (workflow configuration alignment).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jakirkham]

Thanks James! 🙏

[jakirkham]

Guessing this is just because this is when the repo was published

[jameslamb]

Yes I think that's right. This was done automatically by pre-commit.

Because all of the history was squashed when the project was open-sourced: b833f7a

[jakirkham]

/merge