@cryptotaxi247 / kubo / commits / 136a6dc56

release: update changelog

Steven Allen committed Jul 5, 2019 at 02:17 UTC 136a6dc5653ee92813610b6b5528efede3933a02
1 file changed +30
CHANGELOG.md
+30
@@ -1,5 +1,35 @@
1 # go-ipfs changelog
2
3 +## 0.4.22 2019-07-05
4 +
5 +We're releasing a PATCH release of go-ipfs based on 0.4.21 containing some
6 +critical fixes while we improve our release process and testing procedures.
7 +
8 +The past several releases have been shaky so we're cutting a patch release to
9 +fix some critical issues in the 0.4.22 while we re-evaluate our release process
10 +and improve our testing.
11 +
12 +This release includes fixes for the following regressions:
13 +
14 +1. A major bitswap throughput regression introduced in 0.4.21
15 + ([ipfs/go-ipfs#6442](https://github.com/ipfs/go-ipfs/issues/6442)).
16 +2. High bitswap CPU usage when connected to many (e.g., 10,000) peers. See
17 + [ipfs/go-bitswap#154](https://github.com/ipfs/go-bitswap/issues/154).
18 +2. The local network discovery service sometimes initializing before the
19 + networking module, causing it to announce the wrong addresses and sometimes
20 + complain about not being able to determine the IP address)
21 + ([ipfs/go-ipfs#6415](https://github.com/ipfs/go-ipfs/pull/6415)).
22 +
23 +It also includes fixes for:
24 +
25 +1. Pins not being persisted after `ipfs block add --pin`
26 + ([ipfs/go-ipfs#6441](https://github.com/ipfs/go-ipfs/pull/6441)).
27 +2. Concurrent map access on GC due to the pinner
28 + ([ipfs/go-ipfs#6419](https://github.com/ipfs/go-ipfs/pull/6419)).
29 +3. Potential pin-set corruption given a concurrent `ipfs repo gc` and `ipfs pin
30 + rm` ([ipfs/go-ipfs#6444](https://github.com/ipfs/go-ipfs/pull/6444)).
31 +4. Build failure due to a deleted git tag in one of our dependencies.
32 +
33 ## 0.4.21 2019-05-30
34
35 We're happy to announce go-ipfs 0.4.21. This release has some critical bug fixes