-
Notifications
You must be signed in to change notification settings - Fork 80
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
dependabot struggles with wasmtime-go #110
Comments
I'd love to have a better way to ship this library without checking in precompiled binaries but I haven't ever figured out a way to do so :( |
I don't know what, but something happened -- I've just had a dependabot-created PR for wasmtime-go 0.38.0. 🎉 That's good news. Let's see if the problem is just gone. 🤞 |
It's OK now, I think. Closing. |
The problem came but, not it slightly changed its shape:
The icky thing is that you don't notice, and you can't see for how long it has been failing -- but that's a dependabot UX issue. |
Hi there.
I'm sure others have run into this, too: dependabot fails to update wasmtime-go, and projects depending on it. We're seeing this with basically every release:
OPA updating wasmtime-go via dependabot fails (Time out)
The same thing happens with every project depending on OPA after OPA has (manually) bumped wasmtime-go. My guess is that it has to do with the size of the release's binary libs, and the way they'd have to be pulled down and pushed up for a PR, since OPA vendors its dependencies.
I'm sharing this here because I might be missing some workaround...? Has anyone solved that issue?
We've already got a support ticket open with github, but there's hasn't been much progress with that.
The text was updated successfully, but these errors were encountered: