Changed order to fix the publish pipeline (#7)

Author: allancassaro

.github/workflows/publish.yaml

@@ -68,14 +68,21 @@ jobs:
         new_version="${major}.${minor}.${patch}"
         echo "New release is ${new_version}"
         echo "new_version=${new_version}" >> "$GITHUB_OUTPUT"
-        git pull --rebase
         npm version --no-git-tag-version --allow-same-version $new_version || exit 0
 
+    - name: Publish the package
+      env:
+        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      run: npm publish --access public
+
     - name: Commit the changes
-      continue-on-error: true
-      run: | 
+      env:
+        new_version: ${{ steps.set_new_version.outputs.new_version }}
+      run: |
+        git reset --hard
         git config --global user.email 'github-ci@boldcommerce.com'
         git config --global user.name 'bold-github-ci'
+        npm version --no-git-tag-version --allow-same-version $new_version || exit 0
         git add package.json package-lock.json
         git commit -m 'Bump version number for release' || exit 0
         git push origin || exit 0
@@ -84,8 +91,4 @@ jobs:
       env:
         new_version: ${{ steps.set_new_version.outputs.new_version }}
       run: |
-        gh release create ${new_version} --generate-notes --latest
-
-    - run: npm publish --access public
-      env:
-        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        gh release create ${new_version} --generate-notes --latest