chore: properly promote from @next in the release-latest workflow

10up · Jun 1, 2022 · 90d21c9 · 90d21c9
1 parent 903daef
commit 90d21c9
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/.github/workflows/npm-release-latest-version.yml b/.github/workflows/npm-release-latest-version.yml
@@ -22,9 +22,9 @@ jobs:
 
       - name: Install Dependencies
         run: npm ci
-      - name: Exit pre next
+      - name: Promote from @next
         run: |
-          [[ -f .changeset/pre.json ]] && { npx changeset pre exit; npx changeset version; } || echo 'not in pre mode, no need to exit'
+          [[ -f .changeset/pre.json ]] && { npx changeset pre exit; npx changeset version; git add -u; git commit -m "Version packages"; git push --follow-tags; } || echo 'not in pre mode, no need to exit'
       - name: Create Release Pull Request or Publish to npm
         id: changesets
         uses: changesets/action@v1

diff --git a/packages/hooks/package.json b/packages/hooks/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@10up/react-hooks",
-  "version": "1.2.1-next.0",
+  "version": "1.2.1",
   "description": "",
   "main": "dist/react-hooks.js",
   "module": "dist/react-hooks.mjs",