Use explicit version numbers for current rotary (workaround for #102)#103
Merged
Use explicit version numbers for current rotary (workaround for #102)#103
Conversation
Signed-off-by: Jose Luis Rivero <jrivero@honurobotics.com>
azeey
approved these changes
Mar 10, 2026
azeey
left a comment
azeey
left a comment
There was a problem hiding this comment.
A few of the packages need a version bump. Otherwise, LGTM!
Contributor
Author
arg, get them from main branches but forgot that the PRs are open to update them. Thanks for the fixes. |
Co-authored-by: Addisu Z. Taddese <addisu@openrobotics.org>
This was referenced Mar 10, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Workaround for #102 and gazebo-tooling/release-tools#1456 (comment)