Update module golang.org/x/term to v0.45.0 - #131
Closed
renovate[bot] wants to merge 1 commit into
Closed
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/golang.org-x-term-0.x
branch
2 times, most recently
from
May 16, 2026 00:32
ced76ce to
2c20946
Compare
renovate
Bot
force-pushed
the
renovate/golang.org-x-term-0.x
branch
from
June 8, 2026 16:50
2c20946 to
8b4baa5
Compare
renovate
Bot
force-pushed
the
renovate/golang.org-x-term-0.x
branch
from
July 8, 2026 20:05
8b4baa5 to
8cbf8bd
Compare
Collaborator
|
Superseded by #144, which updates this along with the rest of the Go module set in one change. Closing to keep the dependency surface reviewable as a single unit. |
Contributor
Author
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
TheFynx
added a commit
that referenced
this pull request
Jul 31, 2026
* chore(deps): update Go dependencies Refreshes all Go module dependencies to current releases, superseding the individual bot PRs for the direct ones: - github.com/go-git/go-git/v5 5.19.1 -> 5.19.2 (renovate #140, dependabot #135) - github.com/ulikunitz/xz 0.5.15 -> 0.5.16 (renovate #139) - golang.org/x/term 0.44.0 -> 0.45.0 (renovate #131) - github.com/go-git/go-billy/v5 (indirect) -> 5.9.1 (dependabot #134) Plus the transitive set, notably golang.org/x/crypto 0.53.0 -> 0.54.0, golang.org/x/net 0.56.0 -> 0.57.0 and google.golang.org/protobuf 1.33.0 -> 1.36.11. No source changes were needed. govulncheck now reports zero vulnerabilities, where the previous tree had one. Verified: go build, go test ./..., go vet, golangci-lint and gosec all pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * ci: run checks on every pull request The workflow only triggered for PRs targeting master, so a PR based on another PR's branch got no checks at all — which is exactly the shape of the stack this series uses. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.44.0→v0.45.0Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.