Closed maschad closed 1 year ago
This is fixed now but it's almost certainly going to happen again.
Our options are:
My preference is for 2, but 1 might be faster.
Seeing as the go-libp2p-daemon's libp2p version is not going to be actively updated by design, I would say that we should invest the effort in 2 as well to remove it as a dependency.
closing in favor of https://github.com/libp2p/js-libp2p-webtransport/issues/75
Option 3, which is the simplest, is to pin the version of Go.
The reason that wasn't added as an option above is that it means adding go config to every JS repo, which didn't feel like a natural thing to do.
These failures on CI suggest that the version of quic-go bing used can't be built on Go 1.20 yet. Should we downgrade it to a compatible version?