-
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 GitHub Release #5641
base: automate-build-release
Are you sure you want to change the base?
Automate GitHub Release #5641
Conversation
📋 StatsFile sizes
Modules
View stats and visualisations on the review app Action run for 6e45dfa |
e6a1b6a
to
ee682da
Compare
ee682da
to
ddd4e44
Compare
ddd4e44
to
00ca872
Compare
00ca872
to
1b24a1c
Compare
1b24a1c
to
4374074
Compare
4374074
to
dcd78a7
Compare
1c66edd
to
db8212d
Compare
d68b862
to
076bb32
Compare
8bbd97d
to
c29878a
Compare
c29878a
to
548a384
Compare
548a384
to
b84b2e4
Compare
b84b2e4
to
f07c25f
Compare
dd45487
to
46d1b86
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
46d1b86
to
c806c93
Compare
#5635 has been updated so this just needs a rebase and then we can review properly. |
f07c25f
to
6e45dfa
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.
One non-blocking comment. I don't have anything to add, this looks grand to me!
I don't know if we want to merge now or wait for #5635 to be mergable and then merge this into main
. Up to you.
docs/releasing/publishing.md
Outdated
4. Add release notes from [`CHANGELOG.md`](/CHANGELOG.md) | ||
5. Attach as release binary the ZIP file that has been generated at the root of this project during the npm publishing phase | ||
6. Publish release | ||
1. Open the ["RELEASE: Publish to GitHub" workflow](https://github.com/alphagov/govuk-frontend/actions/workflows/publish-release-to-github.yaml) and run the workflow on the `main` branch. This will generate a GitHub tag and release. If the workflow fails after creating a tag, or after creating a release, you'll need to manually delete these via the GitHub UI before running the workflow again. |
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.
Worth linking to the tags UI for ease?
1. Open the ["RELEASE: Publish to GitHub" workflow](https://github.com/alphagov/govuk-frontend/actions/workflows/publish-release-to-github.yaml) and run the workflow on the `main` branch. This will generate a GitHub tag and release. If the workflow fails after creating a tag, or after creating a release, you'll need to manually delete these via the GitHub UI before running the workflow again. | |
1. Open the ["RELEASE: Publish to GitHub" workflow](https://github.com/alphagov/govuk-frontend/actions/workflows/publish-release-to-github.yaml) and run the workflow on the `main` branch. This will generate a GitHub tag and release. If the workflow fails after creating a tag, or after creating a release, you'll need to manually delete these via [the GitHub tags UI](https://github.com/alphagov/govuk-frontend/tags) before running the workflow again. |
c806c93
to
d22f8bf
Compare
Co-authored-by: Brett Kyle <[email protected]> Co-authored-by: Owen Jones <[email protected]>
6e45dfa
to
8457687
Compare
1ff7a14
to
0a68ec6
Compare
What
resolves #5608
Automates our GitHub releases through a
workflow_dispatch
GitHub Actions workflow.The workflow creates a GitHub tag for the version in the package.json file. It also creates a zip file, and generates release notes from the CHANGELOG, before creating a release.
If the tag or the release already exist, the job will fail, and these will need to be manually deleted via the UI.
Notes
It's possible to skip the tag creation step, since
gh release
automatically creates a tag for the release if it doesn't exist. This PR keeps this step so that the tags/release are fully consistent with every previous release tag on the repo.