update slack message and update step description

[shichengripple001]

High Level Overview of Change

update slack message and update step description

Context of Change

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Tests (You added tests for code that already exists, or your new feature included in this PR)
• Documentation Updates
• Release

Did you update HISTORY.md?

• Yes
• No, this change does not impact library users

Test Plan

[coderabbitai]

Walkthrough

Renamed review job titles and updated Slack/message templates in .github/workflows/release.yml to use dynamic variables (PACKAGE_NAME, PACKAGE_VERSION, RUN_URL, reviewers). Control flow and all functional steps (PR creation, reviewer retrieval, SBOM, notifications, publishing) remain unchanged.

Changes

Cohort / File(s)	Summary of Changes
CI workflow messaging updates \.github/workflows/release.yml	Renamed Dev/Sec review job names; replaced hardcoded package references with PACKAGE_NAME/PACKAGE_VERSION; updated Slack messages to use dynamic environment inputs; no changes to workflow logic or steps beyond messaging/text updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Release pipeline #3039 — Modifies the same release workflow, adjusting job names and Slack templates with PACKAGE_NAME/PACKAGE_VERSION variables.

Suggested reviewers

• mvadari
• khancode
• achowdhry-ripple
• Patel-Raj11
• pdp2121

Poem

hop hop—release bots sing,
names refreshed, alerts take wing.
No gears moved, just clearer chime,
variables rhyme with build-time.
I nibble logs, ears up high—
“PACKAGE_VERSION?”—oh my! 🥕
Ship it, skyward we fly.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description provides only a minimal summary and leaves all template sections blank or incomplete, omitting context of the change, type of change selection, test plan details, HISTORY.md updates, and any future tasks.	Please complete the required template sections by adding background context, marking the appropriate type of change, outlining the test plan, indicating whether HISTORY.md needs updating, and listing any future tasks.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title succinctly and accurately describes the primary change—updating Slack messages and step descriptions—matching the core modifications in the workflow without introducing unrelated details.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 006ef0f and c728062.

📒 Files selected for processing (1)

• .github/workflows/release.yml (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)

• GitHub Check: integration (20.x)
• GitHub Check: integration (22.x)
• GitHub Check: browser (22.x)
• GitHub Check: build-and-lint (22.x)
• GitHub Check: unit (20.x)
• GitHub Check: unit (22.x)
• GitHub Check: semgrep-cloud-platform/scan
• GitHub Check: semgrep-cloud-platform/scan

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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