docs: mention explicit browser support range #5354
Merged
Conversation
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
JoshuaKGoldberg
commented
May 6, 2025
mark-wiemer
approved these changes
May 11, 2025
|
Do we have an issue to automate testing to ensure Mocha still actually works on these versions? Thumbs-up from me either way, if someone reports an issue we can manually handle it, and I trust you manually tested at least the very oldest versions we report as supported? |
|
@mark-wiemer I think the closest one is your #5253 :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
PR Checklist
status: accepting prsOverview
Goes with the same version support range strategy as #5226 (comment): the major versions of evergreen browsers as of the oldest supported Node.js.