Summary
When a new version of cps-ui-kit is published to NPM, a corresponding GitHub release is not created automatically. It must be created manually, which is error-prone, easy to forget, and inconsistent with the automated publish pipeline.
Current Behavior
cps-ui-kit-publish.yml automatically:
- Bumps the version in
projects/cps-ui-kit/package.json
- Commits and pushes the bump to
master
- Builds and publishes the package to the NPM registry
A GitHub release is not created at any point in this process.
Proposed Change
Add a new job (e.g. create-release) to cps-ui-kit-publish.yml that runs after publish succeeds and creates a GitHub release using the bumped version tag. Note we should not necessarily publish a new version after each commit to the master.
Summary
When a new version of
cps-ui-kitis published to NPM, a corresponding GitHub release is not created automatically. It must be created manually, which is error-prone, easy to forget, and inconsistent with the automated publish pipeline.Current Behavior
cps-ui-kit-publish.ymlautomatically:projects/cps-ui-kit/package.jsonmasterA GitHub release is not created at any point in this process.
Proposed Change
Add a new job (e.g.
create-release) tocps-ui-kit-publish.ymlthat runs afterpublishsucceeds and creates a GitHub release using the bumped version tag. Note we should not necessarily publish a new version after each commit to themaster.