ci: change CI to publish to GitHub package registry

* Only publish package on successful builds of the experience-cs
  branch.

* Configure npm to use github registry URL

* Use organisation-specific release version to avoid confusion with
  versions in the canonical package and use "experience-cs" string
  to distinguish it from the package version(s) used by other projects.

* Always publish using "latest" npm tag.

* Add `--access public` option to `npm publish` command, because scoped
  packages only allow "restricted" access by default.

* We can use the GITHUB_TOKEN that is made available by default in a
  GitHub Action as `NODE_AUTH_TOKEN`, although we need to add the
`packages: write` permission to the Action.

Co-authored-by: Chris Lowis <[email protected]>

Author: sebjacobs

.github/workflows/ci-cd.yml

@@ -3,6 +3,7 @@ name: CI/CD
 on:
     workflow_dispatch: # Allows you to run this workflow manually from the Actions tab
     push: # Runs whenever a commit is pushed to the repository
+        branches: [experience-cs]
 
 concurrency:
     group: "${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}"
@@ -13,6 +14,7 @@ permissions:
     pages: write # deploy to GitHub Pages
     issues: write # comment on released issues
     pull-requests: write # comment on released pull requests
+    packages: write # deploy to GitHub Packages
 
 jobs:
     ci-cd:
@@ -27,6 +29,7 @@ jobs:
               with:
                   cache: "npm"
                   node-version-file: ".nvmrc"
+                  registry-url: "https://npm.pkg.github.com"
 
             - name: Info
               run: |
@@ -45,7 +48,8 @@ jobs:
 
             - name: Semantic release (configured to run dry if branch is other than 'develop')
               env:
-                  NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
-                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+                  NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
               run: |
-                  npx --no -- semantic-release
+                  RELEASE_VERSION="0.1.0-experience-cs.$(date +'%Y%m%d%H%M%S')"
+                  npm version --no-git-tag-version $RELEASE_VERSION
+                  npm publish --access public --tag latest