Skip to content

Release v2.5.0

Choose a tag to compare
@NATS-CI NATS-CI released this 09 Sep 22:12
· 4153 commits to main since this release


Notice for JetStream Users

See important note if upgrading from a version prior to v2.4.0.

Notice for MQTT Users

See note in the Improved and Changed section.

Go Version

  • 1.16.8: Both release executables and Docker images are built with this Go release.


  • MQTT/Monitoring:
    • MQTTClient in the /connz connections report and system events CONNECT and DISCONNECT. Ability to select on mqtt_client. Thanks to @carr123 and @imranrazakhan for the suggestions (#2507)


  • MQTT:
    • Sessions are now all stored inside a single stream, as opposed to individual streams, reducing resources usage (#2501)


  • JetStream:
    • Using Nats-Expected-Last-Subject-Sequence header with a value of 0 now means that the server will reject the store command if there were messages on this subject (#2506)
  • MQTT:
    • Due to improvement described above, when an MQTT client connects for the first time after an upgrade to this server version, the server will migrate all individual $MQTT_sess_<xxxx> streams to a new $MQTT_sess stream for the user's account (#2501)


  • JetStream:
    • Possible deadlock due to lock inversion (#2479)
    • Possible consumer stall. Thanks to @carr123 for the report (#2480)
    • Don't send 408 status when pull request expires. This has no visible impact for users, but library implementers may want to be aware of it (#2482)
    • During peer removal, try to remap any stream or consumer assets (#2493)
    • Issues with remapping of stream and/or consumer assets during peer removal (#2493)
    • Issue that could lead to perceived message loss (#2490)
    • Message cleanup for interest stream and AckNone consumers in clustered mode (#2499)
    • Suppress duplicates on JS deny all for system account (#2502)
    • Consumers stopped receiving messages. Thanks to @anjmao, @izarraga and @tigrato for the report (#2505)
  • Handle SIGTERM on Windows platform (#2481)
  • Account resolver TLS connection may fail with x509: certificate signed by unknown authority errors. Thanks to @Ryner51, @ronaldslc for the report (#2483)

Complete Changes