Skip to content

devops: Lighthouse budget assertions are all "warn" — can never fail a PR #304

Description

@Austinaminu2

Problem

`.github/lighthouse-budget.json` sets every assertion category (`performance`, `accessibility`, `best-practices`, `seo`) to `"warn"`, never `"error"`.

Location

`.github/lighthouse-budget.json`

Impact

The Lighthouse workflow is purely advisory no matter how badly scores regress — it can never actually block a PR from merging.

Suggested fix

Change budget assertions from `"warn"` to `"error"` for the categories that should actually gate merges (at minimum performance and accessibility).

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave programdevopsCI/CD and infrastructure

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions