From 7ea34c6c6ed18e886f869a1fbe725a848d13695c Mon Sep 17 00:00:00 2001
From: Jeromy <jeromyj@gmail.com>
Date: Fri, 12 May 2017 11:36:24 -0700
Subject: [PATCH] Ipfs release 0.4.9

License: MIT
Signed-off-by: Jeromy <jeromyj@gmail.com>
---
 .gx/lastpubver         |  2 +-
 CHANGELOG.md           | 25 +++++++++++++++++++++++++
 package.json           |  2 +-
 repo/config/version.go |  2 +-
 4 files changed, 28 insertions(+), 3 deletions(-)

diff --git a/.gx/lastpubver b/.gx/lastpubver
index ef5e060c2..7afbdf417 100644
--- a/.gx/lastpubver
+++ b/.gx/lastpubver
@@ -1 +1 @@
-0.4.8: QmPnTPuoB9y4Wzm3j8BdUmoqG7icmN7zGazDLuT4Duke9S
+0.4.9: QmQuvzi7p2qv9oduQ8o6fhPXDBCns9ryjjxqumyNvE5gZs
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 27c4b809d..ee3172a29 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,31 @@
 
 ### 0.4.9 - 2017-04-30
 
+Ipfs 0.4.9 is a maintenance release that contains several useful bugfixes and
+improvements. Notably, `ipfs add` has gained the ability to select which CID
+version will be output. The common ipfs hash that looks like this:
+`QmRjNgF2mRLDT8AzCPsQbw1EYF2hDTFgfUmJokJPhCApYP` is a multihash. Multihashes
+allow us to specify the hashing algorithm that was used to verify the data, but
+it doesn't give us any indication of what format that data might be. To address
+that issue, we are adding another couple of bytes to the prefix that will allow us
+to indicate the format of the data referenced by the hash. This new format is
+called a Content ID, or CID for short. The previous bare multihashes will still
+be fully supported throughout the entire application as CID version 0. The new
+format with the type information will be CID version 1. To give an example,
+the content referenced by the hash above is "Hello Ipfs!". That same content,
+in the same format (dag-protobuf) using CIDv1 is
+`zb2rhkgXZVkT2xvDiuUsJENPSbWJy7fdYnsboLBzzEjjZMRoG`.
+
+CIDv1 hashes are supported in ipfs versions back to 0.4.5. Nodes running 0.4.4
+and older will not be able to load content via CIDv1 and we recommend that they
+update to a newer version.
+
+There are many other use cases for CIDs. Plugins can be written to
+allow ipfs to natively address content from any other merkletree based system,
+such as git, bitcoin, zcash and ethereum -- a few systems we've already started work on.
+
+Aside from the CID flag, there were many other changes as noted below:
+
 - Features
   - Add support for using CidV1 in 'ipfs add' ([ipfs/go-ipfs#3743](https://github.com/ipfs/go-ipfs/pull/3743))
 - Improvements
diff --git a/package.json b/package.json
index 07082e792..f4ee43aa7 100644
--- a/package.json
+++ b/package.json
@@ -312,6 +312,6 @@
   "language": "go",
   "license": "MIT",
   "name": "go-ipfs",
-  "version": "0.4.9-rc2"
+  "version": "0.4.9"
 }
 
diff --git a/repo/config/version.go b/repo/config/version.go
index 4f265a10b..325bb8ae3 100644
--- a/repo/config/version.go
+++ b/repo/config/version.go
@@ -4,6 +4,6 @@ package config
 var CurrentCommit string
 
 // CurrentVersionNumber is the current application's version literal
-const CurrentVersionNumber = "0.4.9-rc2"
+const CurrentVersionNumber = "0.4.9"
 
 const ApiVersion = "/go-ipfs/" + CurrentVersionNumber + "/"