chore: fix alpha releases and docker images

.github/workflows/build.yml

@@ -251,7 +251,7 @@ jobs:
           git config --global user.name 'github-actions[bot]'
           git config --global user.email 'github-actions[bot]@users.noreply.github.com'
       - name: release and publish to NPM
-        run: yarn lerna publish --yes --conventional-commits --conventional-prerelease --dist-tag alpha --exact --create-release github
+        run: yarn lerna publish --yes --conventional-commits --conventional-prerelease --conventional-bump-prerelease --dist-tag alpha --exact --create-release github
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/post-release-docker-hub.yml

@@ -20,4 +20,4 @@ jobs:
           password: ${{ secrets.DOCKERHUB_TOKEN }}
 
       - name: build and release the latest Docker image
-        run: make -C docker release version-tag latest-tag
+        run: make -C docker release version-tag branch-tag

CONTRIBUTING.md

@@ -98,7 +98,7 @@ Log4brains follows a **simplified Git Flow** model. Here’s how the process wor
 
    This helps us get feedback from early adopters before merging changes into `stable`, and thus triggering a stable release.
 
-7. **Releasing to Stable**: Once the `develop` branch is stable and tested, the maintainers will merge it into `stable`, and run manually `scripts/release.sh` to publish a new stable release to npm (TODO: should be automated in the future).
+7. **Releasing to Stable**: Once the `develop` branch is stable and tested, the maintainers will merge it into `stable`, and run manually `scripts/release.sh` + `make -C docker release version-tag branch-tag latest-tag` to publish a new stable release to npm (TODO: should be automated in the future).
 
 ### Urgent hotfix specific case