-
Notifications
You must be signed in to change notification settings - Fork 335
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
Open
domoscargin
wants to merge
2
commits into
automate-build-release
Choose a base branch
from
automate-publish-release-to-github
base: automate-build-release
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Automate GitHub Release #5641
domoscargin
wants to merge
2
commits into
automate-build-release
from
automate-publish-release-to-github
+74
−8
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
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 15:43
Inactive
📋 StatsFile sizes
Modules
View stats and visualisations on the review app Action run for f07c25f |
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 15:50
e6a1b6a
to
ee682da
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 15:51
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 15:55
ee682da
to
ddd4e44
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 15:55
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 16:01
ddd4e44
to
00ca872
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 16:02
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 16:04
00ca872
to
1b24a1c
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 16:04
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 16:07
1b24a1c
to
4374074
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 16:07
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 16:52
4374074
to
dcd78a7
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 16:53
Inactive
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 21:26
Inactive
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 21:33
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 21:36
1c66edd
to
db8212d
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 21:37
Inactive
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 21:45
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 21:49
d68b862
to
076bb32
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 21:50
Inactive
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 22:07
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 22:12
8bbd97d
to
c29878a
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 22:13
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 22:22
c29878a
to
548a384
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 22:22
Inactive
Co-authored-by: Brett Kyle <brett.kyle@digital.cabinet-office.gov.uk> Co-authored-by: Owen Jones <owen.jones@digital.cabinet-office.gov.uk>
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 22:29
548a384
to
b84b2e4
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-5641
January 22, 2025 22:29
Inactive
domoscargin
force-pushed
the
automate-publish-release-to-github
branch
from
January 22, 2025 22:38
b84b2e4
to
f07c25f
Compare
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.
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.