fix: upgrade go and dependencies

[raffis]

Current situation

Proposal

Summary by CodeRabbit

• Chores
  • Updated Go version to 1.24.x across all workflows.
  • Upgraded direct and indirect dependencies to newer versions, including Kubernetes modules and utility libraries.
  • Removed some outdated indirect dependencies for improved compatibility.
  • Updated golangci-lint tool to version 2.1.2 for enhanced linting support.

[coderabbitai]

Warning

Rate limit exceeded

@raffis has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 2 minutes and 0 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 955d934 and 3dc502f.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (7)

• .github/workflows/main.yaml (1 hunks)
• .github/workflows/pr-build.yaml (3 hunks)
• .github/workflows/release.yaml (1 hunks)
• Makefile (1 hunks)
• go.mod (2 hunks)
• internal/controllers/ingress_controller.go (3 hunks)
• internal/proxy/oauth2.go (1 hunks)

Walkthrough

This update focuses on upgrading the Go version used throughout the project from 1.22.x to 1.24.x. The Go version is updated in all GitHub Actions workflow files, including those for the main branch, pull request builds, and releases. Additionally, the go.mod file is updated to specify Go 1.24.2 and to upgrade various direct and indirect dependencies to their latest compatible versions. The Makefile is also updated to install a newer version of golangci-lint. No changes are made to code logic, workflow steps, or public API declarations.

Changes

File(s)	Change Summary
.github/workflows/main.yaml	Updated Go version in GitHub Actions from 1.22.x to 1.24.x.
.github/workflows/pr-build.yaml	Updated Go version in all jobs from 1.22.x to 1.24.x.
.github/workflows/release.yaml	Updated Go version in release workflow from 1.22.x to 1.24.x.
go.mod	Updated Go version to 1.24.2; upgraded multiple direct and indirect dependencies; removed some indirect dependencies.
Makefile	Updated golangci-lint tool version from v1.52.2 to v2.1.2.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant Go Toolchain

    Developer->>GitHub Actions: Push or PR triggers workflow
    GitHub Actions->>Go Toolchain: Setup Go 1.24.x environment
    GitHub Actions->>GitHub Actions: Run build, test, release jobs using Go 1.24.x
    GitHub Actions-->>Developer: Report job results

Loading

Possibly related issues

• DoodleScheduling/gitrepository-fetch#12: Updates Go version and dependencies in workflows and go.mod, matching the changes in this PR.
• DoodleScheduling/k8skeycloak-cluster-controller#60: Tracks Go and dependency upgrades similar to those performed in this PR.

Suggested labels

size/XS

Suggested reviewers

• petardoodle

Poem

Hopping along with a brand new Go,
Dependencies fresh, our builds will flow!
Workflows updated, the future is bright,
With 1.24, we leap to new height.
The burrow is tidy, the carrots in line,
This rabbit approves—everything’s fine! 🥕

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.