-
Notifications
You must be signed in to change notification settings - Fork 23
fix: bump openjd-rs crate deps to 0.4.0/0.5.2/0.5.2 #335
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
Merged
leongdl
merged 1 commit into
OpenJobDescription:mainline
from
leongdl:chore/bump-openjd-rs-crates-0.5.2
Aug 24, 2026
+12
−12
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
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.
openjd-expr0.3.0->0.4.0is a SemVer-breaking bump for a0.xcrate, and this PR changes no binding source. Two of the mirrored enums inrust-bindings/src/expr/profile.rsfail silently rather than at compile time, so neithercargo buildnor the existing test suite would catch drift here.1.
ExprRevision— silent mislabeling.From<ExprRevision> for PyExprRevision(profile.rs:105-115) has a wildcard arm mapping any unknown upstream variant back toV2026_02, guarded byallow(unreachable_patterns). If0.4.0added a revision and movedExprRevision::CURRENTto it, thenExprProfile()— which resolves toExprRevision::CURRENTat profile.rs:395 — would build a profile on the new revision while therevisiongetter reportsExprRevision.V2026_02, and the PythonExprRevision.CURRENTclassattr (profile.rs:61) would still be pinned to the old variant. The wildcard suppresses the non-exhaustive-match warning, so the build stays green. No test asserts the mapping either:test_equality.py:190only comparesCURRENT == CURRENT, andtest_pickle.py:80only round-trips the literalV2026_02— both pass regardless.__repr__at profile.rs:487-491 has the same wildcard.2.
ExprExtension— import-time panic.PyExprExtension::ALL(profile.rs:152-160) maps overExprExtension::ALLthroughFrom<ExprExtension>, whose body isunreachable!("ExprExtension has no variants in this crate version")(profile.rs:178-183). If0.4.0shipped the firstExprExtensionvariant, this panics — and becauseALLis aclassattr, it fires during module import, not on first use.Worth confirming against the
0.4.0release notes that neither enum gained a variant. If they did not, consider replacing theExprRevisionwildcard with a loud failure — matching howExprValueandTypeCodealready handle this atexpr_value.rs:179andexpr_type.rs:76— so the next bump breaks the build instead of quietly reporting the wrong revision.