go-ipfs 0.4.22 released

go-ipfs 0.4.22 released

We've released a PATCH version of go-ipfs based on 0.4.21 containing some critical fixes.

The IPFS network has scaled to the point where small changes can have a wide-reaching impact on the entire network. To keep this situation from escalating, we've put a hold on releasing new features until we can improve our release process (opens new window) (which we've trialed in this release) and testing procedures (opens new window).

You can read more about the new release process in the release process blog post.

This release includes fixes for the following regressions:

  1. A major bitswap throughput regression introduced in 0.4.21 (ipfs/go-ipfs#6442 (opens new window)).
  2. High bitswap CPU usage when connected to many (e.g. 10,000) peers. See ipfs/go-bitswap#154 (opens new window).
  3. The local network discovery service sometimes initializes before the networking module, causing it to announce the wrong addresses and sometimes complain about not being able to determine the IP address (ipfs/go-ipfs#6415 (opens new window)).

It also includes fixes for:

  1. Pins not being persisted after ipfs block add --pin (ipfs/go-ipfs#6441 (opens new window)).
  2. Panic due to concurrent map access when adding and listing pins at the same time (ipfs/go-ipfs#6419 (opens new window)).
  3. Potential pin-set corruption given a concurrent ipfs repo gc and ipfs pin rm (ipfs/go-ipfs#6444 (opens new window)).
  4. Build failure due to a deleted git tag in one of our dependencies (ipfs/go-ds-badger#64 (opens new window)).

Thanks to:

# ❤️ Contributors

Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started:

# ⁉️ Do you have questions?

The best place to ask your questions about IPFS, how it works and what you can do with it is at discuss.ipfs.io (opens new window). We are also available at the #ipfs channel on Freenode, which is also accessible through our Matrix bridge (opens new window).