chore: further automate release process #235
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
We use
np
to orchestrate the publication of a module to NPM. One of the stepsnp
performs is a commit to editpackage.json
'sversion
.As we have branch protection enabled for
main
, we have to raise a PR to get this commit in. Automate this process in the release script as it's pretty boring!This change checks one has the GitHub CLI installed and raises a PR if it can.
Related https://github.com/guardian/cdk/pull/229/files#r570193715
This is still a stop gap until we have semantic-release or similar in the project.
Does this change require changes to existing projects or CDK CLI?
No.
How to test
Create a release?
How can we measure success?
More automation = less thinking = fewer mistakes!
Have we considered potential risks?
n/a