Bump govuk-frontend from 4.7.0 to 4.10.0

[dependabot]

Bumps govuk-frontend from 4.7.0 to 4.10.0.

Release notes

Sourced from govuk-frontend's releases.

GOV.UK Frontend v4.10.0

We do not plan to make any further updates to GOV.UK Frontend v4. Consider upgrading to GOV.UK Frontend v5 to get the latest changes.

To install this version with npm, run npm install govuk-frontend@4.10.0. You can also find more information about how to stay up to date in our documentation.

New features

Prepare to use the refreshed GOV.UK brand

We’ve added features from the latest version of GOV.UK Frontend to help more services implement GOV.UK’s refreshed brand. Ahead of the brand’s go-live date of 25 June 2025, you should prepare your service by updating its code. You’ll then need to deploy the changes to production on 25 June 2025 or as soon after this date as possible.

The changes affect these components:

• GOV.UK header
• GOV.UK footer
• Cookie banner

The changes also affect the theme-color metadata and updated assets, including:

• icons
• Open Graph image
• manifest.json

To help you get ready, we've published this release, which includes several features to make the necessary updates across your service:

• updated markup for the GOV.UK header component (with the refreshed logo) and GOV.UK footer component (adding the crown logo)
• a new govuk-template--rebranded HTML class to apply updated styles from our CSS
• a new set of assets for icons, Open Graph image and page metadata

You’ll need to serve the new assets in your service. After that, what you’ll need to do depends on the code in your service and if you use GOV.UK Frontend:

• with its Nunjucks page template and macros
• with its Nunjucks macros (without the page template)
• without using Nunjucks

Add the brand refresh assets to your project

GOV.UK Frontend provides updated assets for the icons, Open Graph image and manifest.json to reflect the refreshed brand. These assets are available in the dist/govuk/assets/rebrand folder of the package.

Additionally, for the brand refresh, we’ve changed the names, formats and sizes of icon assets we distribute in Frontend.

Check that you’ve copied the following files from the /assets/rebrand/ directory to the correct place and are serving them at the correct URLs:

• manifest.json
• images/favicon.ico
• images/favicon.svg
• images/govuk-icon-180.png
• images/govuk-icon-192.png
• images/govuk-icon-512.png
• images/govuk-icon-mask.svg

... (truncated)

Changelog

Sourced from govuk-frontend's changelog.

v4.10.0 (Feature release)

We do not plan to make any further updates to GOV.UK Frontend v4. Consider upgrading to GOV.UK Frontend v5 to get the latest changes.

To install this version with npm, run npm install govuk-frontend@4.10.0. You can also find more information about how to stay up to date in our documentation.

New features

Prepare to use the refreshed GOV.UK brand

We’ve added features from the latest version of GOV.UK Frontend to help more services implement GOV.UK’s refreshed brand. Ahead of the brand’s go-live date of 25 June 2025, you should prepare your service by updating its code. You’ll then need to deploy the changes to production on 25 June 2025 or as soon after this date as possible.

The changes affect these components:

• GOV.UK header
• GOV.UK footer
• Cookie banner

The changes also affect the theme-color metadata and updated assets, including:

• icons
• Open Graph image
• manifest.json

To help you get ready, we've published this release, which includes several features to make the necessary updates across your service:

• updated markup for the GOV.UK header component (with the refreshed logo) and GOV.UK footer component (adding the crown logo)
• a new govuk-template--rebranded HTML class to apply updated styles from our CSS
• a new set of assets for icons, Open Graph image and page metadata

You’ll need to serve the new assets in your service. After that, what you’ll need to do depends on the code in your service and if you use GOV.UK Frontend:

• with its Nunjucks page template and macros
• with its Nunjucks macros (without the page template)
• without using Nunjucks

Add the brand refresh assets to your project

GOV.UK Frontend provides updated assets for the icons, Open Graph image and manifest.json to reflect the refreshed brand. These assets are available in the dist/govuk/assets/rebrand folder of the package.

Additionally, for the brand refresh, we’ve changed the names, formats and sizes of icon assets we distribute in Frontend.

Check that you’ve copied the following files from the /assets/rebrand/ directory to the correct place and are serving them at the correct URLs:

• manifest.json
• images/favicon.ico
• images/favicon.svg
• images/govuk-icon-180.png
• images/govuk-icon-192.png
• images/govuk-icon-512.png

... (truncated)

Commits

• 7b2ad65 Merge pull request #5992 from alphagov/release-4.10.0
• 7551145 Fix missed list in cangelog
• 745b45f Release v4.10.0
• 0928bd5 Merge pull request #5989 from alphagov/4.10.0-changelog
• 37b1139 Update changelog for 4.10.0
• dcef400 Merge pull request #5984 from alphagov/backport-nunjucks-shortcut
• a8e232b Remove unnecessary htmlClasses set in generic template
• 11bb259 Apply govukRebrand global to header and footer
• 71bca54 Swap out new and old icon and meta markup based on rebrand flag
• 09f1b33 Add support in renderTemplate for applying template variables via set
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
govuk-frontend	[>= 5.a, < 6]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #1127.