chore(deps): update step-security/harden-runner action to v2.18.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
step-security/harden-runner	action	minor	v2.17.0 → v2.18.0

---

Release Notes

step-security/harden-runner (step-security/harden-runner)

v2.18.0

Compare Source

What's Changed

Global Block List: During supply chain incidents like the recent axios and trivy compromises, StepSecurity will add known malicious domains and IP addresses (IOCs) to a global block list. These will be automatically blocked, even in audit mode, providing immediate protection without requiring any workflow changes.

Deploy on Self-Hosted VM: Added deploy-on-self-hosted-vm input that allows the Harden Runner agent to be installed directly on ephemeral self-hosted Linux runner VMs at workflow runtime. This is intended as an alternative when baking the agent into the VM image is not possible.

Full Changelog: step-security/harden-runner@v2.17.0...v2.18.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

Claude finished @renovate[bot]'s task in 28s —— View job

---

Code Review

• Gather context
• Review changed files
• Post findings

This is a straightforward Renovate dependency update for step-security/harden-runner from v2.17.0 to v2.18.0.

Changes

Both .github/actions/claude-code-review/action.yml and .github/workflows/claude.yml are updated identically — pinned SHA updated to match the new tag.

Assessment

LGTM. The update is safe to merge:

• Both files use pinned SHA commits (best practice for security actions), not just version tags — this prevents tag mutation attacks.
• The SHAs are consistent with the official release tag v2.18.0.
• The new version adds a global block list for supply chain incidents (e.g., axios/trivy compromises) and self-hosted VM support — no breaking changes, only additive features.
• egress-policy: audit is unchanged, so no behavioral changes in allowed network traffic.

No issues found.