Skip to content

Conversation

FedericoRuzzier
Copy link
Contributor

List of Changes

  • fixing junit tests

Motivation and Context

How Has This Been Tested?

Through junit

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as
    expected)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@FedericoRuzzier FedericoRuzzier requested a review from a team as a code owner October 8, 2025 09:34
@FedericoRuzzier FedericoRuzzier added the bug Something isn't working label Oct 8, 2025
Copy link
Contributor

github-actions bot commented Oct 8, 2025

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

@github-actions github-actions bot added the patch label Oct 8, 2025
Copy link
Contributor

github-actions bot commented Oct 8, 2025

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

Copy link

sonarqubecloud bot commented Oct 8, 2025

Copy link
Contributor

github-actions bot commented Oct 9, 2025

This pull request does not contain a valid label. Please add one of the following labels: [major, minor, patch, patch, skip]

@FedericoRuzzier FedericoRuzzier merged commit 9e9bf8e into main Oct 9, 2025
20 of 22 checks passed
@FedericoRuzzier FedericoRuzzier deleted the fix-junit-tests branch October 9, 2025 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants