go: Update Go version to 1.26.1

[RieshBissessur]

This PR updates the Go version in Weld from 1.25.7 to 1.26.1.

This is part of the Go version upgrade process across our backend services. This PR must be merged and released before we can proceed with updating the core repository's dependencies.

Changes:

Updated go.mod to specify Go 1.26.1
Impact:

No breaking changes expected
This will allow core services to use Go 1.26.1 features
Next Steps:

Merge this PR
Wait for Weld release/tag to be available
Update core repository dependencies to reference new Weld version

[coderabbitai]

Walkthrough

The pull request updates the Go version and toolchain metadata in the go.mod file. The Go language version is bumped from 1.25 to 1.26, and the toolchain directive is updated from go1.25.6 to go1.26.1. This is a purely version management change with no modifications to dependencies or semantic content.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• gomod: Update Go version to 1.24.3 #34: Updates Go version in go.mod file, matching the version upgrade pattern in this PR.
• gomod: Update version to Go 1.25.0 #38: Modifies the go.mod Go toolchain version directive to align with project upgrades.
• gomod: Update Go toolchain to 1.25.3 and remove 1.24 compatibility #55: Updates both go.mod Go version/toolchain and CI workflows to maintain consistency across the project.

Suggested labels

AI::Created

Poem

🐰 A leap from one-two-five to one-two-six,
Toolchains updated, the project's all fixed,
Go forth with new versions so bright,
Metadata dancing in morning light! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change: updating the Go version to 1.26.1, which directly corresponds to the go.mod changes.
Description check	✅ Passed	The description is directly related to the changeset, providing context about the Go version upgrade, its purpose, and next steps.
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
• Post copyable unit tests in a comment
• Commit unit tests in branch go-1.26.1-upgrade

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

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

Inline comments:
In `@go.mod`:
- Around line 3-5: The go.mod currently sets "go 1.26" while adding a "toolchain
go1.26.1", which does not propagate the 1.26.1 requirement to downstream
consumers; decide whether 1.26.1 is the actual minimum and, if so, update the
module directive from "go 1.26" to "go 1.26.1" (or alternatively remove/adjust
the "toolchain" directive if you want to keep 1.26.0 compatibility) so the
module requirement and the toolchain are consistent; locate the go.mod file and
change the top-level "go" directive to match the intended minimum Go version.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f3405f3a-ef88-4fa3-8b96-cab4de4a9ab7

📥 Commits

Reviewing files that changed from the base of the PR and between e80b9e6 and 4f4571b.

📒 Files selected for processing (1)

• go.mod

not needed