cicd: use yarn to publish instead of changesets

Signed-off-by: Alexandre Ferreira <alexjorgef@protonmail.com>

Author: alexjorgef

.github/workflows/release.yml

@@ -35,15 +35,19 @@ jobs:
           registry-url: https://registry.npmjs.org/
       - name: Install Dependencies
         run: yarn --immutable
-      - name: Create Release Pull Request or Publish to npm
-        id: changesets
-        uses: changesets/action@v1
-        with:
-          commit: "chore(release): Publish"
-          title: "Changesets: Version Packages"
-          publish: yarn release
-          # Workaround for https://github.com/changesets/changesets/issues/421
-          version: yarn release-update-lockfile
+      - name: Publish Package
+        run: yarn publish --non-interactive --access public
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      # - name: Create Release Pull Request or Publish to npm
+      #   id: changesets
+      #   uses: changesets/action@v1
+      #   with:
+      #     commit: "chore(release): Publish"
+      #     title: "Changesets: Version Packages"
+      #     publish: yarn release
+      #     # Workaround for https://github.com/changesets/changesets/issues/421
+      #     version: yarn release-update-lockfile
+      #   env:
+      #     GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      #     NPM_TOKEN: ${{ secrets.NPM_TOKEN }}