fix verify-hardcoded-version issues

[jameslamb]

Fixes this pre-commit error that's blocking CI:

verify-hardcoded-version.................................................Failed
- hook id: verify-hardcoded-version
- exit code: 1

In file RAPIDS_BRANCH:1:9:
 release/26.04
warning: do not hard-code version, read from VERSION file instead

In file RAPIDS_BRANCH:1:9:
 release/26.04

See rapidsai/pre-commit-hooks#121 for more details.

[jameslamb]

RAPIDS_BRANCH is the relevant one here, but I just copied the entire default config from https://github.com/rapidsai/pre-commit-hooks/blob/21c6bc63c83501a320b7aa8cbb3ca17adb61df2a/.pre-commit-hooks.yaml#L43

Not sure why that didn't just get pulled in directly (exclude: was not overridden here), but this should work just fine.

[KyleFromNVIDIA]

IIRC, I changed the upstream exclude: after release and just haven't released it yet (or this repo isn't using that release yet)

[jameslamb]

ahhh ok, that'd explain it. Well let's keep this change for now, but we should do a release too.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d3d3aea5-9358-4993-8ad2-47c72c79e6f2

📥 Commits

Reviewing files that changed from the base of the PR and between 35fc9e3 and 6b0442a.

📒 Files selected for processing (1)

• .pre-commit-config.yaml

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated pre-commit configuration to exclude additional file patterns from version verification checks, reducing false positives during development.

Walkthrough

The .pre-commit-config.yaml file was updated to add an exclude configuration block to the verify-hardcoded-version pre-commit hook, specifying multiple paths and file patterns to be skipped during verification runs.

Changes

Cohort / File(s)	Summary
Pre-commit Configuration .pre-commit-config.yaml	Added exclude block to verify-hardcoded-version hook with multiple path and file-pattern exclusions to skip hardcoded-version verification for specified files and patterns.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: fixing verify-hardcoded-version issues by adding exclusions to the pre-commit configuration.
Description check	✅ Passed	The description is directly related to the changeset, explaining the specific pre-commit hook failure and referencing the relevant issue for context about the fix.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

📝 Coding Plan

• Generate coding plan for human review comments

---

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

Tip

CodeRabbit can generate a title for your PR based on the changes.

Add @coderabbitai placeholder anywhere in the title of your PR and CodeRabbit will replace it with a title based on the changes in the PR. You can change the placeholder by changing the reviews.auto_title_placeholder setting.

[KyleFromNVIDIA]

IIRC, I changed the upstream exclude: after release and just haven't released it yet (or this repo isn't using that release yet)

[jcrist]

/merge