Release v1.13

Author: Julien Castets

MAINTAINERS.md

@@ -11,9 +11,16 @@ For the sake of the example, we assume you want to release the version `42.8`.
 
 ### Commit release
 
-* Edit the Changelog in [README.md](README.md), ensure it is up to date and
-  fill the current date. Also update the link in the line "View full commits
-  list": replace *master* with *v42.8*.
+* Edit the Changelog at the bottom of [README.md](README.md).
+
+  - Header: change the version from *v42.7* (or whatever is the previous
+    version) to *v42.8*
+  - Header: replace "unreleased" with the current date
+  - Content: read commits history, and fill the changelog if it's not already
+    done
+  - Footer: edit the "View full commit list" link from */compare/v42.7..master*
+    to */compare/v42.8..v42.7*
+
 * Edit [pkg/scwversion/version.go](pkg/scwversion/version.go) and update the
   *VERSION* to *v42.8*.
 * Make the commit release: `git commit -m 'Release v42.8'`.

README.md

@@ -1200,13 +1200,14 @@ $ scw inspect myserver | jq '.[0].public_ip.address'
 
 ## Changelog
 
-### v1.12+dev (unreleased)
+### v1.13 (2017-05-10)
 
-This is the current development version. Update below with your changes. Remove
-this line when releasing the package.
 * Add new ARM64 offers
+* For scaleway-cli developers: build time is improved, and standard tools are
+  used to cross-compile the project
+* Ask two-factor authentication token on `scw login`
 
-View full [commits list](https://github.com/scaleway/scaleway-cli/compare/v1.12...master)
+View full [commits list](https://github.com/scaleway/scaleway-cli/compare/v1.13...v1.12)
 
 ### v1.12 (2017-03-30)
 

pkg/scwversion/version.go

@@ -4,7 +4,7 @@ import "fmt"
 
 var (
 	// VERSION represents the semver version of the package
-	VERSION = "v1.12+dev"
+	VERSION = "v1.13"
 
 	// GITCOMMIT represents the git commit hash of the package, it is configured at build time
 	GITCOMMIT string