Skip to content

Conversation

@geofjamg
Copy link
Member

@geofjamg geofjamg commented Nov 21, 2025

Please check if the PR fulfills these requirements

  • 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)
  • A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?

No

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

Contingency list are in com.powsybl.contingency.contingency.list package.

What is the new behavior (if this is a feature change)?
Contingency list are in com.powsybl.contingency.list package.

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

  • Yes
  • No

If yes, please check if the following requirements are fulfilled

  • The Breaking Change or Deprecated label has been added
  • The migration steps are described in the following section

https://github.com/powsybl/powsybl-core/wiki/Migration-guide-v7.1.0#contingency

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

Signed-off-by: Geoffroy Jamgotchian <[email protected]>
@geofjamg geofjamg added the Breaking Change API is broken label Nov 21, 2025
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Breaking Change API is broken

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants