Bump YARP version to 3.8.100 #3054
Closed
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
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would update the release notes by adding a file in |
|
Not necessary anymore as now YARP 3.9.0 was released: https://github.com/robotology/yarp/releases/tag/v3.9.0 . |
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 current
masterof YARP (used in the CI of the robotology-superbuild to catch errors as early as possible) contains a breaking change introduced in a29c6b2 . We can easily handle this in downstream libraries, but to avoid a tight coupling between the YARP version and the version of downstream libraries, we would need some way to know which version of YARP contains this change. While we wait for YARP 3.9.0, an easy fix for this is to bump the version of YARP to 3.8.100, that is a simple way to mark development builds.