chore(deps): Upgrade golang to 1.26.7 (v0.8 branch) - #3545
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> (cherry picked from commit 7d3992d27ba67f5e46a02cab4c86aca05bd8901b in release-v0.7 branch PR)
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
PR Summary by QodoUpgrade Go toolchain to 1.26.7 on v0.8
AI Description
High-Level Assessment
Files changed (7)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can commit Qodo's fix in one click with committable suggestions (GitHub & GitLab) |
Pin all remaining unpinned actions per stricter GitHub policies: - conforma/github-workflows auto-merge and golang-version-check pinned to e049ae95 (main) - jlumbroso/free-disk-space pinned to 54081f13 (v1.3.1) - conforma/pr-size-label-action pinned to 8b1fcdb8 (v1.0.0) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
It's a long story, but the policy repo release branches are not meant to be "real" branches. They're more like tags, and they were created to provide a stable compatible reference for RHTAP. Recently some renovate PRs were merged in the release-v0.8 branch, so the git sha has moved, causing the snapshot data to no longer match. As a workaround to get my PR green, I'm using a git sha in the policy.yaml (rather than changing the snapshot data to the new git ref).
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
No description provided.