You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do a feature release of GOV.UK Frontend before we start work on v4.
Why
We were notified about a high priority issue with the panel component just after releasing 3.13.1. We don't want to wait until v4.0.0 to release this fix. We've also worked on a few new features since 3.13.1 too, so we can release them at the same time.
Further detail
We're using this release as an opportunity to test releasing changes from a support branch (e.g: support/3.x). This is to give us the confidence when working on breaking releases that we can still publish urgent fix releases even if we've merged changes into main.
This will have an impact on how we do this release. We will be following these draft release steps. Because the changes are already merged into main, we essentially need to duplicate those changes into new PRs against the support/3.x branch. In a more realistic scenario, we'd have made the changes against the support branch first, and then copied them onto main afterwards.
What
Do a feature release of GOV.UK Frontend before we start work on v4.
Why
We were notified about a high priority issue with the panel component just after releasing 3.13.1. We don't want to wait until v4.0.0 to release this fix. We've also worked on a few new features since 3.13.1 too, so we can release them at the same time.
Further detail
We're using this release as an opportunity to test releasing changes from a support branch (e.g:
support/3.x
). This is to give us the confidence when working on breaking releases that we can still publish urgent fix releases even if we've merged changes intomain
.This will have an impact on how we do this release. We will be following these draft release steps. Because the changes are already merged into
main
, we essentially need to duplicate those changes into new PRs against thesupport/3.x
branch. In a more realistic scenario, we'd have made the changes against the support branch first, and then copied them ontomain
afterwards.Support branch PRs
text-align
override classes #2368govuk-spacing
to output negative spacing #2367Who needs to know about this
Developers, Content Design, Tech Writer
Done when
The text was updated successfully, but these errors were encountered: