From bdf10575315af38ec48a68e8c10a16616894d60b Mon Sep 17 00:00:00 2001 From: Bappa Mandal Date: Sat, 27 Jun 2026 07:26:34 +0530 Subject: [PATCH] Make Lighthouse CI warning based --- docs/lighthouse-codeql.md | 4 ++-- lighthouserc.cjs | 1 - 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/lighthouse-codeql.md b/docs/lighthouse-codeql.md index 8a59203..0a57290 100644 --- a/docs/lighthouse-codeql.md +++ b/docs/lighthouse-codeql.md @@ -10,7 +10,7 @@ Lighthouse CI runs a real browser audit against: https://gigworlds.net ``` -It checks performance, accessibility, best practices, and SEO signals. The current workflow is intentionally warning-based because it audits a live external website. Live network, hosting, CDN, and third-party script variance can change scores between runs. +It checks performance, accessibility, best practices, and SEO signals. The current workflow is intentionally warning-based because it audits a live external website. Live network, hosting, CDN, third-party script variance, and existing production issues can change scores between runs. Run locally: @@ -34,7 +34,7 @@ The GitHub workflow runs: - Weekly on Monday. - When Lighthouse configuration changes on `main`. -When the target site and budgets are stable, warning thresholds can be changed to failing assertions. +When the target site and budgets are stable, warning thresholds can be changed to failing assertions. Until then, the workflow should stay green while still uploading reports and printing actionable warnings. ## CodeQL diff --git a/lighthouserc.cjs b/lighthouserc.cjs index cb7cdd7..7da58d8 100644 --- a/lighthouserc.cjs +++ b/lighthouserc.cjs @@ -9,7 +9,6 @@ module.exports = { } }, assert: { - preset: "lighthouse:recommended", assertions: { "categories:performance": ["warn", { minScore: 0.5 }], "categories:accessibility": ["warn", { minScore: 0.8 }],