JS release updates

.github/workflows/js-release.yml

@@ -27,11 +27,10 @@ jobs:
           yarn install
           npm run build --workspaces --if-present
       - name: upgrade & publish version(s)
-        ## TODO version and publish commands need to be adjusted when we're confident with the pipeline
         run: |
-          npx changeset version --snapshot migration
-          npx changeset publish --no-git-tag --snapshot
-      ## TODO enable the git tagging when we're confident with the pipeline
-      ##- name: Push to git
-      ##  run: |
-      ##    git push --follow-tags
+          npx changeset version
+          npx changeset publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_REGISTRY_TOKEN }}
+      - name: Push to git
+        run: git push --follow-tags

visual-js/.changeset/tasty-cheetahs-talk.md

@@ -0,0 +1,9 @@
+---
+"@saucelabs/visual": minor
+"@saucelabs/cypress-visual-plugin": minor
+"@saucelabs/nightwatch-sauce-visual-service": minor
+"@saucelabs/visual-storybook": minor
+"@saucelabs/wdio-sauce-visual-service": minor
+---
+
+Bump minor after GH migration

visual-js/CONTRIBUTING.md

@@ -0,0 +1,6 @@
+## Using changesets
+
+- Please use `npx changeset` command to instruct [changesets](https://github.com/changesets/changesets/tree/main) to generate the change summary and versioning information.
+  After you're done with the command you'll be able to see a .md file created in .changeset folder listing the packages and the type of release picked (major, minor or patch)
+
+- Once the PR is merged, `JS (release)` GitHub action needs to be run manually. This action will run `npx changeset version` to update and commit the package.json files using the release information from the .md file. `npx changeset publish` is executed right after to publish the latest version to public npm registry.