-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
Is there an existing issue for this?
- I have searched the existing issues
Package ecosystem
gomod
Package manager version
No response
Language version
1.24.1
Manifest location and content before the Dependabot update
.github/dependabot.yml
dependabot.yml content
version: 2
registries:
my-company:
type: git
url: https://git.company.com
username: x-access-token
password: ${{secrets.GH_ACCESS_TOKEN}}
updates:
- package-ecosystem: "gomod"
directory: "/"
schedule:
interval: "daily"
registries:- my-company
Updated dependency
No response
What you expected to see, versus what you actually saw
Since the GOTOOLCHAIN variable is set to local+auto, I expected that the packages in gomod could be updated normally regardless of the version of the dependabot-action. However, among the packages I use, if its go version is higher than the runner's version, it will cause a destination_file_not_resolvable error. If it is less than or equal to the runner's version, I have confirmed that it works normally. How do I work around this?
The image of the runner I used was github/dependabot-action@ghes-3.14.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Handled error whilst updating sigs.k8s.io/controller-runtime: dependency_file_not_resolvable {:message=>"go: loading module retractions for sigs.k8s.io/controller-runtime@v0.1.1: module sigs.k8s.io/controller-runtime@v0.20.3 requires go >= 1.23.0 (running go 1.22.4; GOTOOLCHAIN=local+auto)"}
Smallest manifest that reproduces the issue
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status