🚧 Make publishing packages on GitHub working

.github/workflows/publish.yaml

@@ -1,17 +1,44 @@
-name: Publish
+name: 🚢 Publish
 
 on:
   push:
     branches:
       - main
-    tags:
-      - '**'
+      - release/next
+      - release/alpha
+      - release/beta
 
 jobs:
+  hasTag:
+    name: 🏷️ Analyze Tags
+    runs-on: ubuntu-24.04
+
+    outputs:
+      hasTag: ${{ steps.checkTagExists.outputs.has-tag }}
+
+    steps:
+      - name: Clone repository
+        uses: actions/checkout@v4
+        with:
+          fetch-tags: true
+
+      # ⚠️ This check works only if the tag is pushed alongside the commit
+      # Please, use `git push && git push --tags` or `git push --follow-tags` (works only for annonated tags)
+      - name: Check Tag On Commit
+        id: checkTagExists
+        run: |
+          if [ -n "$(git tag --points-at HEAD)" ]; then
+            echo "has-tag=true" >> $GITHUB_OUTPUT
+          else
+            echo "has-tag=false" >> $GITHUB_OUTPUT
+          fi
+
   publish:
-    if: ${{ startsWith(github.ref, 'refs/tags/') }}
-    name: Publish package
+    name: 📦 Publish Packages
+    needs: hasTag
+    if: ${{ needs.hasTag.outputs.hasTag == 'true' }}
     runs-on: ubuntu-24.04
+
     steps:
       - name: Clone repository
         uses: actions/checkout@v4
@@ -39,4 +66,5 @@ jobs:
       - name: Publish
         run: make publish
         env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}

CONTRIBUTING.md

@@ -255,14 +255,23 @@ For more, please read the article [How to Run GitHub Actions Locally with the ac
 
 ## Publishing
 
-This project uses GitHub Actions to publish the packages automatically to npm. New packages are published after the new tag is pushed to the main branch. PR can be merged only by the appropriate group of maintainers.
+This project uses GitHub Actions to publish the packages automatically to npm.
+New packages are published after the new tag is pushed to the main branch.
+PR can be merged only by the appropriate group of maintainers.
 
 ### Steps to Create a New Package Version
 
-1. Merge all appropriate PRs you want to publish into the main branch
+1. Merge all appropriate PRs you want to publish into the appropriate branch
+   - branches:
+     - `main` - for the latest stable version
+     - `next` - for the canary version
+     - `alpha` - for the alpha version
+     - `beta` - for the beta version
 2. Run the `make version` command to bump the version number in packages (a new version number is determined automatically based on commit history)
 3. Check that the version number is correct and everything looks good
-4. Run manually `git push && git push --tags` to push the changes to the remote
+4. Push changes and tags to repository
+   4a. Run manually `git push && git push --tags` to push the changes to the remote
+   4b. or use `git push --follow-tags` to push the changes and tags at once (works only when tags are annotated).
 5. Publishing is done automatically by GitHub Actions (uses `build` script and `make publish` command)
 
 > If you have further questions do not hesitate to open an issue and ask us! ❤️

Makefile

@@ -96,7 +96,7 @@ version: ## Create new version of packages
 # @see https://github.com/lerna/lerna/tree/main/commands/version#readme
 # Bump version of packages changed since the last release
 # --yes` - skip all confirmation prompts
-	$(PKG_MANAGER) $(MONOREPO_TOOL) version --yes --no-push $(MONOREPO_TOOL_FLAGS) $(MONOREPO_TOOL_NO_PUSH)
+	$(PKG_MANAGER) $(MONOREPO_TOOL) version --create-release github --yes --no-push $(MONOREPO_TOOL_FLAGS) $(MONOREPO_TOOL_NO_PUSH)
 
 build: ## Builds all packages
 	$(PKG_MANAGER) build