chore: 🔧 Update PR review workflow for title case insensitivity

[evaline-ju]

Summary

Update workflow version to include rossoctl/.github#86

Related issue(s)

Fixes rossoctl/.github#87

Summary by CodeRabbit

• Chores
  • Updated an automated pull request verification workflow reference to a newer approved revision to keep the check process current and reliable.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c9657832-f589-492c-8932-b98eeda4b5a4

📥 Commits

Reviewing files that changed from the base of the PR and between 929eba0 and c0ccc25.

📒 Files selected for processing (1)

• .github/workflows/pr-verifier.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/pr-verifier.yml

---

📝 Walkthrough

Walkthrough

The verify-pr-title job in .github/workflows/pr-verifier.yml now points to a newer pinned commit SHA for the reusable pr-verifier-required.yml workflow, with an inline main and date comment added on the same line.

Changes

PR Verifier SHA Update

Layer / File(s)	Summary
Pinned SHA update for pr-verifier-required.yml .github/workflows/pr-verifier.yml	Updates the reusable workflow reference to a new pinned commit SHA and adds an inline main, 2026-06-25 comment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A tiny SHA hopped into place,
With lowercase titles now in grace.
The verifier hums, quick and light,
Under the moon, all feels just right.
🐇✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise and accurately reflects the workflow update and title-case-insensitivity focus.
Linked Issues check	✅ Passed	The pinned workflow update is described as bringing in PR #86's lowercase-title handling, matching issue #87.
Out of Scope Changes check	✅ Passed	The only change is a workflow pin/comment update directly tied to the PR verifier fix.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

[esnible]

Approved.

Is it usual to pin to particular SHAs without a comment? When future users see this line they will have to trace it back through to this PR to get the rationale.

[evaline-ju]

@esnible

Is it usual to pin to particular SHAs without a comment? When future users see this line they will have to trace it back through to this PR to get the rationale.

It seems generally the workflows that point to a released dependency do tend to have comments, but https://github.com/kagenti/.github doesn't have releases to point to, so I think it hasn't been usual for any of those referenced workflows. Here I've just updated with the main reference and a date so we have some idea of staleness of the pin here.