Skip to content
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

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

lauraghiorghisor-tw
Copy link
Contributor

@lauraghiorghisor-tw lauraghiorghisor-tw commented Sep 18, 2024

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 with Terser as per the documentation here.

⚠️ This repo is Continuously Deployed: make sure you follow the guidance ⚠️

Copy link
Contributor

@ChrisBAshton ChrisBAshton left a 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.

config/environments/production.rb Outdated Show resolved Hide resolved
This is effectively an upgrade to GOV.UK Frontend 5.
@lauraghiorghisor-tw
Copy link
Contributor Author

lauraghiorghisor-tw commented Sep 19, 2024

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.

We saw this Uglifier::Error in the failure here.

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).

@ChrisBAshton
Copy link
Contributor

@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 rails assets:precompile to https://github.com/alphagov/contacts-admin/blob/main/.github/workflows/rspec.yml 🙏

@lauraghiorghisor-tw
Copy link
Contributor Author

@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 rails assets:precompile to https://github.com/alphagov/contacts-admin/blob/main/.github/workflows/rspec.yml 🙏

Seems like that's already running as part of rspec.yml. See

- name: Precompile assets

@lauraghiorghisor-tw
Copy link
Contributor Author

Shall we just merge? @ChrisBAshton 🤔

@ChrisBAshton
Copy link
Contributor

Try a branch deploy of upgrade-to-frontend-5 first maybe? But yes, good to go 👍

@lauraghiorghisor-tw lauraghiorghisor-tw merged commit b9eb513 into main Sep 19, 2024
10 checks passed
@lauraghiorghisor-tw lauraghiorghisor-tw deleted the upgrade-to-frontend-5 branch September 19, 2024 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants