Force backtrace version that is compatible with 1.75 #481
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
Signed-off-by: Michael X. Grey <[email protected]>
jhdcs
reviewed
May 14, 2025
Collaborator
jhdcs
left a comment
jhdcs
left a comment
There was a problem hiding this comment.
Seems a simple enough change, and CI is passing. Thank you!
maspe36
approved these changes
May 14, 2025
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.
A recent version bump in
backtraceis no longer compatible with Rust version 1.75, despite being a patch increase.This PR forces a fixed version for several examples that have a transitive dependency on
backtraceto keep it compatible with Rust 1.75. This should fix CI failures that recently started happening.