Ipfs release 0.4.10
License: MIT Signed-off-by: Jeromy <jeromyj@gmail.com>
Jeromy committed
Jun 26, 2017 at 22:24 UTC
48cbd2d75ff2d8d5d0a7f6c93b60ca78457d0e71
3 files changed
+45
-3
CHANGELOG.md
+43
-1
@@ -1,6 +1,48 @@
1
# go-ipfs changelog
2
3
-### 0.4.10 - 2017-06-18
3
+### 0.4.10 - 2017-06-27
4
+
5
+Ipfs 0.4.10 is a patch release that contains several exciting new features,
6
+bugfixes and general improvements. Including new commands, easier corruption
7
+recovery, and a generally cleaner codebase.
8
+
9
+The `ipfs pin` command has two new subcommands, `verify` and `update`. `ipfs
10
+pin verify` is used to scan the repo for pinned object graphs and check their
11
+integrity. Any issues are reported back with helpful error text to make error
12
+recovery simpler. This subcommand was added to help recover from datastore
13
+corruptions, particularly if using the experimental filestore and accidentally
14
+deleting tracked files.
15
+`ipfs pin update` was added to make the task of keeping a large, frequently
16
+changing object graph pinned. Previously users had to call `ipfs pin rm` on the
17
+old pin, and `ipfs pin add` on the new one. The 'new' `ipfs pin add` call would
18
+be very expensive as it would need to verify the entirety of the graph again.
19
+The `ipfs pin update` command takes shortcuts, portions of the graph that were
20
+covered under the old pin are assumed to be fine, and the command skips
21
+checking them.
22
+
23
+Next up, we have finally implemented an `ipfs shutdown` command so users can
24
+shut down their ipfs daemons via the API. This is especially useful on
25
+platforms that make it difficult to control processes (Android, for example),
26
+and is also useful when needing to shut down a node remotely and you do not
27
+have access to the machine itself.
28
+
29
+`ipfs add` has gained a new flag; the `--hash` flag allows you to select which
30
+hash function to use and we have given it the ability to select `blake2b-256`.
31
+This pushes us one step closer to shifting over to using blake2b as the
32
+default. Blake2b is significantly faster than sha2-256, and also is conjectured
33
+to provide superior security.
34
+
35
+We have also finally implemented a very early (and experimental) `ipfs p2p`.
36
+This command and its subcommands will allow you to open up arbitrary streams to
37
+other ipfs peers through libp2p. The interfaces are a little bit clunky right
38
+now, but shouldn't get in the way of anyone wanting to try building a fully
39
+peer to peer application on top of ipfs and libp2p. For more info on this
40
+command, to ask questions, or to provide feedback, head over to the [feedback
41
+issue](https://github.com/ipfs/go-ipfs/issues/3994) for the command.
42
+
43
+A few other subcommands and flags were added around the API, as well as many
44
+other requested improvements. See below for the full list of changes.
45
+
46
47
- Features
48
- Add support for specifying the hash function in `ipfs add` ([ipfs/go-ipfs#3919](https://github.com/ipfs/go-ipfs/pull/3919))
package.json
+1
-1
@@ -312,6 +312,6 @@
312
"language": "go",
313
"license": "MIT",
314
"name": "go-ipfs",
315
- "version": "0.4.10-rc1"
315
+ "version": "0.4.10"
316
}
317
repo/config/version.go
+1
-1
@@ -4,6 +4,6 @@ package config
4
var CurrentCommit string
5
6
// CurrentVersionNumber is the current application's version literal
7
-const CurrentVersionNumber = "0.4.10-rc1"
7
+const CurrentVersionNumber = "0.4.10"
8
9
const ApiVersion = "/go-ipfs/" + CurrentVersionNumber + "/"