Align release process with that of GOV.UK Frontend #695
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- add extra details to the steps - makes process more in line with our other repos
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Following this morning's release, I've tried to update the release process to bring it even closer to how we release GOV.UK Frontend.
The steps were already following a very similar process. The main technical change is that instead of having the commit and tag generated by
npm version, like it was in the current process, it is now handled manually (similarly to how the release scripts of GOV.UK Frontend commit the version change and create a tag).I've also updated the draft for the comms to match what we did in the latest release.