-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate Build release #5635
base: main
Are you sure you want to change the base?
Automate Build release #5635
Conversation
📋 StatsFile sizes
Modules
View stats and visualisations on the review app Action run for 0a68ec6 |
cb23382
to
a521965
Compare
fe4ff35
to
3fcd4cc
Compare
c1d9d1e
to
5f01be7
Compare
5f01be7
to
22183ea
Compare
22183ea
to
45dfeb4
Compare
45dfeb4
to
98ef2a4
Compare
98ef2a4
to
1dc1858
Compare
076464b
to
89d5dea
Compare
89d5dea
to
78fcf3a
Compare
78fcf3a
to
d53003d
Compare
a48ad16
to
dd45487
Compare
dd45487
to
46d1b86
Compare
46d1b86
to
c806c93
Compare
c806c93
to
d22f8bf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've left a few pedantic comments, but the only blocking thing is de-async/awaiting the changelog-release-helper.
Otherwise this is looking super!
* @returns {string|null} - Processed semver which we expect to have the format X.Y.Z | ||
*/ | ||
function convertVersionHeadingToSemver(heading) { | ||
const coercedHeading = semver.coerce(heading) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, I looked up the spec for .coerce
'cuz I was wondering what was happening with the heading hashes. What a crazy function! Nice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't it cool! I think it's safe to sue here too if we presume that our headings are always going to follow the same format
|
||
if (!semver.satisfies(newVersion, `<=${correctIncrement}`)) { | ||
throw new Error( | ||
`New version number ${newVersion} is incrementing more than one for its increment type (${incType}). Please provide a version number than only increments by one from the current version. In this case, it's likely that your new version number should be: ${correctIncrement}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love the helpful suggestion here!
> - has [nvm](https://github.com/nvm-sh/nvm) or [`asdf`](https://asdf-vm.com/guide/getting-started.html) | ||
> on their machine to install the correct version of NodeJS and npm | ||
> - has access to Bitwarden to retreive the credentials for publishing on npm | ||
## Build the release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏
Boy howdy, it feels good to read the release docs for this! |
d22f8bf
to
1ff7a14
Compare
Adds a script which: - validates the new version based on the version in the changelog - updates the changelog headings - gneerates release notes from the changelog
1ff7a14
to
0a68ec6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noice!
Change
Adds a 'Build release' github workflow that automates steps 1 to 8 of the previous manual release process. Specifically this workflow:
This PR also updates our docs and our jest config to cover the github workflow scripts folder.
Resolves #5603