chore: update Go toolchain to 1.25 and bump golang.org/x/oauth2 package

[im-adithya]

Summary by CodeRabbit

Chores

• Updated Go build environment to a newer version
• Upgraded OAuth2 dependency for improved security and compatibility

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates two version specifications: the Go compiler base image in the Dockerfile from version 1.24 to 1.25, and the golang.org/x/oauth2 dependency in go.mod from v0.34.0 to v0.36.0.

Changes

Cohort / File(s)	Summary
Go Version Update Dockerfile	Updated the builder stage base image from golang:1.24 to golang:1.25.
Dependency Upgrade go.mod	Upgraded golang.org/x/oauth2 direct dependency from v0.34.0 to v0.36.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Version bumps, oh what a delight,
Go 1.25 shines ever so bright,
OAuth2 updated, secure and sound,
Dependencies fresh, improvements found! 🌟

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: updating the Go toolchain from 1.24 to 1.25 in the Dockerfile and bumping the golang.org/x/oauth2 package version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-go-1.25

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

Dockerfile (1)

12-12: Pin the Go builder image to a specific version for reproducibility.

golang:1.25 is a moving tag; builds can drift over time. Pinning to a patch version (e.g., golang:1.25.8) improves reproducibility and reduces surprise breakage in CI. For even stronger supply chain security, pin to a digest.

Proposed hardening

-FROM golang:1.25 AS builder
+FROM golang:1.25.8 AS builder

For maximum reproducibility and supply chain security, also consider pinning to the image digest instead.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@Dockerfile` at line 12, The Dockerfile's builder image uses the moving tag
"golang:1.25"; update the FROM instruction (the builder stage) to pin to a
specific patch release (e.g., "golang:1.25.8") or, better, to an image digest
for stronger reproducibility and supply-chain security so the build won't drift
over time.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@Dockerfile`:
- Line 12: The Dockerfile's builder image uses the moving tag "golang:1.25";
update the FROM instruction (the builder stage) to pin to a specific patch
release (e.g., "golang:1.25.8") or, better, to an image digest for stronger
reproducibility and supply-chain security so the build won't drift over time.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: de7f15ef-65d0-4257-87ec-6a43f36bd89b

📥 Commits

Reviewing files that changed from the base of the PR and between 2ea06d3 and 8cb0402.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• Dockerfile
• go.mod