chore(deps): update dependency @lhci/cli to v0.15.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@lhci/cli	0.14.0 → 0.15.1

---

Release Notes

GoogleChrome/lighthouse-ci (@​lhci/cli)

v0.15.1

Compare Source

What's Changed

• fix: use viewer origin as string instead of object by @​akhilbv in #​1109

New Contributors

• @​akhilbv made their first contribution in #​1109

Full Changelog: GoogleChrome/lighthouse-ci@v0.15.0...v0.15.1

v0.15.0

Compare Source

• feat: upgrade to lighthouse 12.6.1 (#​1103) (6b3b50e), closes #​1103
• feat(cli): change wizard default branch to main (#​1069) (d04aba1), closes #​1069
• feat(server): configure viewer origin from args (#​1004) (f6f80cb), closes #​1004
• fix(cli): improve filename sanitization for hash routes (#​1084) (e83b2f6), closes #​1084
• fix(cli): don't mutate collect.settings (#​1068) (55ae4a5), closes #​1068
• fix(cli): assert - destructure lhr from options (#​1062) (2cb0d07), closes #​1062
• fix(cli): respect collect puppeteerLaunchOptions.headless (#​1051) (03eff8f), closes #​1051
• docs: added actions-lighthouseci-compare (#​1054) (de45968), closes #​1054
• docs: update link to default lighthouse config (#​1091) (c200e07), closes #​1091
• docs: update GitHub Actions versions in README.md (#​1086) (3cac9eb), closes #​1086
• chore: update docker images with latest version (5e7be65)
• chore: bump lhci references to 0.14 (#​1050) (82b272c), closes #​1050
• chore: update versions in heroku-server recipe (#​1078) (ef83477), closes #​1078
• chore: Heroku Postgres Hobby plan doesn't exist anymore (#​1077) (115818a), closes #​1077
• chore: update versions in ci (#​1104) (912d985), closes #​1104
• misc(release): set npm tag correctly (6914f5b)
• misc(release): fix lint issues in changelog script (d1dcd9a)
• Fixed typo in documentation (#​1100) (7779db1), closes #​1100

BREAKING CHANGE

• upgrade to lighthouse 12.6.1

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm csp_evaluator is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: frontend/package-lock.json → npm/@lhci/cli@0.15.1 → npm/csp_evaluator@1.1.5 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/csp_evaluator@1.1.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm csp_evaluator is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: frontend/package-lock.json → npm/@lhci/cli@0.15.1 → npm/csp_evaluator@1.1.5 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/csp_evaluator@1.1.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm puppeteer-core is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: frontend/package-lock.json → npm/@lhci/cli@0.15.1 → npm/puppeteer-core@24.43.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/puppeteer-core@24.43.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​lhci/​cli@​0.14.0 ⏵ 0.15.1	+1		+1

View full report