Now that we have an API Key saved to GitHub Actions for NPM, we can use it to automate releasing this lib. Once a GitHub Release has been created (which automatically creates an accompanying tag), GitHub Actions will build and publish the library to NPM.
Tests weren't happy without re-recording cassettes, probably leftover from the revert last week?
Testing
This is the same workflow we use locally
Pull Request Type
Please select the option(s) that are relevant to this PR.
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Improvement (fixing a typo, updating readme, renaming a variable name, etc)
Description
Now that we have an API Key saved to GitHub Actions for NPM, we can use it to automate releasing this lib. Once a GitHub Release has been created (which automatically creates an accompanying tag), GitHub Actions will build and publish the library to NPM.
Tests weren't happy without re-recording cassettes, probably leftover from the revert last week?
Testing
This is the same workflow we use locally
Pull Request Type
Please select the option(s) that are relevant to this PR.