feat(hub-501): trying to use locusrobotics as the registry url

.github/workflows/github-publish.yml

@@ -34,8 +34,9 @@ jobs:
       - name: Install Node.js and npm
         uses: actions/setup-node@v3
         with:
+          always-auth: true
           node-version: ${{ env.NODE_VERSION }}
-          registry-url: https://npm.pkg.github.com
+          registry-url: https://npm.pkg.github.com/locusrobotics
 
       - name: Install dependencies
         if: steps.cacheNpm.outputs.cache-hit != 'true'
@@ -51,8 +52,9 @@ jobs:
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
         run: |
+          npm whoami --registry https://npm.pkg.github.com
           ls -al
-          npm publish --registry https://npm.pkg.github.com
+          npm publish --registry https://npm.pkg.github.com/locusrobotics
 
       - name: Create and publish a release
         uses: softprops/action-gh-release@v1

README.md

@@ -8,6 +8,19 @@ This plugin enables Azure Functions support within the Serverless Framework.
 
 <!-- [![Node Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Node%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Node+Integration+Tests%22) [![Python Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/Python%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22Python+Integration+Tests%22) [![.NET Integration Tests](https://github.com/serverless/serverless-azure-functions/workflows/.NET%20Integration%20Tests/badge.svg)](https://github.com/serverless/serverless-azure-functions/actions?query=workflow%3A%22.NET+Integration+Tests%22) -->
 
+## Tagging (Locus)
+
+When developing a feature/bug, create a feature branch from the correct branch (publish-2.2.1). Be sure to update the package.json version to the next sequential letter.
+When the feature branch is merged into branch `publish-2.2.1`, create a tag via the `scripts/tagBranchForRelease.sh`.
+
+```bash
+$ git checkout publish-2.2.1
+$ git pull
+$ ./scripts/tagBranchForRelease.sh publish-2.2.1
+```
+
+Once the tag is pushed, the GitHub action workflow, `github-publish.yml` should run, which will do the publish to the private GitHub package registry.
+
 ## Quickstart
 
 ### Pre-requisites