-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Release v0.4.20 #6163
Comments
Is there any way we can add a generation of PeerId through HTTP-RPC by supplying a public key? |
@Stebalien Just want to confirm with you that v0.4.20 will be released today(3rd April), right? Thanks. I am waiting to use your latest release. 😃 |
@CoreyLin He said release candidate 1 on Wednesday. |
@lordcirth @Stebalien OK. So the release date is not finalized, right? |
Update to IPFS Web UI 2.4.4! I'll PR now. |
Done: #6169 |
@reardenlife I'm trying to avoid "one more thinging" this release. @CoreyLin it'll be released when it's ready but I'm planning on cutting an RC1 today. |
@Stebalien at the risk of “one more thinging”(tm), exposing peer protection as a swarm command would be welcome by users and infra: libp2p/go-libp2p-connmgr#36 it’s low risk as it doesn’t interfere with existing functionality nor the main loop |
I'd like to avoid shipping a new command at this point. However, we can ship a custom build to infra. |
OK, so the RC1's going to be coming tomorrow. I'd really like to get that QUIC fix in at least. |
Please also include an update of the |
Note that I have tagged v0.0.4 in go-libp2p. |
@vyzo done. |
Status: wrestling with the distribution scripts and go modules (and trying not to break rebuilding of old versions with gx). |
Are there any known issues with rc1 that need fixing? |
I promised a short release and got distracted. Luckily, @whyrusleeping came to the rescue so we're going to cut a release ASAP (RC1 on Wednesday).
The primary features will be:
ipfs add [--nocopy] URL
.What am I missing?
TODOs:
LevelDB panic #6146 (may be a memory corruption issue)no ideaThe text was updated successfully, but these errors were encountered: