root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 9 Packages Projects Releases Wiki Activity

Release notes updates 

References #10439
This commit is contained in:
Michael Klishin 2024-09-12 20:40:06 -04:00
parent 8eaddc44ca
commit 8ab0d4cf68
2 changed files with 24 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
release-notes/3.13.0.md
View File

@ -172,14 +172,15 @@ connect to the same node, or inject a pause, or await a certain condition that i
is in place. is in place.
### TLS Defaults ### TLS Client (LDAP, Shovels, Federation) Defaults
Starting with Erlang 26, client side [TLS peer certificate chain verification](https://www.rabbitmq.com/docs/ssl#peer-verification) settings are enabled by default in most contexts: Starting with Erlang 26, client side [TLS peer certificate chain verification](https://www.rabbitmq.com/docs/ssl#peer-verification) settings are enabled by default in most contexts:
from federation links to shovels to TLS-enabled LDAP client connections. from federation links to shovels to TLS-enabled LDAP client connections.
If using TLS peer certificate chain verification is not practical or necessary, it can be disabled. If using TLS peer certificate chain verification is not practical or necessary, it can be disabled.
Please refer to the docs of the feature in question, for example, Please refer to the docs of the feature in question, for example,
this one [on TLS-enabled LDAP client](http://rabbitmq.com/docs/ldap/#tls) connections. this one [on TLS-enabled LDAP client](http://rabbitmq.com/docs/ldap/#tls) connections,
two others on [TLS-enabled dynamic shovels](https://www.rabbitmq.com/docs/shovel#tls) and [dynamic shovel URI query parameters](https://www.rabbitmq.com/docs/uri-query-parameters).
### Management Plugin and HTTP API ### Management Plugin and HTTP API

20
release-notes/4.0.0.md
View File

@ -1,6 +1,6 @@
## RabbitMQ 4.0.0-rc.1 ## RabbitMQ 4.0.0-rc.2
RabbitMQ `4.0.0-rc.1` is a candidate of a new major release. RabbitMQ `4.0.0-rc.2` is a candidate of a new major release.
Starting June 1st, 2024, community support for this series will only be provided to [regularly contributing users](https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md) Starting June 1st, 2024, community support for this series will only be provided to [regularly contributing users](https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md)
and those who hold a valid [commercial support license](https://tanzu.vmware.com/rabbitmq/oss). and those who hold a valid [commercial support license](https://tanzu.vmware.com/rabbitmq/oss).
@ -124,10 +124,22 @@ and `amqp1_0.default_user` are unsupported in RabbitMQ 4.0.
Instead, set the new RabbitMQ 4.0 settings `anonymous_login_user` and `anonymous_login_pass` (both values default to `guest`). Instead, set the new RabbitMQ 4.0 settings `anonymous_login_user` and `anonymous_login_pass` (both values default to `guest`).
For production scenarios, [disallow anonymous logins](https://www.rabbitmq.com/docs/next/production-checklist#anonymous-login). For production scenarios, [disallow anonymous logins](https://www.rabbitmq.com/docs/next/production-checklist#anonymous-login).
### TLS Client (LDAP, Shovels, Federation) Defaults
Starting with Erlang 26, client side [TLS peer certificate chain verification](https://www.rabbitmq.com/docs/ssl#peer-verification) settings are enabled by default in most contexts:
from federation links to shovels to TLS-enabled LDAP client connections.
If using TLS peer certificate chain verification is not practical or necessary, it can be disabled.
Please refer to the docs of the feature in question, for example,
this one [on TLS-enabled LDAP client](http://rabbitmq.com/docs/ldap/#tls) connections,
two others on [TLS-enabled dynamic shovels](https://www.rabbitmq.com/docs/shovel#tls) and [dynamic shovel URI query parameters](https://www.rabbitmq.com/docs/uri-query-parameters).
### Shovels ### Shovels
RabbitMQ Shovels will be able connect to a RabbitMQ 4.0 node via AMQP 1.0 only when the Shovel runs on a RabbitMQ node >= `3.13.7`. RabbitMQ Shovels will be able connect to a RabbitMQ 4.0 node via AMQP 1.0 only when the Shovel runs on a RabbitMQ node >= `3.13.7`.
TLS-enabled Shovels will be affected by the TLS client default changes in Erlang 26 (see above).
## Erlang/OTP Compatibility Notes ## Erlang/OTP Compatibility Notes
@ -351,10 +363,10 @@ GitHub issues: [#8334](https://github.com/rabbitmq/rabbitmq-server/pull/8334), [
### Dependency Changes ### Dependency Changes
* Ra was [upgraded to `2.14.0`](https://github.com/rabbitmq/ra/releases) * Ra was [upgraded to `2.14.0`](https://github.com/rabbitmq/ra/releases)
* Khepri was [upgraded to `0.15.0`](https://github.com/rabbitmq/khepri/releases) * Khepri was [upgraded to `0.16.0`](https://github.com/rabbitmq/khepri/releases)
* Cuttlefish was [upgraded to `3.4.0`](https://github.com/Kyorai/cuttlefish/releases) * Cuttlefish was [upgraded to `3.4.0`](https://github.com/Kyorai/cuttlefish/releases)
## Source Code Archives ## Source Code Archives
To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-4.0.0-rc.1.tar.xz` To obtain source code of the entire distribution, please download the archive named `rabbitmq-server-4.0.0-rc.2.tar.xz`
instead of the source tarball produced by GitHub. instead of the source tarball produced by GitHub.