From e88120c535291cfffdd78ed070b076cb1e7a746d Mon Sep 17 00:00:00 2001
From: Guillaume Fay <guillaume_fay@hotmail.com>
Date: Tue, 8 Dec 2020 20:07:41 +0100
Subject: [PATCH] fix: publish release instructions

---
 README.md    | 10 ++++------
 package.json |  2 +-
 2 files changed, 5 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index 37deb06..831f43e 100644
--- a/README.md
+++ b/README.md
@@ -19,12 +19,10 @@ npm run build
 npm run lint
 
 # Publish new release
-## Update package.json with new version X.X.X (TODO : automate this with git hooks)
-git tag vX.X.X
-git push origin vX.X.X
-
-## Create draft release on github with the tag created just before
-
+## Draft a new release. Set the “Tag version” to the value of version in your application package.json, and prefix it with v. “Release title” can be anything you want.
+## For example, if your application package.json version is 1.0, your draft’s “Tag version” would be v1.0.
+## Push some commits. Every CI build will update the artifacts attached to this draft.
+### Once you are done, publish the release. GitHub will tag the latest commit for you
 npm run build:publish
 
 ```
diff --git a/package.json b/package.json
index b6ed40a..54ed470 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "hip-note",
-  "version": "1.2.0",
+  "version": "1.2.2",
   "author": "Guillaume Fay",
   "description": "Markdown editor with templates for taking notes, writing articles, generating resumes and much more!",
   "license": "MIT",