GoogleChrome / GoogleChrome/lighthouse

Document breaking change policy

Open
#12,719 2 comments 0 reactions 0 assignees View on GitHub
docs P3
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 14h
Merged PRs (30d)
20

Description

ex: we will not change scoring for performance or accessibility w/o a major version bump, but will for best practices. what about other categories?

Contributor guide

Open the contributing guide

Research direction

Start by locating the current documented breaking-change policy and reviewing how scoring categories are handled. Define which categories require a major version bump and which may change without one, including the unresolved “other categories” question. Done means the policy clearly covers all relevant categories and versioning expectations.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.