chore: rename release workflows to use consistent release- prefix

[bhuvan-somisetty]

Description:
Standardize naming of release-related workflows and scripts by applying a consistent release- prefix.

• rename workflow files to use release- prefix
• rename script file to release-coderabbit-gate.js
• update internal references accordingly

Fixes #2134

Notes:

• commit is GPG signed
• DCO sign-off is included
• changes are limited to renaming and references

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 338f174d-d5d8-4577-8437-589848499aee

📥 Commits

Reviewing files that changed from the base of the PR and between e63e151 and 5a720a6.

📒 Files selected for processing (3)

• .github/scripts/release-coderabbit-gate.js
• .github/workflows/release-coderabbit-gate.yml
• .github/workflows/release-publish.yml

---

Walkthrough

Two GitHub Actions workflow files were modified: one now invokes a different local gate script (release-coderabbit-gate.js), and the other pins step-security/harden-runner to v2.18.0 (from v2.17.0).

Changes

Cohort / File(s)	Summary
Release Gate Workflow .github/workflows/release-coderabbit-gate.yml	Replaced inline actions/github-script invocation target to require and run ./.github/scripts/release-coderabbit-gate.js instead of release-pr-coderabbit-gate.js.
Release Publish Workflow .github/workflows/release-publish.yml	Updated step-security/harden-runner action pin from v2.17.0 to v2.18.0 (configuration unchanged).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title clearly summarizes the main change: renaming release workflows to use a consistent 'release-' prefix, which is the primary objective of the changeset.
Description check	✅ Passed	The description directly relates to the changeset, outlining the standardization of naming for release-related workflows and scripts with a 'release-' prefix and reference updates.
Linked Issues check	✅ Passed	The PR addresses all key requirements from issue #2134: updated workflow file references (release-coderabbit-gate.yml, release-publish.yml) and script path changes, with proper internal reference updates.
Out of Scope Changes check	✅ Passed	All changes are directly in-scope: updating the workflow file to reference the renamed script and updating the harden-runner version in the publish workflow, both supporting the renaming objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

📋 Issue Planner

Built with CodeRabbit's Coding Plans for faster development and fewer bugs.

View plan used: #2134

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[bhuvan-somisetty]

Hi @manishdait and @explorerII,

I have addressed all the review comments:

• corrected the script filename and updated the path
• ensured the commit is GPG signed and DCO compliant
• fixed the author details
• recreated the PR with a clean commit history
• resolved merge conflicts and updated the branch with latest main

Please review when possible. Thanks!

[exploreriii]

Hi @bhuvan-somisetty rebase please

[bhuvan-somisetty]

Rebased with latest main and resolved conflicts. Please review again. Thanks!

[exploreriii]

Sincere apologies I clicked rebase and not merge latest changes whcuh has messed up your signing
You’ll need to create a new PR !!!