Update package.json to 3.14.0 #2378
Merged
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
We released 3.14.0 from the support/3.x branch. We now need to make sure `main` is in sync and includes all of the changes that were released in 3.14.0. The release notes were updated in a separate PR: #2369 The changes themselves were already merged into `main` as we were trialling the support branch release process in a slightly artificial scenario and we decided to do this only after the changes were already in `main`. That therefore leaves updating the package/package.json file so it's in sync with the latest release version
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-2378
lfdebrux
approved these changes
Oct 4, 2021
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.
We released 3.14.0 from the support/3.x branch. We now need to make sure
mainis in sync and includes all of the changes that were released in 3.14.0.The release notes were updated in a separate PR: #2369
The changes themselves were already merged into
mainas we were trialling the support branch release process in a slightly artificial scenario and we decided to do this only after the changes were already inmain.That therefore leaves updating the package/package.json file so it's in sync with the latest release version - this is done in this PR