deps: bump golang.org/x/term from 0.40.0 to 0.41.0 in /src

[dependabot]

Bumps golang.org/x/term from 0.40.0 to 0.41.0.

Commits

• 9d2dc07 go.mod: update golang.org/x dependencies
• d954e03 all: upgrade go directive to at least 1.25.0 [generated]
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies, go. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[greptile-apps]

Greptile Summary

This is a Dependabot-generated dependency bump of golang.org/x/term from v0.40.0 to v0.41.0, which also pulls in golang.org/x/sys v0.42.0 as an updated indirect dependency. The bump is straightforward, but it carries a significant side effect: the upstream golang.org/x/term v0.41.0 module now declares go 1.25.0 in its own go.mod, which has caused Go's toolchain to propagate that requirement into this project's go.mod directive — raising it from 1.24.2 to 1.25.0.

Key changes and concerns:

• golang.org/x/term bumped from v0.40.0 → v0.41.0 (direct dependency)
• golang.org/x/sys bumped from v0.41.0 → v0.42.0 (indirect dependency)
• go directive in src/go.mod raised from 1.24.2 → 1.25.0 — all three CI workflows (.github/workflows/ci.yml, rc.yml, and release.yml) pin go-version: '1.24', which is below the new minimum and will cause build failures once this PR is merged
• src/go.sum checksums updated correctly to match the new dependency versions

Confidence Score: 1/5

• Not safe to merge — the Go version directive bump to 1.25.0 will break all CI pipelines currently pinned to Go 1.24.
• The dependency bump itself is benign, but the cascading Go toolchain version requirement bump from 1.24.2 to 1.25.0 is a blocking issue. All three GitHub Actions workflows (ci.yml, rc.yml, release.yml) specify go-version: '1.24', which is incompatible with the new go 1.25.0 directive. Every CI job — tests, RC builds across 6 platform targets, and the release pipeline — will fail until those workflows are updated.
• .github/workflows/ci.yml, .github/workflows/rc.yml, and .github/workflows/release.yml all need their go-version updated to '1.25' to align with the new go 1.25.0 directive in src/go.mod.

Important Files Changed

Filename	Overview
src/go.mod	Bumps golang.org/x/term to v0.41.0 and golang.org/x/sys to v0.42.0 (indirect), but also upgrades the go directive from 1.24.2 to 1.25.0 — which is incompatible with the go-version: '1.24' used across all three CI workflows.
src/go.sum	Hash entries updated to reflect the new versions of golang.org/x/term (v0.41.0) and golang.org/x/sys (v0.42.0). No issues; the checksums are the expected output of the dependency bump.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["dependabot bump\ngolang.org/x/term\nv0.40.0 → v0.41.0"] --> B["x/term v0.41.0 go.mod\nrequires go 1.25.0"]
    B --> C["go mod tidy propagates\ngo directive: 1.24.2 → 1.25.0"]
    C --> D["x/sys bumped\nv0.41.0 → v0.42.0\n(indirect)"]
    C --> E{"CI workflows\ngo-version: '1.24'"}
    E -->|"1.24 < 1.25.0 required"| F["❌ Build fails\nci.yml · rc.yml · release.yml"]
    E -->|"Fix: bump to '1.25'"| G["✅ All CI passes"]

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: src/go.mod
Line: 3

Comment:
**Go version directive breaks all CI pipelines**

The `go` directive was bumped from `1.24.2` to `1.25.0` as a transitive consequence of `golang.org/x/term v0.41.0` (its upstream `go.mod` now requires Go 1.25.0). However, all three CI workflows pin the Go toolchain to `'1.24'`:

- `.github/workflows/ci.yml` (line 25): `go-version: '1.24'`
- `.github/workflows/rc.yml` (line 46): `go-version: '1.24'`
- `.github/workflows/release.yml` (line 110): `go-version: '1.24'`

Starting with Go 1.21, the `go` directive in `go.mod` is enforced as a **minimum toolchain requirement**. A Go 1.24.x toolchain building a module that declares `go 1.25.0` will refuse to proceed with an error such as:

```
go: module requires Go >= 1.25.0
```

Merging this PR as-is will cause every CI job (tests, RC builds, and release builds) to fail. The CI workflows need to be updated to `go-version: '1.25'` (or `'1.25.0'`) before or alongside this dependency bump.

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: "deps: bump golang.or..."}

[greptile-apps]

Go version directive breaks all CI pipelines

The go directive was bumped from 1.24.2 to 1.25.0 as a transitive consequence of golang.org/x/term v0.41.0 (its upstream go.mod now requires Go 1.25.0). However, all three CI workflows pin the Go toolchain to '1.24':

• .github/workflows/ci.yml (line 25): go-version: '1.24'
• .github/workflows/rc.yml (line 46): go-version: '1.24'
• .github/workflows/release.yml (line 110): go-version: '1.24'

Starting with Go 1.21, the go directive in go.mod is enforced as a minimum toolchain requirement. A Go 1.24.x toolchain building a module that declares go 1.25.0 will refuse to proceed with an error such as:

go: module requires Go >= 1.25.0

Merging this PR as-is will cause every CI job (tests, RC builds, and release builds) to fail. The CI workflows need to be updated to go-version: '1.25' (or '1.25.0') before or alongside this dependency bump.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/go.mod
Line: 3

Comment:
**Go version directive breaks all CI pipelines**

The `go` directive was bumped from `1.24.2` to `1.25.0` as a transitive consequence of `golang.org/x/term v0.41.0` (its upstream `go.mod` now requires Go 1.25.0). However, all three CI workflows pin the Go toolchain to `'1.24'`:

- `.github/workflows/ci.yml` (line 25): `go-version: '1.24'`
- `.github/workflows/rc.yml` (line 46): `go-version: '1.24'`
- `.github/workflows/release.yml` (line 110): `go-version: '1.24'`

Starting with Go 1.21, the `go` directive in `go.mod` is enforced as a **minimum toolchain requirement**. A Go 1.24.x toolchain building a module that declares `go 1.25.0` will refuse to proceed with an error such as:

```
go: module requires Go >= 1.25.0
```

Merging this PR as-is will cause every CI job (tests, RC builds, and release builds) to fail. The CI workflows need to be updated to `go-version: '1.25'` (or `'1.25.0'`) before or alongside this dependency bump.

How can I resolve this? If you propose a fix, please make it concise.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.