@bigbinary/neeto-team-members-frontend 2.5.19 → 2.5.21

package/README.md

@@ -12,13 +12,13 @@ functioning of the package. Install all the peer dependencies using the below
 command:
 
     ```zsh
-    yarn add @bigbinary/neeto-commons-frontend@2.0.36 @bigbinary/neeto-icons@1.9.11 @bigbinary/neetoui@4.3.3 @honeybadger-io/js@5.1.1 @honeybadger-io/react@5.1.3 axios@1.3.3 classnames@2.3.2 formik@2.2.9 js-logger@1.6.1 ramda@0.28.0 react-helmet@6.1.0 react-query@3.39.3 react-router-dom@5.3.4 react-toastify@8.2.0 yup@1.0.0
+    yarn add @bigbinary/neeto-commons-frontend@2.0.36 @bigbinary/neeto-filters-frontend@2.6.13 @bigbinary/neeto-icons@1.9.12 @bigbinary/neetoui@4.4.0 @honeybadger-io/js@5.1.1 @honeybadger-io/react@5.1.3 axios@1.3.4 classnames@2.3.2 formik@2.2.9 js-logger@1.6.1 mixpanel-browser@2.45.0 ramda@0.28.0 react-helmet@6.1.0 react-query@3.39.3 react-router-dom@5.3.4 react-toastify@8.2.0 yup@1.0.2
     ```
 
 2. Now install the latest **neetoTeamMembers** package using the below command:
 
     ```zsh
-    yarn add @bigbinary/neeto-team-members-frontend@2.5.17
+    yarn add @bigbinary/neeto-team-members-frontend@2.5.20
     ```
 
 ## Usage
@@ -82,11 +82,27 @@ The configurations for the components present in this NPM package are given belo
     yarn start
     ```
 
-## Building
-
-The neetoTeamMembers package gets published to NPM only whenever we push the PR to the `main` branch.
-By default, we will bump the patch version. If you want to release a minor or major version, then provide the `minor` or `major` label to the PR.
-You can checkout the `publish` workflow in GitHub Actions to get a live update.
+# Building and releasing.
+
+The `@bigbinary/neeto-team-members-frontend` package gets published to NPM when we
+merge a PR with `patch`, `minor` or `major` label to the `main` branch. The
+`patch` label is used for bug fixes, `minor` label is used for new features and
+`major` label is used for breaking changes. You can checkout the
+`Create and publish releases` workflow in GitHub Actions to get a live update.
+
+In case if you missed to add the label, you can manually publish the package.
+For that first you need to create a PR to update the version number in the
+`package.json` file and merge it to the `main` branch. After merging the PR, you
+need to create a
+[new github release](https://github.com/bigbinary/neeto-team-members-frontend/releases/new)
+from main branch. Whenever a new release is created with a new version number,
+the github actions will automatically publish the built package to npm. You can
+checkout the `Publish to npm` workflow in GitHub Actions to get a live update.
+
+Please note that before publishing the package, you need to verify the
+functionality in some of the neeto web-apps locally using `yalc` package
+manager. The usage of yalc is explained in this video:
+https://youtu.be/QBiYGP0Rhe0
 
 ## Integrations