-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gomod: go 1.21.3 not supported #8203
Comments
Should be fixed now! |
yep it's working now, thanks @jakecoffman ! |
Hi @jakecoffman, I'm wondering if you could share what the fix here was? I'm seeing this for 1.21.4 currently:
…it seems to be happening with each new Go release. |
My understanding is that #8225 was not a permanent fix. It just made it so that quickly after each go release, we'll get a Dependabot PR to bump the version that Dependabot uses, and as soon as that PR lands, Dependabot is able to handle the new go release. In this case, we should be getting a PR bumping go to 1.21.4 next Monday, and once that's merged it will be all good. |
Go was bumped in #8374 so it should be good now. |
Is there an existing issue for this?
Package ecosystem
Go
Package manager version
No response
Language version
1.21.3
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
In my
go.mod
I haveand now dependabot fails to do anything with errors like
I always assumed that dependabot would use the version specified in
go.mod
to run the updates, but looks like it isn't?Maybe I'm missing something with the new go.mod versioning? Manually updating the go patch version every time a new version comes out is already getting old...
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: