build(deps): bump golang.org/x/crypto from 0.51.0 to 0.52.0

[mwbrooks]

Changelog

• N/A

Summary

This pull request bumps the indirect golang.org/x/crypto dependency from v0.51.0 to v0.52.0 to clear 13 Snyk-reported vulnerabilities (5 High, 8 Medium) pulled in transitively through github.com/go-git/go-git/v5.

Preview

N/A — indirect dependency bump, no user-facing changes.

Testing

• Run snyk test and confirm Tested 352 dependencies for known issues, no vulnerable paths found. (was 13 issues / 40 vulnerable paths before the bump)
• Run make build and confirm the binary builds cleanly
• Run make test and confirm the suite passes

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.65%. Comparing base (f0d20ad) to head (a0e7862).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #602      +/-   ##
==========================================
+ Coverage   71.64%   71.65%   +0.01%     
==========================================
  Files         226      226              
  Lines       19176    19176              
==========================================
+ Hits        13739    13741       +2     
  Misses       4222     4222              
+ Partials     1215     1213       -2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[zimeg]

@mwbrooks Amazing find thanks for keeping us on the latest 🔏

I note a changelog section exists in the PR title but not labels and was wondering if this is something we want to surface next release notes?

[mwbrooks]

@zimeg Thanks for the quick review!

Good call. I removed the changelog entry and didn't add a label. I don't think we need it surfaced in the public changelog.