Update dependency @govuk-prototype-kit/common-templates to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@govuk-prototype-kit/common-templates	2.0.1 → 3.0.0

---

Release Notes

alphagov/govuk-prototype-kit-common-templates (@​govuk-prototype-kit/common-templates)

v3.0.0

Compare Source

Breaking changes

• #​33 - Support GOV.UK Frontend 6.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: undefined@undefined
npm error Found: govuk-frontend@5.14.0
npm error node_modules/govuk-frontend
npm error   govuk-frontend@"5.14.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer govuk-frontend@">=6.0.0" from @govuk-prototype-kit/common-templates@3.0.0
npm error node_modules/@govuk-prototype-kit/common-templates
npm error   @govuk-prototype-kit/common-templates@"3.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-06-11T09_12_06_467Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-11T09_12_06_467Z-debug-0.log

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud