fix(schema): add ROS 2 core22 extensions for remote-build #4756
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
|
The failing test is google:ubuntu-24.04-64:tests/spread/core-devel/basic, unrelated to this PR. |
mr-cal
approved these changes
Apr 29, 2024
|
Hello, any news on this? |
Hey @Guillaumebeuzeboc, sorry for the delay. I'll ping @cmatsuoka for a review. |
cmatsuoka
approved these changes
Jun 5, 2024
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.
tox run -m lint?tox run -e test-py310? (supported versions:py39,py310,py311,py312)Adds ROS 2 core22 extensions in the legacy schema for remote-build.
Referring to this commit: f509ac0
Remote-building always uses legacy and use the legacy schema to validate.