docs: update readme and release instructions

Author: kerimdzhanov

README.md

@@ -29,12 +29,18 @@ $ yarn add dotenv-flow
 
 ## Usage
 
-As early as possible in your application, require and configure **dotenv-flow**.
+As early as possible in your Node.js application initialize **dotenv-flow**:
 
 ```js
 require('dotenv-flow').config();
 ```
 
+or, if you're using typescript:
+
+```ts
+import 'dotenv-flow/config';
+```
+
 After this, you can access all the environment variables you have defined in your `.env*` files through `process.env.*`.
 
 For example, let's suppose that you have the following `.env*` files in your project:

RELEASE.md

@@ -2,10 +2,13 @@
 
 ## Shipping a new version
 
-1. Ensure you've pushed all the necessary changes to the repo and tests are successfully passed on TravisCI
+1. Make sure all the latest changes are pushed to the repo and all the related
+   workflow tests are passing on CI (https://github.com/kerimdzhanov/dotenv-flow/actions)
 2. Bump up the version in `package.json`
 3. Update the `CHANGELOG.md` file using `$ yarn changelog`
 4. Make a release commit with a message in format of `chore(release): vX.Y.Z`
 5. Tag the release commit using `$ git tag vX.Y.X`
-6. Push the release commit (including the tag) to GitHub `$ git push && git push --tags`
-7. Publish the new package version using `$ yarn publish [--tag=next]`
+6. Push the release commit (with the tag) to GitHub `$ git push && git push --tags`
+7. Create a new version release on GitHub based on the created tag
+
+> Once the release is published, Github Actions' workflow will build and publish the new package version to NPM.