Include patch number in Rhino data #1731
Merged
Conversation
This file contains 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
ljharb
approved these changes
Jun 12, 2021
chicoxyzzy
approved these changes
Jun 15, 2021
JLHwung
pushed a commit
to JLHwung/compat-table
that referenced
this pull request
Mar 30, 2023
* Specify patch version for rhino * Build changes in rhino patch version
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.
Although previously we had used
rhino1_7to describe its compatibility, Rhino hasn't bumped a minor version in over a decade and all the changes happen on1.7.x. Accordingly, I think it might be best to include that in the data, particularly because I expect a new version under 1.7 will come out soon with higher ES6 compatibility.