Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump powsybl-core to 4.3.1 #335

Merged
merged 1 commit into from
Jul 16, 2021
Merged

Bump powsybl-core to 4.3.1 #335

merged 1 commit into from
Jul 16, 2021

Conversation

flo-dup
Copy link
Contributor

@flo-dup flo-dup commented Jul 16, 2021

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem ?
No

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
powsybl-core update

What is the current behavior? (You can also link to an open issue here)
powsybl-core 4.3.0-RC1

What is the new behavior (if this is a feature change)?
powsybl-core 4.3.1

Does this PR introduce a breaking change or deprecate an API?
No

@flo-dup flo-dup force-pushed the update_powsybl_core_4.3.1 branch from 4e1e138 to 6116912 Compare July 16, 2021 13:12
Signed-off-by: Florian Dupuy <florian.dupuy@rte-france.com>
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@flo-dup flo-dup merged commit 53e193f into master Jul 16, 2021
@flo-dup flo-dup deleted the update_powsybl_core_4.3.1 branch July 16, 2021 13:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant