Skip to content

Bump the test-dependencies group across 1 directory with 2 updates#206

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/maven/test-dependencies-4ac7b52158
Open

Bump the test-dependencies group across 1 directory with 2 updates#206
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/maven/test-dependencies-4ac7b52158

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 2, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps the test-dependencies group with 2 updates in the / directory: org.junit.jupiter:junit-jupiter-api and org.junit.jupiter:junit-jupiter-engine.

Updates org.junit.jupiter:junit-jupiter-api from 5.11.4 to 6.1.0

Release notes

Sourced from org.junit.jupiter:junit-jupiter-api's releases.

JUnit 6.1.0 = Platform 6.1.0 + Jupiter 6.1.0 + Vintage 6.1.0

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.0.3...r6.1.0

JUnit 6.1.0-RC1 = Platform 6.1.0-RC1 + Jupiter 6.1.0-RC1 + Vintage 6.1.0-RC1

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.1.0-M1...r6.1.0-RC1

JUnit 6.1.0-M1 = Platform 6.1.0-M1 + Jupiter 6.1.0-M1 + Vintage 6.1.0-M1

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.0.0...r6.1.0-M1

JUnit 6.0.3 = Platform 6.0.3 + Jupiter 6.0.3 + Vintage 6.0.3

See Release Notes.

Full Changelog: junit-team/junit-framework@r6.0.2...r6.0.3

JUnit 6.0.2 = Platform 6.0.2 + Jupiter 6.0.2 + Vintage 6.0.2

See Release Notes.

... (truncated)

Commits

Updates org.junit.jupiter:junit-jupiter-engine from 5.11.4 to 6.1.0

Release notes

Sourced from org.junit.jupiter:junit-jupiter-engine's releases.

JUnit 6.1.0 = Platform 6.1.0 + Jupiter 6.1.0 + Vintage 6.1.0

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.0.3...r6.1.0

JUnit 6.1.0-RC1 = Platform 6.1.0-RC1 + Jupiter 6.1.0-RC1 + Vintage 6.1.0-RC1

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.1.0-M1...r6.1.0-RC1

JUnit 6.1.0-M1 = Platform 6.1.0-M1 + Jupiter 6.1.0-M1 + Vintage 6.1.0-M1

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.0.0...r6.1.0-M1

JUnit 6.0.3 = Platform 6.0.3 + Jupiter 6.0.3 + Vintage 6.0.3

See Release Notes.

Full Changelog: junit-team/junit-framework@r6.0.2...r6.0.3

JUnit 6.0.2 = Platform 6.0.2 + Jupiter 6.0.2 + Vintage 6.0.2

See Release Notes.

... (truncated)

Commits

Updates org.junit.jupiter:junit-jupiter-engine from 5.11.4 to 6.1.0

Release notes

Sourced from org.junit.jupiter:junit-jupiter-engine's releases.

JUnit 6.1.0 = Platform 6.1.0 + Jupiter 6.1.0 + Vintage 6.1.0

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.0.3...r6.1.0

JUnit 6.1.0-RC1 = Platform 6.1.0-RC1 + Jupiter 6.1.0-RC1 + Vintage 6.1.0-RC1

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.1.0-M1...r6.1.0-RC1

JUnit 6.1.0-M1 = Platform 6.1.0-M1 + Jupiter 6.1.0-M1 + Vintage 6.1.0-M1

See Release Notes.

New Contributors

Full Changelog: junit-team/junit-framework@r6.0.0...r6.1.0-M1

JUnit 6.0.3 = Platform 6.0.3 + Jupiter 6.0.3 + Vintage 6.0.3

See Release Notes.

Full Changelog: junit-team/junit-framework@r6.0.2...r6.0.3

JUnit 6.0.2 = Platform 6.0.2 + Jupiter 6.0.2 + Vintage 6.0.2

See Release Notes.

... (truncated)

Commits

@dependabot @github

dependabot Bot commented on behalf of github Jun 2, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot added the automated label Jun 2, 2026
@dependabot dependabot Bot requested a review from sfloess as a code owner June 2, 2026 06:09
@dependabot dependabot Bot added the automated label Jun 2, 2026
@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

PR Validation Results

✅ Code Coverage

Coverage report generated. Download artifacts to view details.

Quality Checks

  • ✅ Compilation successful
  • ✅ All tests passed
  • ✅ Code coverage meets requirements
  • ✅ SpotBugs analysis passed
  • ✅ PMD analysis passed
  • ✅ Checkstyle passed
  • ✅ JavaDoc generation successful

Note: Full build artifacts are available for download.

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

📊 Quality Gate Report

Tool Status Metrics
🧪 JaCoCo ✅ Instruction: 98%, Branch: 98%
🐛 SpotBugs ✅ 0 bugs found
📝 PMD ✅ 0 violations
✓ Checkstyle ✅ 0 errors
🔒 OWASP ✅ 0 vulnerabilities (0 critical, 0 high)

✅ All quality gates passed!

📋 View detailed reports

Download the quality-reports artifact from this workflow run for detailed analysis.

  • JaCoCo: target/site/jacoco/index.html
  • SpotBugs: target/spotbugsXml.xml
  • PMD: target/pmd.xml
  • Checkstyle: target/checkstyle-result.xml
  • OWASP: target/dependency-check-report.xml

@sfloess

sfloess commented Jun 7, 2026

Copy link
Copy Markdown
Member

🤖 AUTONOMOUS PR REVIEW

Quality Score: 57/100
AI Consensus: request_changes (42% agreement)
Impact Risk: critical
Auto-Decision: REJECT

Decision Reasoning

Breaking changes detected: JUnit Jupiter 6.1.0, Mockito 5.23.0 compatibility, Maven Surefire Plugin 3.x

Impact Analysis

  • Breaking Changes: 3
    • ⚠️ JUnit Jupiter 6.1.0: JUnit 6.x requires Java 17 minimum (already met by project). However, JUnit 6.x introduces breaking changes: unified versioning across Platform/Jupiter/Vintage, CSV parsing migration from univocity-parsers to FastCSV (lineSeparator attribute removed from @CsvFileSource), deprecation of junit-jupiter-migrationsupport module, and Constants class moved from org.junit.jupiter.engine.Constants to org.junit.jupiter.api.Constants.
    • ⚠️ Mockito 5.23.0 compatibility: Mockito 5.x series compatibility with JUnit 6.x is uncertain. Community has raised concerns about whether Mockito is compatible with JUnit 6, with potential issues reported. Mockito 5.x was designed for JUnit 5, and JUnit 6 compatibility is not guaranteed. This could cause test execution failures or require Mockito upgrade.
    • ⚠️ Maven Surefire Plugin 3.x: JUnit 6.x requires Maven Surefire/Failsafe 3.x minimum. Current project uses maven-surefire-plugin 3.5.5, which meets the requirement, but older Surefire 2.x versions are no longer supported by JUnit 6.
  • High-Risk Changes: 4
  • Files Impacted: 23
  • Missing Tests: 0

AI Reviews (3 models)

opus - request_changes (40/100, 90% confidence)

  • Issues: 5 (1 critical)
    • critical: Major version bump from JUnit Jupiter 5.x to 6.x is a breaking change. JUnit 6 is a new major version with breaking API changes including: unified versioning across Platform/Jupiter/Vintage (no more separate version tracks), CSV parsing migration from univocity-parsers to FastCSV (lineSeparator attribute removed from @CsvFileSource), deprecation of junit-jupiter-migrationsupport module, and Constants class relocation from org.junit.jupiter.engine.Constants to org.junit.jupiter.api.Constants. While the current test suite happens to pass, this is a major dependency upgrade that deserves careful evaluation and explicit acceptance, not an auto-merge from Dependabot.
    • high: Dependency version mismatch between JUnit Jupiter and Mockito. The project declares junit-jupiter-api 6.1.0 directly, but mockito-junit-jupiter 5.23.0 has a transitive dependency on junit-jupiter-api 5.13.4. The CI logs confirm Maven is downloading both junit-bom 6.1.0 and junit-bom 5.13.4 BOMs. While Maven dependency mediation resolves this to 6.1.0 (the directly declared version) and tests currently pass, this version mismatch means Mockito 5.23.0 was compiled against and tested with JUnit 5.x APIs, not JUnit 6.x. This creates fragile coupling that could break with any Mockito or JUnit patch release.
    • high: The pitest-junit5-plugin (version 1.2.1) configured in the project is designed for JUnit 5. Its compatibility with JUnit 6 is not established. While pitest did not appear to run in the CI checks for this PR, mutation testing may fail when developers run it locally or when it is triggered in other CI scenarios.
    • ✅ All 287 unit tests and 20 integration tests pass with JUnit 6.1.0, demonstrating that the current codebase does not use any of the removed or changed APIs
    • ✅ All quality gates pass: 98% instruction coverage, 98% branch coverage, 0 SpotBugs bugs, 0 PMD violations, 0 Checkstyle errors, 0 OWASP vulnerabilities

sonnet - request_changes (45/100, 75% confidence)

  • Issues: 5 (2 critical)
    • critical: JUnit Jupiter upgrade from 5.11.4 to 6.1.0 introduces BREAKING CHANGES: (1) CSV parsing migration from univocity-parsers to FastCSV removes lineSeparator attribute from @CsvFileSource and changes exception messages for malformed CSV; (2) Constants class moved from org.junit.jupiter.engine.Constants to org.junit.jupiter.api.Constants; (3) AbstractTestDescriptor.getChildren() now returns immutable set instead of unmodifiable collection. Project has 23 test files that need verification.
    • critical: PITest mutation testing plugin (pitest-junit5-plugin version 1.2.1) compatibility with JUnit 6.1.0 is UNVERIFIED. Plugin documentation states support for JUnit Platform 1.5.0 to 1.10.0-M1, but JUnit 6.x uses a different platform version scheme. No evidence found that pitest-junit5-plugin 1.2.1 supports JUnit 6.x series. This could cause mutation testing to fail completely.
    • high: Mockito 5.23.0 compatibility with JUnit 6.1.0 is UNCERTAIN. GitHub issue Is Mockito compatible with JUnit 6? mockito/mockito#3779 (March 2026) raises concerns about Mockito compatibility with JUnit 6, particularly regarding Spring 7 which requires JUnit 6. While mockito-junit-jupiter extension exists, formal JUnit 6 support is not confirmed by Mockito project as of early 2026.
    • ✅ Automated dependency update via Dependabot reduces manual maintenance burden
    • ✅ Project already meets JUnit 6 Java 17 baseline requirement (maven.compiler.source=17)

haiku - approve (87/100, 92% confidence)

  • Issues: 2 (0 critical)
    • low: JUnit 6.1.0 introduces unified versioning and Constants relocation, but this project doesn't use the relocated classes. CSV lineSeparator attribute removed, but no CSV tests in project.
    • low: GitHub issue #3779 shows Mockito/JUnit 6 compatibility remains officially unresolved, though practical testing confirms it works. Community consensus supports compatibility but formal endorsement pending.
    • ✅ JUnit 6.1.0 is stable and production-ready (Sept 2025 release)
    • ✅ All tests pass with new version (mvn verify verified)

Arbiter Decision (opus)

This PR bumps JUnit from 5.11.4 to 6.1.0, which is a major version upgrade (5.x to 6.x), not a simple patch or minor update. While all 287 tests pass successfully, several concerns warrant requesting changes:

  1. CI is failing: The quality-check, Validate Pull Request, SonarCloud Scan, and Validate PR Title checks all fail. The build failure is from maven-site-plugin's Doxia Sitetools version mismatch, which may be a pre-existing issue but still means this PR cannot be merged in its current state with failing CI.

  2. Major version jump risk: Going from JUnit 5.x to 6.x is a significant major version upgrade. JUnit 6 may introduce breaking changes, removed APIs, or behavioral differences that could surface in edge cases not covered by the current test suite. Major version bumps deserve careful human review of the JUnit 6 migration guide and changelog to understand what changed.

  3. Downstream compatibility: This library is a foundation layer used by the Solenopsis stack. A major test framework version bump should be coordinated with downstream projects to ensure they are compatible with the same JUnit version.

Two of three models (scores 40 and 45) recommended requesting changes, citing the major version jump risk and CI failures. The third model (score 87) approved, likely weighing the passing tests heavily. The consensus aligns with requesting changes given the failing CI pipeline and the significance of a major version bump in a foundational library.

Key Concerns:

  • CI pipeline is failing: quality-check BUILD FAILURE (maven-site-plugin Doxia Sitetools mismatch), plus Validate Pull Request, SonarCloud Scan, and Validate PR Title checks all fail. PR cannot be merged with these failures.
  • Major version upgrade from JUnit 5.11.4 to 6.1.0 - this is a full major version bump (5.x to 6.x), not a routine patch update. Major version changes can introduce breaking API changes, removed methods, or behavioral differences.
  • As a foundational library in the Solenopsis stack, major dependency version changes should be reviewed against JUnit 6 migration documentation and coordinated with downstream consumers.
  • The PR title says '2 updates' (junit-jupiter-api and junit-jupiter-engine) but both use the same version property, so the diff is a single line change - this is fine but should be verified for consistency.

Automated review by pr-review-auto workflow
Approval Criteria: Quality ≥ 90, Consensus ≥ 85%, No breaking changes

sfloess
sfloess requested changes Jun 7, 2026
View reviewed changes

@sfloess sfloess left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Changes requested: Breaking changes detected: JUnit Jupiter 6.1.0, Mockito 5.23.0 compatibility, Maven Surefire Plugin 3.x

@sfloess

sfloess commented Jun 7, 2026

Copy link
Copy Markdown
Member

🤖 AUTONOMOUS PR REVIEW

Quality Score: 45/100
AI Consensus: approve (70% agreement)
Impact Risk: high
Auto-Decision: REJECT

Decision Reasoning

Breaking changes detected: JUnit Jupiter API, Test Infrastructure, Maven Surefire/Failsafe Integration

Impact Analysis

  • Breaking Changes: 3
    • ⚠️ JUnit Jupiter API: Upgrading from 5.11.4 to 6.1.0 requires Java 17+ (already satisfied), but JUnit 6.x introduces breaking changes in core APIs: removed modules (junit-platform-runner, junit-platform-jfr), deprecated store methods (getOrComputeIfAbsent), CSV annotation changes, and AbstractTestDescriptor.getChildren() now returns immutable set instead of unmodifiable set
    • ⚠️ Test Infrastructure: JUnit 6.1.0 removes previously deprecated APIs and changes behavior of AbstractTestDescriptor.getChildren() from unmodifiable to immutable sets. The uniqueIdFormat field was removed from UniqueId class. While basic @test, @beforeeach, @AfterEach annotations remain compatible, extension implementations using store APIs need migration from getOrComputeIfAbsent to computeIfAbsent
    • ⚠️ Maven Surefire/Failsafe Integration: JUnit Platform version automatically updated from 1.11.4 to 1.12.0+ as a transitive dependency, which may affect test discovery and execution behavior. The junit-platform-jfr module has been discontinued and its functionality integrated into junit-platform-launcher
  • High-Risk Changes: 4
  • Files Impacted: 23
  • Missing Tests: 0

AI Reviews (3 models)

opus - request_changes (25/100, 92% confidence)

  • Issues: 6 (2 critical)
    • critical: Major version jump from JUnit Jupiter 5.11.4 to 6.1.0. This is a breaking major version upgrade that crosses a major semver boundary (5.x to 6.x). JUnit 6 removes previously deprecated APIs, changes behavior of internal classes (e.g., AbstractTestDescriptor.getChildren() returns immutable instead of unmodifiable sets), removes the junit-platform-runner and junit-platform-jfr modules, and changes store API methods. While this project's tests use basic JUnit APIs (@test, @tempdir, Assertions), the ecosystem compatibility risk is high.
    • critical: pitest-junit5-plugin 1.2.1 is declared as a dependency of pitest-maven. This plugin is specifically designed for JUnit 5 and may not be compatible with JUnit 6.x. A JUnit 6-compatible pitest plugin (e.g., pitest-junit6-plugin or an updated pitest-junit5-plugin) would need to be verified and potentially replaced.
    • high: mockito-junit-jupiter 5.23.0 (used via @ExtendWith(MockitoExtension.class) in SoapUtilTest and StringUtilTest) may not be compatible with JUnit Jupiter 6.x. The MockitoExtension integrates with JUnit's extension API, which may have breaking changes in the 6.x line. Mockito would need to release a version that explicitly supports JUnit 6 before this upgrade is safe.
    • ✅ The PR correctly identifies both junit-jupiter-api and junit-jupiter-engine as needing the same version, keeping them in sync via the shared property
    • ✅ The PR is scoped to test-only dependencies (scope: test), so the breaking change does not affect production code or downstream consumers of the library

sonnet - request_changes (65/100, 92% confidence)

  • Issues: 4 (1 critical)
    • critical: JUnit Jupiter API upgrade from 5.11.4 to 6.1.0 is a MAJOR VERSION jump (JUnit 5 → JUnit 6) that introduces breaking changes. While tests currently pass, JUnit 6.x removes deprecated APIs (junit-platform-runner, junit-platform-jfr modules), changes Store API methods (getOrComputeIfAbsent removed), modifies AbstractTestDescriptor.getChildren() behavior, and removes UniqueId.uniqueIdFormat field. This is not a routine patch/minor update.
    • high: The upgrade from JUnit 5.11.4 to 6.1.0 is NOT a routine dependency bump. JUnit 6.1.0 is in milestone preview (6.1.0-M1) and not production-ready. The current stable release is 6.0.3 (February 2026). Using milestone versions in production violates project standards for stability.
    • medium: Maven Surefire/Failsafe transitive dependency automatically upgrades from JUnit Platform 1.11.4 to 1.12.0+, which may affect test discovery and execution behavior. The junit-platform-jfr module functionality has been integrated into junit-platform-launcher, potentially affecting performance profiling.
    • ✅ All 286 tests pass successfully with JUnit 6.1.0
    • ✅ Code coverage remains excellent: 98% instruction coverage, 95% branch coverage (both exceed project minimums of 93% and 86%)

haiku - request_changes (45/100, 92% confidence)

  • Issues: 5 (1 critical)
    • critical: JUnit API/Engine version mismatch: The PR updates junit-jupiter-api to 6.1.0 but uses the same property variable for junit-jupiter-engine. This creates an API-Engine version mismatch, which is a known JUnit 6.x requirement violation. Both must be identical major.minor versions (e.g., both 6.1.x). The engine will fail to initialize with mismatched versions.
    • high: JUnit 6.1.0 is a major version upgrade from 5.11.4 with breaking changes: removed junit-platform-runner module, removed junit-platform-jfr module, deprecated Store.getOrComputeIfAbsent() in favor of computeIfAbsent(), and TestDescriptor.getChildren() now returns immutable instead of unmodifiable collections. While current test code does not use these deprecated APIs directly, this is still a major version change requiring explicit testing and validation.
    • high: Mockito 5.23.0 compatibility with JUnit 6.1.0 not explicitly verified: While Mockito 5.x should be compatible with JUnit Platform 1.12.0+, this upgrade path (JUnit 5.11.4 → 6.1.0) represents a significant transitive dependency change to junit-platform-commons from 1.11.4 → 1.12.0+. This needs validation through full test execution before merging.
    • ✅ Test code uses only standard JUnit 5/6 compatible annotations (@test, @beforeeach, @ExtendWith) with no deprecated APIs
    • ✅ MockitoExtension is the only JUnit extension used, which is compatible with both JUnit 5.x and 6.x

Arbiter Decision (opus)

All three model reviews recommended request_changes, but after thorough investigation the concerns do not hold up against the actual evidence.

The PR bumps JUnit Jupiter (API and engine) from 5.11.4 to 6.1.0 -- a major version change. While major version bumps warrant scrutiny, the evidence strongly supports approval:

  1. ALL 287 UNIT TESTS PASS with zero failures, zero errors. The code compiles and runs correctly with JUnit 6.1.0.

  2. ALL QUALITY GATES PASS: JaCoCo coverage at 98%/98% (well above the 93%/86% thresholds), SpotBugs 0 bugs, PMD 0 violations, Checkstyle 0 errors, OWASP 0 vulnerabilities.

  3. CI FAILURES ARE UNRELATED TO THIS PR:

    • quality-check fails due to maven-site-plugin 3.12.1 Doxia version incompatibility (pre-existing issue)
    • SonarCloud Scan fails due to SONAR_TOKEN configuration (pre-existing issue)
    • PR title validation fails because dependabot titles do not follow conventional commits (cosmetic)

  4. JUnit 6 migration from 5.x is well-documented as smooth. JUnit 6 requires Java 17+ baseline, which this project already meets (maven.compiler.source/target = 17). Core annotations, extensions, and test lifecycle are preserved. No code changes were needed in the test suite.

  5. The change is test-scoped only -- both junit-jupiter-api and junit-jupiter-engine are declared with scope=test. There is zero impact on the library's production API or runtime dependencies.

  6. SonarCloud independently confirms 0 new issues on this PR.

The three reviewing models likely flagged this as a major version bump requiring caution, which is reasonable as a general principle. However, the concrete evidence (all tests pass, all quality gates pass, no code changes needed, test-scope only) demonstrates this upgrade is safe and beneficial. Staying on JUnit 5.x when 6.x is the current stable release would accumulate technical debt.

Key Concerns:

  • This is a major version bump (JUnit 5.x to 6.x), but all 287 tests pass without any code changes, confirming backward compatibility for this project's usage patterns.
  • CI check failures (quality-check, SonarCloud Scan, PR title validation) are all pre-existing issues unrelated to this dependency update.
  • The file mode change from 100755 to 100644 on pom.xml is harmless -- removing an unnecessary executable bit.
  • Both junit-jupiter-api and junit-jupiter-engine share the same version property, so both are upgraded together as intended by the dependabot group update.
  • JUnit 6 requires Java 17+ minimum, which this project already satisfies with its maven.compiler.source/target = 17 configuration.

Automated review by pr-review-auto workflow
Approval Criteria: Quality ≥ 90, Consensus ≥ 85%, No breaking changes

sfloess
sfloess requested changes Jun 7, 2026
View reviewed changes

@sfloess sfloess left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Changes requested: Breaking changes detected: JUnit Jupiter API, Test Infrastructure, Maven Surefire/Failsafe Integration

@dependabot
Bump the test-dependencies group across 1 directory with 2 updates
8fce9ae 
Bumps the test-dependencies group with 2 updates in the / directory: [org.junit.jupiter:junit-jupiter-api](https://github.com/junit-team/junit-framework) and [org.junit.jupiter:junit-jupiter-engine](https://github.com/junit-team/junit-framework).


Updates `org.junit.jupiter:junit-jupiter-api` from 5.11.4 to 6.1.0
- [Release notes](https://github.com/junit-team/junit-framework/releases)
- [Commits](junit-team/junit-framework@r5.11.4...r6.1.0)

Updates `org.junit.jupiter:junit-jupiter-engine` from 5.11.4 to 6.1.0
- [Release notes](https://github.com/junit-team/junit-framework/releases)
- [Commits](junit-team/junit-framework@r5.11.4...r6.1.0)

Updates `org.junit.jupiter:junit-jupiter-engine` from 5.11.4 to 6.1.0
- [Release notes](https://github.com/junit-team/junit-framework/releases)
- [Commits](junit-team/junit-framework@r5.11.4...r6.1.0)

---
updated-dependencies:
- dependency-name: org.junit.jupiter:junit-jupiter-api
  dependency-version: 6.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: test-dependencies
- dependency-name: org.junit.jupiter:junit-jupiter-engine
  dependency-version: 6.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: test-dependencies
- dependency-name: org.junit.jupiter:junit-jupiter-engine
  dependency-version: 6.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: test-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump the test-dependencies group with 2 updates Bump the test-dependencies group across 1 directory with 2 updates Jun 8, 2026
@dependabot dependabot Bot force-pushed the dependabot/maven/test-dependencies-4ac7b52158 branch from e12c260 to 8fce9ae Compare June 8, 2026 10:11
@sonarqubecloud

sonarqubecloud Bot commented Jun 8, 2026

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown

PR Validation Results

✅ Code Coverage

Coverage report generated. Download artifacts to view details.

Quality Checks

  • ✅ Compilation successful
  • ✅ All tests passed
  • ✅ Code coverage meets requirements
  • ✅ SpotBugs analysis passed
  • ✅ PMD analysis passed
  • ✅ Checkstyle passed
  • ✅ JavaDoc generation successful

Note: Full build artifacts are available for download.

@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown

📊 Quality Gate Report

Tool Status Metrics
🧪 JaCoCo ✅ Instruction: 98%, Branch: 98%
🐛 SpotBugs ✅ 0 bugs found
📝 PMD ✅ 0 violations
✓ Checkstyle ✅ 0 errors
🔒 OWASP ✅ 0 vulnerabilities (0 critical, 0 high)

✅ All quality gates passed!

📋 View detailed reports

Download the quality-reports artifact from this workflow run for detailed analysis.

  • JaCoCo: target/site/jacoco/index.html
  • SpotBugs: target/spotbugsXml.xml
  • PMD: target/pmd.xml
  • Checkstyle: target/checkstyle-result.xml
  • OWASP: target/dependency-check-report.xml

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

Reviewers

@sfloess sfloess sfloess requested changes

Assignees

No one assigned

Labels

automated

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@sfloess