Skip to content

Update Go toolchain to v1.27.0 - #2759

Open
github-actions[bot] wants to merge 2 commits into
mainfrom
renovate/go-toolchain
Open

Update Go toolchain to v1.27.0#2759
github-actions[bot] wants to merge 2 commits into
mainfrom
renovate/go-toolchain

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
go (source) minor 1.26.61.27.0
golang (source) minor 1.26.61.27.0

Configuration

📅 Schedule: (UTC)

  • 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 becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@github-actions github-actions Bot added dependencies Issue/PR Pull about a dependency file renovate Pull requests generated by renovate bot labels Aug 19, 2026
@copy-pr-bot

copy-pr-bot Bot commented Aug 19, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Comment thread docker/Dockerfile Outdated
@github-actions
github-actions Bot force-pushed the renovate/go-toolchain branch from 1d9bc47 to f5ca74e Compare August 21, 2026 17:23
@github-actions github-actions Bot changed the title Update dependency go to v1.27.0 Update Go toolchain to v1.27.0 Aug 21, 2026
@rajathagasthya

Copy link
Copy Markdown
Contributor

/ok-to-test f5ca74e

pull Bot pushed a commit to Reality2byte/gpu-operator that referenced this pull request Aug 21, 2026
The custom regex manager for docker/Dockerfile only matched the golang
version and resolved it via the golang-version datasource, which has no
notion of image digests. Renovate PRs bumped the tag but left the pinned
@sha256 digest unchanged (e.g. NVIDIA#2759); since the digest takes precedence
over the tag at pull time, builds silently kept using the old image. The
other digest-pinned base images (ubi9, debian, distroless/cc) were not
managed at all.

Replace the golang-specific manager with a generic one that captures the
image name, tag, and digest from every pinned FROM line and resolves
updates via the docker datasource, so tag and digest are updated
together. Images with non-version tags (ubi9:latest, debian:trixie-slim)
get digest-only updates. Extend the Go toolchain group rule so golang
image bumps still land in the same PR as the versions.mk GOLANG_VERSION
bump.

Signed-off-by: Rajath Agasthya <ragasthya@nvidia.com>
@rajathagasthya

Copy link
Copy Markdown
Contributor

/ok-to-test 0fabfbf

That version supports Go 1.27.

The staticcheck bundled with v2.13.1 reports SA1019 deprecation issues
that the previous version did not, so fix those as well:

The .golangci.yml exclusions for the deprecated licensing-config fields
stopped matching because staticcheck now emits full type symbol names
((pkg.Type).Field). Update the patterns to the new format.

Drop the deprecated Requeue field from the upgrade controller's
results. RequeueAfter is always set to a non-zero interval there, and
controller-runtime ignores Requeue whenever RequeueAfter is positive.

Signed-off-by: Rajath Agasthya <ragasthya@nvidia.com>
@rajathagasthya

Copy link
Copy Markdown
Contributor

/ok-to-test 2cd3d6b

@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 37.542% (-1.0%) from 38.495% — renovate/go-toolchain into main

Comment thread controllers/upgrade_controller.go
@tariq1890

Copy link
Copy Markdown
Contributor

Coverage Status
coverage: 37.542% (-1.0%) from 38.495% — renovate/go-toolchain into main

This is quite the drop. Do we know why?

@github-actions

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Issue/PR Pull about a dependency file renovate Pull requests generated by renovate bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants