prepare for 2.0.0 (#147)

README.md

@@ -190,17 +190,12 @@ envman add --key SOME_KEY --valuefile /path/to/file/which/contains/the/value --e
 
 ### Release a new version
 
-1. Update go dependencies (`bitrise run dep-update`)
-1. PR & merge these changes to the `master` branch
-1. Bump `RELEASE_VERSION` in bitrise.yml
-1. Commit (do not Push) these changes on `master` branch
-1. Run `bitrise run create-release`
-1. Fill the current version's `Release Notes` section in `CHANGELOG.md`
-1. Push the changes to the `master` branch
-1. Open the project's bitrise app on bitrise.io, find the triggered `create-release` workflow run's build
-1. Download and test the generated bitrise binaries (`envman version --full`)
-1. Create the new version's release on [github](https://github.com/bitrise-io/envman/releases/new):
-  - Fill Tag and Version inputs
-  - Copy paste the Changelog's `Release Notes` and `Install or upgrade` sections to the release description on github
-  - Attach the generated (on bitrise.io) linux and darwin binaries to the release
-  - Push the `Publish release` button on github
+- merge every code changes to the master branch
+
+- do not forget to merge every version related file changes:
+
+  - update the version number (in version.go file)
+  - update version tests (in _tests/integration/version_test.go file)
+  - update version number in bitrise.yml
+
+- push the new version tag to the master branch

version/version.go

@@ -1,4 +1,4 @@
 package version
 
 // VERSION ...
-const VERSION = "1.2.1"
+const VERSION = "2.0.0"