feat: compatibility with ruby 3.2 #299
Open
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
jhonasiv
approved these changes
Nov 11, 2024
The protection is meant to avoid usage of core objects (plan, interface), outside the Roby execution thread. It is always disabled in tests because of interaction with equality (assert_equal, flexmock, ...). It is also disabled by default because of the performance impact.
wvmcastro
approved these changes
Dec 2, 2024
jhonasiv
approved these changes
Dec 2, 2024
It breaks it in some ways when loading the gemspec files
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.
The main change is that ruby > 3.0 will have to use the v2 interface. I don't want to backport keyword argument support on the v1 interface.
This implements as well the abiltiy to use the v2 interface for the cucumber support.