-
Notifications
You must be signed in to change notification settings - Fork 4
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
Upgrade to govuk_publishing_components 43.1.1 #1472
Conversation
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.
Thanks for picking this up! One suggestion below.
Aside from that, is there a way we can get CI to fail without the switch to Terser? I'd have more confidence in the PR if we could see CI fail (before merge), and then fix it by switching to Terser, rather than making the changes up front and hoping it'll work.
This is effectively an upgrade to GOV.UK Frontend 5.
6bd381c
to
2dc273a
Compare
We saw this On a more general note, though, that should have failed the PR checks too, no? I imagine both the PR checks and the CI are the same script, running in a very similar set-up. Whilst I can understand a flaky test passing the PR checks and then failing when we merge in, this error here does not strike me as a potentially flaky one. Rather odd, and we're seeing similar stuff in WH (though in that case I think tests are just flaky). |
@lauraghiorghisor-tw that's what I mean - I'd like the PR check to fail, rather than us finding out it's broken only after merge when it's trying to deploy 😅 We could probably add something like |
Seems like that's already running as part of
|
Shall we just merge? @ChrisBAshton 🤔 |
Try a branch deploy of |
This is effectively an upgrade to GOV.UK Frontend 5.
This is another attempt at making the upgrade. We've just reverted in PR #1467.
Current changes include replacing
Uglifier
withTerser
as per the documentation here.