Revise "Addition of browsers" data guideline - #27213
Merged
Merged
Conversation
This adds some details that reflects contemporary considerations, especially the increasing automation of BCD browser and support data.
ddbeck
force-pushed
the
addition-guideline-updates
branch
from
July 1, 2025 09:46
19affee to
6bf13e4
Compare
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
Co-authored-by: Florian Scholz <fs@florianscholz.com>
caugner
approved these changes
Jul 8, 2025
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
queengooborg
approved these changes
Jul 22, 2025
queengooborg
left a comment
Contributor
There was a problem hiding this comment.
This matches our requirements nowadays, so LGTM!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This adds some details that reflects contemporary considerations, especially the increasing automation of browser and support data.
Test results and supporting details
This came up in today's BCD call in regards to how or whether Bun qualifies for inclusion. The current guideline doesn't really reflect, for example, how we scrape release information or rely on the collector for accuracy.
Related issues