release(1.2.0): stream responses and evaluate body return patterns

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## Unreleased
+## [1.2.0] - 2026-10-17
 
 ### Fixed
 

README.md

@@ -39,11 +39,11 @@ Published on Maven Central:
 
 ```kotlin
 dependencies {
-    implementation("com.guard-core:spring-boot-guard:1.1.0")
+    implementation("com.guard-core:spring-boot-guard:1.2.0")
 }
 ```
 
-It brings in the engine facade `com.guard-core:guard-core:4.3.3`. To build from source, see "Engine dependency" below, or consume the composite from a sibling checkout.
+It brings in the engine facade `com.guard-core:guard-core:4.4.0`. To build from source, see "Engine dependency" below, or consume the composite from a sibling checkout.
 
 ## Kotlin and coroutines versions under Spring Boot dependency management
 
@@ -164,10 +164,10 @@ logs the same "eager init not honored" warning as fastapi-guard.
 The engine artifact `com.guard-core:guard-core` (groupId is the Central Portal namespace; Kotlin
 packages stay `com.guardcore.*`) is on Maven Central for consumers. This repository's own build pins the engine from source instead: CI and local builds check out `Guard-Core/guard-core-jvm` at the
 pinned ref `7711606` as the sibling directory `./guard-core-jvm`, and `settings.gradle.kts`
-substitutes the declared coordinates `com.guard-core:guard-core:4.3.3` /
-`com.guard-core:guard-core-engine:4.3.3` with the included build's projects (the Gradle analog of
+substitutes the declared coordinates `com.guard-core:guard-core:4.4.0` /
+`com.guard-core:guard-core-engine:4.4.0` with the included build's projects (the Gradle analog of
 the Rust path+version pattern). The declared dependency coordinates stay
-`com.guard-core:guard-core:4.3.3` (lockstep version per the family versioning law); consumers of a
+`com.guard-core:guard-core:4.4.0` (lockstep version per the family versioning law); consumers of a
 published artifact resolve the real Maven artifact with no composite involved.
 
 Set `GUARD_CORE_USE_COMPOSITE=false` to build without the composite: the declared coordinates then

build.gradle.kts

@@ -15,7 +15,7 @@ plugins {
 // standard practice for hyphenated domains.
 group = "com.guard-core"
 
-version = "1.1.0"
+version = "1.2.0"
 
 // Section 14.3 lockfile analog: every configuration resolves against the
 // committed gradle.lockfile. A dependency change without
@@ -34,7 +34,7 @@ kotlin {
 }
 
 dependencies {
-  // The engine facade: com.guard-core:guard-core:4.3.3, substituted with the
+  // The engine facade: com.guard-core:guard-core:4.4.0, substituted with the
   // pinned guard-core-jvm includeBuild checkout (settings.gradle.kts).
   api(libs.guard.core)
   implementation(platform(libs.netty.bom))

docs/index.md

@@ -7,8 +7,8 @@ pipeline runs per request, error responses come byte-exact from the facade
 response factory, and the `guard.*` property surface reaches every
 `SecurityConfig` field.
 
-- **Status**: 1.0.0, released (the first synchronized release)
-- **Engine**: `com.guard-core:guard-core:4.3.3` (built from source through a
+- **Status**: 1.2.0, released
+- **Engine**: `com.guard-core:guard-core:4.4.0` (built from source through a
   composite build, see [Installation](installation.md))
 - **Parity**: the engine's
   [every-feature matrix](https://github.com/Guard-Core/guard-core-jvm/blob/master/docs/every-feature-matrix.md)

docs/installation.md

@@ -13,7 +13,7 @@ Published on Maven Central:
 
 ```kotlin
 dependencies {
-    implementation("com.guard-core:spring-boot-guard:1.1.0")
+    implementation("com.guard-core:spring-boot-guard:1.2.0")
 }
 ```
 
@@ -56,9 +56,9 @@ With `spring-boot-starter-parent` as the parent, set `<kotlin.version>2.4.21</ko
 Consumers resolve the engine artifact `com.guard-core:guard-core` from Maven Central. This repository's own build pins the engine from source instead: CI and
 local builds check out `Guard-Core/guard-core-jvm` at the pinned ref `7711606`
 as the sibling directory `./guard-core-jvm`, and `settings.gradle.kts`
-substitutes the declared coordinates `com.guard-core:guard-core:4.3.3` /
-`com.guard-core:guard-core-engine:4.3.3` with the included build's projects.
-The declared dependency coordinates stay `com.guard-core:guard-core:4.3.3`
+substitutes the declared coordinates `com.guard-core:guard-core:4.4.0` /
+`com.guard-core:guard-core-engine:4.4.0` with the included build's projects.
+The declared dependency coordinates stay `com.guard-core:guard-core:4.4.0`
 (lockstep version per the family versioning law).
 
 ```bash