bump spring-web to 6.2.12 and fix compatibility with new api by a-simeshin · Pull Request #1161 · allure-framework/allure-java

Skip to content

Navigation Menu

Sign in

Appearance settings

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Conversation

@a-simeshin

Copy link Copy Markdown

Contributor

@a-simeshin a-simeshin commented

May 3, 2025

edited

Loading

Context

  • bump spring-web to 6.2.12
  • fix compatibility with new api

Spring-web changes:

  1. spring-web 6+ have java 17 baseline
  2. removed method org.springframework.http.HttpRequest.getMethodValue()
  3. deprecated method org.springframework.http.client.ClientHttpResponse.getRawStatusCode()

Breaking changes:

  1. allure-spring-web compile java version set to 17, was 8

Checklist

Signed-off-by: Artem Simeshin <a.simeshin@gmail.com>

bump spring-web to 6.2.6 and fix compatibility with new api

@a-simeshin a-simeshin force-pushed the fix-spring-web-6-comaptibility branch from e00e76e to a1ff336 Compare

November 12, 2025 20:50

@a-simeshin a-simeshin changed the title bump spring-web to 6.2.6 and fix compatibility with new api bump spring-web to 6.2.12 and fix compatibility with new api

Nov 12, 2025

@baev baev added the type:improvement

Change that improves some user experience but can't be considered as a new feature

label

Nov 13, 2025

@baev baev merged commit 85f3ccd into allure-framework:main

Nov 13, 2025

4 of 5 checks passed

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

Reviewers

@baev baev baev approved these changes

Assignees

No one assigned

Labels

theme:build theme:spring type:improvement

Change that improves some user experience but can't be considered as a new feature

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@a-simeshin @baev