Update to powsybl-core v5.3.2 #130
Merged
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
rolnico
added
PR: waiting-for-review
dependencies
Update to groovy v3.0.15 Update to guava v32.0.1-jre Signed-off-by: Nicolas Rol <[email protected]>
rolnico
force-pushed
the
NRO/upgrade_powsybl_core_5.3.2
branch
from
c95f26a to
35b215a
Compare
marifunf
approved these changes
Jul 18, 2023
capyq
approved these changes
Jul 18, 2023
Signed-off-by: Nicolas Rol <[email protected]>
|
Kudos, SonarCloud Quality Gate passed! |
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
What kind of change does this PR introduce?
Update to powsybl-core v5.3.2
Update to groovy v3.0.15
Update to guava v32.0.1-jre
Update to junit v4.13.1
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
Other information: