This pull request changes the release workflow so that it is triggered manually.
Status
Current release workflow is triggered by tag push (that was generated with npm version). This is fragile under the "two repo" regime (appoptics/solarwinds) and requires more developer involvement.
Change
Workflow is triggered manually.
User is required to type the version being released as it is listed package.json to avoid "accidental clicking".
Before running workflow will check that:
User input of version is valid and matches what is in package.json
Version being released is a full semver or has a -prerelease. preid
Version being released has never been published.
Notes
Since this is a manually triggered workflow pushed for the first time, it is NOT possible to trigger it on the branch before it is merged.
Similar setup used by bindings worked as expected.
Testing on dev repo (excluding last NPM publish step) works as expected.
Prior to the change, using npm version which modifies package.json, and creates a git tag and commit, was required for release. It is now optional to the developer. If modifying pacakge.json by hand, care is due.
Overview
This pull request changes the release workflow so that it is triggered manually.
Status
Current release workflow is triggered by tag push (that was generated with
npm version). This is fragile under the "two repo" regime (appoptics/solarwinds) and requires more developer involvement.Change
package.json-prerelease.preidNotes
npm versionwhich modifiespackage.json, and creates a git tag and commit, was required for release. It is now optional to the developer. If modifyingpacakge.jsonby hand, care is due.