3.16.0 release notes

quarkiverse · Oct 25, 2024 · 4265a65 · 4265a65
1 parent 29db8ea
commit 4265a65
Show file tree

Hide file tree

Showing 4 changed files with 20 additions and 4 deletions.
diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc
@@ -33,6 +33,7 @@
 ** xref:security-guide/ws-securitypolicy-auth.adoc[WS-SecurityPolicy Authentication]
 * xref:release-notes/index.adoc[Release notes]
 ifeval::[{doc-is-main} == true]
+** xref:release-notes/3.16.1.adoc[3.16.1]
 ** xref:release-notes/3.16.0.adoc[3.16.0]
 ** xref:release-notes/3.15.2.adoc[3.15.2 LTS]
 ** xref:release-notes/3.15.1.adoc[3.15.1 LTS]

diff --git a/docs/modules/ROOT/pages/release-notes/3.16.0.adoc b/docs/modules/ROOT/pages/release-notes/3.16.0.adoc
@@ -11,10 +11,13 @@
 {link-quarkus-docs-base}/tls-registry-reference[Quarkus TLS registry] is an extension provided by Quarkus that centralizes the TLS configuration,
 making it easier to manage and maintain secure connections across your application.
 
+[NOTE]
+====
 `io.quarkus:quarkus-tls-registry` is a transitive dependency of `io.quarkiverse.cxf:quarkus-cxf` since {quarkus-cxf-project-name} 3.16.0,
 so you do not have to add it manually.
+====
 
-This is the new recommended way of configuring trust stores, keystores and other TLS/SSL related settings:
+This is the new recommended way of configuring trust stores, keystores and other TLS/SSL related settings in {quarkus-cxf-project-name} 3.16.0+:
 
 .application.properties
 [source,properties]
@@ -66,7 +69,7 @@ quarkus.cxf.client."client-name".http-conduit-factory = VertxHttpClientHTTPCondu
 quarkus.cxf.http-conduit-factory = VertxHttpClientHTTPConduitFactory
 ----
 
-Since then, it went through some improvements and testing so that we are confident to make it default.
+Since then, it went through some improvements and testing so that we are now confident to make it default.
 
 The main motivations for using Vert.x HttpClient based HTTP Conduit as a default are as follows:
 
@@ -79,7 +82,7 @@ The main motivations for using Vert.x HttpClient based HTTP Conduit as a default
 Before this change, the effective default was `URLConnectionHTTPConduitFactory`.
 It is still supported and tested regularly.
 
-There are three options how you can get back to the old default:
+There are three ways how you can get back to the old default:
 
 * Set the `QUARKUS_CXF_DEFAULT_HTTP_CONDUIT_FACTORY` environment variable to `URLConnectionHTTPConduitFactory`
 * Set the global xref:reference/extensions/quarkus-cxf.adoc#quarkus-cxf_quarkus-cxf-http-conduit-factory[quarkus.cxf.http-conduit-factory] option to `URLConnectionHTTPConduitFactory`

diff --git a/docs/modules/ROOT/pages/release-notes/3.16.1.adoc b/docs/modules/ROOT/pages/release-notes/3.16.1.adoc
@@ -0,0 +1,11 @@
+= {quarkus-cxf-project-name} 3.16.1 release notes
+
+Compared to xref:release-notes/3.16.0.adoc[3.16.0], there are no user facing changes in this release.
+We had to do it only because on the first attempt,
+the https://quarkus.io/blog/quarkiverse-and-smallrye-new-release-process/[new release process]
+failed to deploy some testing artifact to Maven Central that was required for validation on
+https://github.com/quarkusio/quarkus-platform[Quarkus Platform].
+
+== Full changelog
+
+https://github.com/quarkiverse/quarkus-cxf/compare/3.16.0+++...+++3.16.1
diff --git a/docs/modules/ROOT/pages/release-notes/index.adoc b/docs/modules/ROOT/pages/release-notes/index.adoc
@@ -19,7 +19,8 @@ Those are typically released on Wednesday following the {quarkus-cxf-project-nam
 |===
 | Quarkus CXF | Release date | Quarkus Platform | CXF
 
-| xref:release-notes/3.16.0.adoc[3.16.0] | 2024-10-24 | 3.16.0 | 4.0.5
+| xref:release-notes/3.16.0.adoc[3.16.0] | 2024-10-24 |        | 4.0.5
+| xref:release-notes/3.16.1.adoc[3.16.1] | 2024-10-24 | 3.16.0 | 4.0.5
 
 | xref:release-notes/3.15.2.adoc[3.15.2 LTS] | 2024-10-03 | 3.15.? | 4.0.5
 | xref:release-notes/3.15.1.adoc[3.15.1 LTS] | 2024-09-23 | 3.15.0 | 4.0.5