chore(ci): correct actions/cache pin comment to actual version v5.0.5

[rusackas]

SUMMARY

The actions/cache action is pinned by SHA 27d5ce7f107fe9357f9df03efb73ab90386fccae in three workflow steps, but the trailing comment reads # v5. That SHA actually corresponds to tag v5.0.5; the floating v5 tag points to a different commit (caa2961...). The comment therefore misrepresents the pinned version.

This updates the comment to the truthful version (# v5.0.5) so it matches the pinned commit. No SHA change, so runtime behavior is identical.

Affected files:

• .github/workflows/release.yml (2 steps)
• .github/workflows/pre-commit.yml (1 step)

Resolves code-scanning alert #2553 (zizmor ref-version-mismatch).

BEFORE/AFTER

Before: uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5
After: uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5

TESTING INSTRUCTIONS

pre-commit run --files .github/workflows/release.yml .github/workflows/pre-commit.yml — zizmor passes.

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

🤖 Generated with Claude Code

[bito-code-review]

Bito Automatic Review Skipped - Files Excluded

Bito didn't auto-review this change because all changed files are in the exclusion list for automatic reviews. No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.
You can change the excluded files settings here, or contact your Bito workspace admin at evan@preset.io.