Skip to content

Revert "Release v2.30.0 (#150)"#151

Merged
SlimaneAmar merged 1 commit intomainfrom
revert_pom_2.30
Feb 3, 2026
Merged

Revert "Release v2.30.0 (#150)"#151
SlimaneAmar merged 1 commit intomainfrom
revert_pom_2.30

Conversation

@SlimaneAmar
Copy link
Collaborator

This reverts commit 223ea87.

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?

What kind of change does this PR introduce?

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?

  • 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

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

Other information:

This reverts commit 223ea87.

Signed-off-by: Slimane AMAR <slimane.amar_externe@rte-france.com>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 3, 2026

@SlimaneAmar SlimaneAmar merged commit 495a337 into main Feb 3, 2026
4 checks passed
@SlimaneAmar SlimaneAmar deleted the revert_pom_2.30 branch February 3, 2026 15:45
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.

2 participants