Skip to content

Conversation

@rolnico
Copy link
Member

@rolnico rolnico commented Dec 16, 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?

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:

Signed-off-by: Nicolas Rol <[email protected]>
@rolnico rolnico self-assigned this Dec 16, 2025
Signed-off-by: Nicolas Rol <[email protected]>
@sonarqubecloud
Copy link

@rolnico rolnico merged commit 2f3300f into main Dec 16, 2025
7 checks passed
@rolnico rolnico deleted the tmp_prepare_release branch December 16, 2025 10: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.

3 participants