chore(deps): update dependency go to v1.26.0#411
chore(deps): update dependency go to v1.26.0#411renovate-sh-app[bot] wants to merge 1 commit intomainfrom
Conversation
4a0c666 to
4db8a0b
Compare
86626ec to
ccffed0
Compare
425efd1 to
4a8ee7a
Compare
4a8ee7a to
4101e7f
Compare
9e8914a to
c9a4c48
Compare
9993201 to
454687a
Compare
d46708f to
6a17385
Compare
6a17385 to
8260010
Compare
go.mod
Outdated
| go 1.24.0 | ||
|
|
||
| toolchain go1.24.4 | ||
| toolchain go1.25.5 |
There was a problem hiding this comment.
Go workspace version mismatch with module toolchain
The go.mod toolchain is being updated from go1.24.4 to go1.25.5, but go.work still declares go 1.24.4. Previously these were in sync. This version mismatch between the workspace file and module toolchain could cause inconsistent Go toolchain selection depending on whether builds run in workspace mode or not, potentially leading to different behavior or compatibility issues across build environments.
8260010 to
f89fe35
Compare
765ff83 to
d6efc28
Compare
185ae59 to
166a04b
Compare
384c594 to
11a9dc7
Compare
192e91b to
62802b6
Compare
b22f130 to
1547fef
Compare
7797eb5 to
a6e94ce
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: go.work not updated alongside go.mod toolchain bump
- Added
toolchain go1.26.0togo.workso workspace toolchain selection is aligned with the updatedgo.modtoolchain.
- Added
Or push these changes by commenting:
@cursor push eac068383c
Preview (eac068383c)
diff --git a/go.work b/go.work
--- a/go.work
+++ b/go.work
@@ -1,5 +1,7 @@
go 1.24.4
+toolchain go1.26.0
+
use (
.
./testing/alerting-gen| go 1.24.0 | ||
|
|
||
| toolchain go1.24.4 | ||
| toolchain go1.26.0 |
There was a problem hiding this comment.
go.work not updated alongside go.mod toolchain bump
Low Severity
The toolchain directive in go.mod was bumped from go1.24.4 to go1.26.0, but the go.work file still specifies go 1.24.4 (which matched the old toolchain version) and has no toolchain directive. This inconsistency means the workspace configuration is out of sync with the module's toolchain requirement. While Go's automatic toolchain switching (GOTOOLCHAIN=auto) will likely resolve this at build time, developers using GOTOOLCHAIN=local or inspecting workspace settings will encounter a mismatch.
| datasource | package | from | to | | -------------- | ------- | ------ | ------ | | golang-version | go | 1.24.4 | 1.26.0 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
a6e94ce to
0c97988
Compare



This PR contains the following updates:
1.24.4→1.26.0Release Notes
golang/go (go)
v1.26.0v1.25.7v1.25.6v1.25.5v1.25.4v1.25.3v1.25.2v1.25.1v1.25.0v1.24.13v1.24.12v1.24.11v1.24.10v1.24.9v1.24.8v1.24.7v1.24.6v1.24.5Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.
Note
Medium Risk
Toolchain upgrades can introduce compiler/runtime behavior changes that may break builds or tests even without code changes.
Overview
Bumps the
go.modtoolchaindirective fromgo1.24.4togo1.26.0, so local builds/CI that honor toolchain selection will compile and test with Go 1.26 by default.Written by Cursor Bugbot for commit 0c97988. This will update automatically on new commits. Configure here.