chore(deps): update dependency go to v1.27.0 - #958
Conversation
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
![buildsworth-bk-app[bot]](https://avatars.githubusercontent.com/in/3010600?s=60&v=4){kind=small}
There was a problem hiding this comment.
There is one blocking compatibility issue in the pinned development toolchain; details are inline.
Want to dig deeper?
Paste this into your agent to explore the findings from this review's Buildkite build:
Download the buildsworth logs from build 19849, then answer my questions about the findings.
Install the reading-buildsworth-logs skill to run this.
About buildsworth
Model: gpt-5.6-sol with xhigh thinking.
How to request a review: Comment @buildsworth-bk review on the PR, or request buildsworth-bk as a reviewer.
Risk labels (how buildsworth classifies risk) — buildsworth classifies risk itself from the diff. Unless repository policy already allows L2 approval, grant it by mentioning @buildsworth-bk (see approval ceiling and L2 approval grant):
- L1 — Low risk (dep bumps, docs/copy, lockfiles, small presentational fixes). buildsworth may approve by default.
- L2 — Standard risk (new UI, additive API fields, refactors). Approved only when repository policy or a verified grant allows it; otherwise comment-only.
- L3 — High risk (auth, migrations, payments, secrets, perf-critical paths). Human review always required.
|
|
||
| [tools] | ||
| go = "1.26.6" | ||
| go = "1.27.0" |
There was a problem hiding this comment.
Blocking: Go 1.27 is newer than the pinned source-analysis binaries, so CI cannot complete. In build #3436, golangci-lint 2.12.2 (built with Go 1.26.2) cannot type-check the new generic method in math/rand/v2, and govulncheck 1.3.0 reports the same Go-version mismatch; the dependent build/release step is then skipped. Please update these pins to Go 1.27-compatible builds (for example, golangci-lint 2.13.1 and govulncheck 1.7.0 both pass locally under Go 1.27), or defer this bump.
There was a problem hiding this comment.
Still open — golangci-lint now passes, but govulncheck remains at 1.3.0 and build #3439 fails its vulncheck job with the Go 1.26/1.27 source-processing mismatch.
There was a problem hiding this comment.
Still open — build #3451 fails the govulncheck step because the pinned 1.3.0 binary was built with Go 1.26 and cannot process Go 1.27 sources.
There was a problem hiding this comment.
Still open — build #3456's govulncheck job fails on the current revision because the pinned 1.3.0 analyzer was built with Go 1.26 and cannot process Go 1.27 sources.
There was a problem hiding this comment.
Still open — build #3463 fails the govulncheck step because the pinned 1.3.0 analyzer was built with Go 1.26 and cannot process Go 1.27 sources.
7677b8f to
e01c28e
Compare
There was a problem hiding this comment.
The previous toolchain-compatibility concern is partly addressed after the rebase, but one blocking piece remains open; details are in the existing thread.
Want to dig deeper?
Paste this into your agent to explore the findings from this review's Buildkite build:
Download the buildsworth logs from build 20156, then answer my questions about the findings.
Install the reading-buildsworth-logs skill to run this.
e01c28e to
2aaf544
Compare
There was a problem hiding this comment.
The existing govulncheck compatibility blocker is still open and current CI fails at the same step; I added the updated build evidence to the existing thread.
Want to dig deeper?
Paste this into your agent to explore the findings from this review's Buildkite build:
Download the buildsworth logs from build 20783, then answer my questions about the findings.
Install the reading-buildsworth-logs skill to run this.
2aaf544 to
54568d2
Compare
There was a problem hiding this comment.
The existing govulncheck compatibility blocker remains open on the current revision; build #3456 fails at the same mandatory check. Details are in the existing thread.
Want to dig deeper?
Paste this into your agent to explore the findings from this review's Buildkite build:
Download the buildsworth logs from build 21512, then answer my questions about the findings.
Install the reading-buildsworth-logs skill to run this.
54568d2 to
122421b
Compare
There was a problem hiding this comment.
The existing govulncheck compatibility blocker remains open after the rebase; current build #3463 fails the same mandatory check. Details are in the existing thread.
Want to dig deeper?
Paste this into your agent to explore the findings from this review's Buildkite build:
Download the buildsworth logs from build 22744, then answer my questions about the findings.
Install the reading-buildsworth-logs skill to run this.
This PR contains the following updates:
1.26.6→1.27.0Release Notes
golang/go (go)
v1.27.0Compare Source
v1.26.7Compare Source
Configuration
📅 Schedule: (UTC)
* * * * 1-5)🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.