docs(README): #354 update versioning heading in README

Author: abhisheksr01

README.md

@@ -552,8 +552,8 @@ In this section we are going to explore [OWASP ZAP](https://www.zaproxy.org/docs
       -t [TARGET_REST_API] -g gen.conf -r pentest-report.html
   ```
 
-  | Parameter       |      Description                         |
-  |-----------------|:---------------------------------------- |
+  | Parameter       | Description                              |
+  |-----------------|:-----------------------------------------|
   | $(pwd)          | Directory where report will be generated |
   | zap-baseline.py | Zap's python script                      |
   | -t [TARGET_URL] | URL to be Pen Tested                     |
@@ -1071,12 +1071,41 @@ Listing down some of the exciting features am going to work on and update the Gi
 
 ### Versioning
 
-We use [SemVer](http://semver.org/) for versioning. For the versions
-available, see the
-[tags on this repository](https://github.com/your/project/tags).
+We use [Cocogitto](https://github.com/cocogitto/cocogitto) for releasing [Semantic SemVer](http://semver.org/) versioned GitHub releases in this repository.
 
-### License
+Check the [Releases](https://github.com/abhisheksr01/spring-boot-microservice-best-practices/releases) section in repository to know the latest releases.
+
+The GitHub releases are automated in the GHA CI based on [Cocogitto's conventional commit types](https://docs.cocogitto.io/guide/commit.html).
+
+<details>
+
+<summary>Clicks here for details on this repository automated the releases.</summary>
+
+#### GHA CI release flow
+
+- When a change is committed to the repository with conventional commit type the GHA CI pipeline is triggered
+- The `docker-build-push` job `cog-bump` step validates whether a version bump is required or not and if required then calculates the new version based on conventional commit type
+- In the `docker-build-push` job we pass an dryrun argument to `cog-bump` step which only provides the version to be bumped.
+- Then we build the image with this new version and test the changes.
+- Once all the changes are verified in the CI we publish the latest version tags and publish a GitHub release with all the relevant changes.
 
-This project is licensed under the MIT License - see the
-[LICENSE.md](LICENSE.md) file for details
+</details>
+
+- We utilize [Cocogitto](https://github.com/cocogitto/cocogitto) to automate the process of creating [Semantic SemVer](http://semver.org/) GitHub releases for this repository.
+- For information on the latest [releases](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases), please visit the Releases section of the repository.
+- The release process is automated through GitHub Actions (GHA CI), following [Cocogitto's conventional commit types](https://docs.cocogitto.io/guide/commit.html)..
+
+<details>
+<summary>Click here for details on how the releases are automated in this repository.</summary>
+
+#### GHA CI Release Process
+- When a commit is made with a conventional commit type, the GHA CI pipeline is triggered.
+- After all the validations the **docker-build-push** job runs the cog-bump step, which checks whether a version bump is necessary. If a bump is needed, it calculates the new version based on the conventional commit type.
+- During this process, we pass a `dry-run: true` argument to the **cog-bump** step to only calculate (but not apply) the version bump.
+- The CI pipeline then builds the Docker image with the new version and tests the changes.
+- Once the changes are verified, the **create-release** job publishes new tags with bumped current version and a GitHub release is created.
+</details>
+
+### License
 
+This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details