-
Notifications
You must be signed in to change notification settings - Fork 492
Deleted upstream dependency; bump github.com/cockroachdb/errors #3659
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
Comments
I'm assuming builds are still ok-ish for most systems because Go uses GOPROXY by default which caches the packages at Google, so those get served out of bounds and not pulled form GitHub, but I'd wager disabling the Go proxy will error. |
Thank you! |
We ran into some issues up in Cockroach and needed to revert. We wont yank the existing tag, so you should still be fine with that version, but we'll want to figure this out by the time we next tag. Going to re-open to track figuring this out. |
I created a I don't think we want to update these deps in CRDB 23.2/24.1 just for the sake of it. |
Sounds good. Feel free to close if there's nothing left to do here. |
Cool, I'll close - we'll make sure the newer deps are kept if more 1.1.x versions are tagged. |
Uh oh!
There was an error while loading. Please reload this page.
Hey there,
We've received a report that our builds are failing ethereum/go-ethereum#29984, and it seems it's a dependency issue originating from Pebble, which in turn originates from
github.com/cockroachdb/errors
v1.11.1 (fixed in cockroachdb/errors#137).It appears that an upstream repo (
sentry-go -> iris
)... just... deleted it's published git version tag. /facepalmAny chance of bumping the
github.com/cockroachdb/errors
package in mainline pebble to the one that has the fixed dependency, and then tagging a v1.1.1 patch release do we could also pick up the fix?Thanks
The text was updated successfully, but these errors were encountered: