Repository navigation
deps: bump testng, cucumber, surefire-testng in lockstep - #96
Merged
Merged
Conversation
- testng 7.9.0 -> 7.12.0 (as proposed in #92, verified green) - cucumber-java 7.34.8 -> 8.0.3, cucumber-testng 7.20.1 -> 8.0.3 (not 8.0.1 as #93 proposed: 8.0.1's own transitive deps conflict — cucumber-core pins io.cucumber:messages:34.2.1 while several of its other transitives require messages in the 32.x/33.x range, so 8.0.1 can't even resolve. 8.0.3 resolves cleanly. Bumped cucumber-testng alongside it since the pom comment requires matching versions.) - maven-surefire-plugin 3.2.5 -> 3.5.6, surefire-testng 3.2.5 -> 3.5.6 (not 3.6.0 as #90 proposed: the surefire-testng provider was never published at 3.6.0, only the plugin was, so #90 fails to resolve. 3.5.6 is the latest version published for both.) 547 tests green on `mvn clean verify`. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Supersedes #90, #92, #93 (and leaves #91 unneeded) — those four dependabot PRs each bump one artifact independently, but two of them are individually broken:
cucumber-core:8.0.1pinsio.cucumber:messages:34.2.1while several of its other transitives (pretty-formatter,query,teamcity-formatter,usage-formatter,cucumber-json-formatter) requiremessagesin the32.x–33.xrange — an unsatisfiable conflict baked into that release. 8.0.3 resolves cleanly. Bumped cucumber-testng 7.20.1 → 8.0.3 alongside it, since the pom's own comment requires the two to stay on matching versions.maven-surefire-plugin:3.6.0was published, butsurefire-testng:3.6.0(its TestNG provider) never was, so deps: bump org.apache.maven.plugins:maven-surefire-plugin from 3.2.5 to 3.6.0 #90 fails withCould not find artifact org.apache.maven.surefire:surefire-testng:jar:3.6.0. deps: bump org.apache.maven.surefire:surefire-testng from 3.2.5 to 3.5.6 #91 alone would've had the same lockstep problem in reverse (provider at 3.5.6, plugin still 3.2.5). 3.5.6 is the latest version published for both.Testing
mvn clean verifywith all four changes together: 547 tests, 0 failures, 0 errors, GPG-signed jar builds successfully.🤖 Generated with Claude Code