Upgrade io.rest-assured family 4.5.1 -> 5.5.2 (no source changes) - #198
Open
devin-ai-integration[bot] wants to merge 1 commit into
Open
Upgrade io.rest-assured family 4.5.1 -> 5.5.2 (no source changes)#198devin-ai-integration[bot] wants to merge 1 commit into
devin-ai-integration[bot] wants to merge 1 commit into
Conversation
Bumps rest-assured, json-path, xml-path and spring-mock-mvc together. No source changes: io.restassured.* package names are unchanged between 4.5 and 5.x. Groovy moves from org.codehaus.groovy 3.x to org.apache.groovy 4.0.22 transitively; the two use different Maven groups so the Boot 2.6.3 BOM's groovy.version does not apply and no ext override is needed.
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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.
Summary
Upgrades the
io.rest-assuredtest-scope artifact family from 4.5.1 to 5.5.2 (highest stable 5.x; published 2025-05-14). Zero source changes were needed — theio.restassured.*package and API surface used by this repo (RestAssuredMockMvc, its staticgiven()) is unchanged between 4.5 and 5.x.The only behavioural delta is transitive: rest-assured 5.x moved from Groovy 3 (
org.codehaus.groovy) to Groovy 4 (org.apache.groovy). Because Groovy 4 ships under a different Maven group, the Spring Boot 2.6.3 BOM'sgroovy.version(which managesorg.codehaus.groovy:*) does not apply to it, so noext['groovy.version']override or explicit test-scope pin is required — and there is no classpath split, sinceorg.codehaus.groovydisappears fromtestRuntimeClasspathentirely once 4.5.1 is gone.Stays inside the fixed ceiling: rest-assured 5.5.2 is Java 8 bytecode (
major 52) andspring-mock-mvc5.5.2 still compiles against Spring 5.1 /javax.servlet3.1, so it is compatible with Spring Boot 2.6.3 + Java 11. Spring Boot, the dependency-management plugin, DGS, and every other dependency are untouched.Coordinate diff
Also updates the stale
4.5.1baseline row in.agents/skills/java-engineering-excellence/SKILL.mdso the skill's dependency table matches reality.BOM /
extoverridesNone needed. Checked explicitly:
io.rest-assured:*is not managed by the Boot 2.6.3 BOM; the literal versions inbuild.gradlewin.graphql-dgs-platform-dependencies:4.3.1) requests{prefer 3.3.0}for the rest-assured artifacts —preferyields to the declared 5.5.2, confirmed below.org.apache.groovy:*, a group the Boot 2.6 BOM does not manage.dependencyInsightevidence (testRuntimeClasspath)No conflict-resolution downgrade, one version per artifact, and exactly one Groovy on the classpath.
API migration
None.
grep -rn "io.restassured" src/returns only:Both are unchanged in 5.x. No test assertions,
@Disabledannotations, or coverage/format thresholds were modified.Gate
main)spotlessCheckBoth runs performed first-hand on JDK 11 (the JDK CI uses, matching
sourceCompatibility = 11). Test count is identical — no tests silently stopped being discovered.Pre-existing on base, not addressed here
jacocoTestCoverageVerificationfails onmainat ~0.33 instruction coverage against the 0.80 rule inbuild.gradle. CI excludes it (./gradlew clean test -x jacocoTestCoverageVerification), so this run excludes it too. The threshold was not lowered and no tests were added to raise coverage — out of scope for a dependency bump.spotlessJavaimplicit-dependency and Gradle-8 deprecation warnings on bothmainand this branch; unrelated to this change.Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/a0cb9f9040164a358821ab1c334e7755
Requested by: @mbatchelor81