-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Compare API compatibility against both 4.0 and 4.1 #80354
Conversation
fe87615
to
9fa98b2
Compare
This approach seems good to me! |
9fa98b2
to
7af89d3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Needs a rebase.
7af89d3
to
97dc955
Compare
97dc955
to
4dfff3e
Compare
Validate extension JSON: API was removed: classes/GLTFDocumentExtensionPhysics | ||
Validate extension JSON: API was removed: classes/GLTFDocumentExtensionTextureWebP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two entries are new, but they are mentioned in this PR as being removed from the export, so this is correct and exactly the kind of thing that could slip through before this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have hidden warnings from prior versions (as I originally intended), as it is kinda unavoidable that they happen (unless editing the expected files for old versions). (tho thinking about it there may still be some issues when changing a value in multiple versions, potentially still requiring changes to old expected files)
4dfff3e
to
b83dff7
Compare
Thanks! |
Allows running the API compat checks against multiple Godot versions without having to duplicate a bunch of entries by using a scheme were, if the basename of an expected file contains an
_
it will be compared against the version indicated by the part before the_
but the expected errors will be concatenated to those of the version after the underscore (possibly recursively).This changes prevents accidentally breaking APIs that there newly added in 4.1.