Upgrade vulnerable go mod

[yuvco]

Summary by CodeRabbit

• Chores
  • Updated various dependencies to newer versions for improved stability and compatibility.
  • Upgraded the Go version used by the project.
  • Removed outdated and unused dependencies.

[coderabbitai]

Walkthrough

The go.mod file was updated to bump versions of core, utility, Kubernetes, Helm, OpenTelemetry, and various indirect dependencies. Some obsolete indirect dependencies were removed. The Go version was set to 1.24.0 with toolchain go1.24.4. No code or API changes.

Changes

Cohort / File(s)	Change Summary
Dependency Upgrades go.mod	Upgraded core, Kubernetes, Helm, OpenTelemetry, and utility dependencies to newer versions.
Indirect Dependency Cleanup go.mod	Removed several obsolete indirect dependencies from the list.
Go Version Update go.mod	Set Go version to 1.24.0 and toolchain to go1.24.4.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 370e686 and 439d73c.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (1)

• go.mod (4 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• go.mod

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: goreleaser
• GitHub Check: Analyze (go)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch yuval/dependabot-security-updates

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

🔭 Outside diff range comments (1)

go.mod (1)

3-5: Go 1.24 + toolchain 1.24.4 don’t exist (yet)
Using a non-existent Go version will break every CI/CD and editor integration. Kubernetes v0.33.x is still built/tested with Go 1.22.
Fix: stick to go 1.22 (or 1.23 if you’ve proven it compiles) and drop the toolchain line unless you really need it.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf2a929 and 9697af8.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (1)

• go.mod (6 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: goreleaser
• GitHub Check: Analyze (go)

🔇 Additional comments (2)

go.mod (2)

52-75: Many “2024-2025” pseudo-versions → check provenance
Several indirects point to commits dated in the future (2025…). That usually means a private fork or a tampered tag. Verify the SHAs and source before shipping.

---

160-166: OpenTelemetry 1.37 bump: confirm exporter compatibility
1.37 introduced the new Metrics SDK; some exporters break if not updated in lock-step. Ensure your otel exporter modules are ≥ 1.37 or builds will fail at runtime.