Apply ClientHttpResponse#getRawStatusCode() migration as of Spring Framework 6.0#1031
Merged
timtebeek merged 1 commit intoMay 29, 2026
Merged
Conversation
…amework 6.0 The deprecation and HttpStatusCode return-type change for ClientHttpResponse#getRawStatusCode() landed in Spring Framework 6.0, but MigrateClientHttpResponseGetRawStatusCodeMethod was only wired into UpgradeSpringFramework_6_2. Move it to UpgradeSpringFramework_6_0 so the fix is applied for anyone migrating to 6.0; it is still inherited by 6.1 and 6.2 via the upgrade chain.
Jenson3210
approved these changes
May 29, 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.
ClientHttpResponse#getRawStatusCode()was deprecated and its siblinggetStatusCode()changed its return type fromHttpStatustoHttpStatusCodein Spring Framework 6.0. The recipe that handles this,MigrateClientHttpResponseGetRawStatusCodeMethod, was only wired intoUpgradeSpringFramework_6_2, so applications migrating to 6.0 (the version that actually introduced the change) did not get the fix.This moves the recipe into
UpgradeSpringFramework_6_0, alongside the relatedMigrateResponseStatusExceptionmigration. It is still applied for 6.1 and 6.2 since those chain throughUpgradeSpringFramework_6_0, so the direct entry inUpgradeSpringFramework_6_2is removed to avoid duplication.