From b8aaa4fd92888b1a0f5f7dc9a79e991cdad610ab Mon Sep 17 00:00:00 2001 From: Canitas Date: Tue, 23 Jun 2026 15:44:47 -0700 Subject: [PATCH] docs(release): clarify platform line break --- CHANGELOG.md | 5 +++-- README.md | 7 ++++--- docs/release.md | 8 +++++--- docs/usage-guide.md | 7 ++++--- 4 files changed, 16 insertions(+), 11 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f1ed0a2..b1e1986 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -18,8 +18,9 @@ include migration notes. `tools.jackson.databind.ObjectMapper`. - Updated integration tests for Spring Boot 4's `spring-boot-resttestclient` package and explicit test client auto-configuration. -- Recommended a new `7.0.0` release for Spring Boot 4.1 consumers. Use - `6.0.x` for Spring Boot 3.5 / Java 21 applications. +- Recommended a new `7.0.0` release for Spring Boot 4.1 consumers. Vigil + `6.0.x` was the final Spring Boot 3.5 / Java 21 line, not a + backward-compatibility target for `7.0.x`. ## 6.0.0 - 2026-06-05 diff --git a/README.md b/README.md index c08e227..ede878a 100644 --- a/README.md +++ b/README.md @@ -19,9 +19,10 @@ Vigil `7.0.0` is the Spring Boot 4.1.x / Java 25 certification line. | Gradle wrapper | 9.1.x | | JSON support | Jackson 3 (`tools.jackson`) | -Vigil `6.0.x` remains the Spring Boot 3.5.x / Java 21 line. Spring Boot 4.1 -consumers should use `7.0.0` or newer because Boot 4 moves to Jackson 3 and -modular test/client support. +Vigil `7.0.x` is the active supported platform line. Vigil `6.0.x` was the +final Spring Boot 3.5.x / Java 21 line and is not supported for Spring Boot +4.1 consumers. Do not add compatibility shims between the two lines; Boot 4 +moves to Jackson 3 and modular test/client support. The only intentional public API break in `7.0.0` is the JSON mapper type used by `VigilAuthenticationEntryPoint`: Spring Boot 4 defaults to Jackson 3, so the diff --git a/docs/release.md b/docs/release.md index d25dda0..030be9d 100644 --- a/docs/release.md +++ b/docs/release.md @@ -44,9 +44,11 @@ Current tested compatibility envelope: - HS256 with a configured 256-bit minimum secret; - RS256 with configured PEM private/public keys and JWKS publication. -Vigil `6.0.x` is the Spring Boot 3.5.x / Java 21 line. Spring Boot 4.1 -consumers must use a `7.0.x` or newer artifact because Boot 4 changes the -default JSON stack to Jackson 3 and modularizes several Boot support packages. +Vigil `7.0.x` is the active supported platform line. Vigil `6.0.x` was the +final Spring Boot 3.5.x / Java 21 line and is not supported for Spring Boot +4.1 consumers. Do not add compatibility shims between the two lines; Boot 4 +changes the default JSON stack to Jackson 3 and modularizes several Boot +support packages. The `7.0.0` line intentionally changes `VigilAuthenticationEntryPoint(String, ObjectMapper)` from Jackson 2 diff --git a/docs/usage-guide.md b/docs/usage-guide.md index 178490c..fd796bc 100644 --- a/docs/usage-guide.md +++ b/docs/usage-guide.md @@ -15,9 +15,10 @@ Vigil `7.0.x` supports Spring Boot 4.1.x, Spring Framework 7.x, Spring Security 7.1.x, Java 25, Gradle 9.1.x, and Jackson 3. Consumers still own their `SecurityFilterChain` and product authentication endpoints. -Use Vigil `6.0.x` for Spring Boot 3.5.x / Java 21 applications. Do not mix the -Boot 3.5 line with Vigil `7.0.x` because Spring Boot 4 moves JSON support to -Jackson 3 `tools.jackson` packages. +Vigil `6.0.x` was the final Spring Boot 3.5.x / Java 21 line. Do not mix the +Boot 3.5 line with Vigil `7.0.x`, and do not add compatibility shims between +the two platform lines. Spring Boot 4 moves JSON support to Jackson 3 +`tools.jackson` packages. ## Choosing The Client Path