RATATOSK
← All releases

NATSv2.12.3

Security 4Breaking changes 6Important fixes 27Enhancements 13Dependency updates 8Other changes 11

Get NATS alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Upgrade guide1
2.12 upgrade guide for users on 2.11.x
2 items from linked documents
  • GC thresholds controlled by GOMEMLIMITThe note says tuning GOMEMLIMIT may be appropriate based on available system memory or, in Kubernetes, memory reservations.
  • Stream state files rebuilt after downgradeOn the first restart after downgrading from v2.12 to v2.11, all stream message blocks are rescanned, which can increase CPU use and delay the restarted node reporting healthy. This does not cause data loss.
Original release notes
Refer to the [2.12 Upgrade Guide](https://docs.nats.io/release-notes/whats_new/whats_new_212) for backwards compatibility notes with 2.11.x.
github.com/nats-io/nats-server/releases/tag/v2.12.3

Security4medium1

WebSocket compression-bomb memory use fixed

medium

2026-02-23 Security advisory GHSA-qrvq-68c2-7grw published after the release

AffectsWebSocket connections receiving compressed frames

Previously, decompressing a highly compressed frame could create a very large buffer before the server rejected it for exceeding the maximum payload size, risking excessive memory use and server termination. Decompression now stops at the configured maximum payload size, or the default maximum if none is specified, and returns ErrMaxPayload.

Show release-note lines
- WebSocket connections will now correctly limit the buffer size during decompression (#7625, thanks to Pavel Kokout at Aisle Research)
github.com/nats-io/nats-server/releases/tag/v2.12.3
Security advisory
This was fixed in the v2.11 series with v2.11.12 and in the v2.12 series with v2.12.3.
github.com/nats-io/nats-server/security/advisories/GHSA-qrvq-68c2-7grw

Implicit $MQTT. subject permissions for MQTT clients and non-client connections

AffectsMQTT clients and non-client connections, including routes and leaf connections

Previously, configured subscribe permissions needed an explicit allow for the $MQTT_sub. prefix used by JetStream consumer subscriptions. These connections can now publish and subscribe on $MQTT.-prefixed subjects without an allow entry, but deny ACLs still apply; regular NATS core clients receive no implicit allowance.

Show release-note lines
- Permissions to `$MQTT.` subscriptions are now handled implicitly, with the exception of `deny` ACLs which still permit restriction (#7637)
github.com/nats-io/nats-server/releases/tag/v2.12.3

TLS cipher-suite selection updated

AffectsTLS connections relying on insecure or newly available cipher suites(Inferred)

New cipher suites from crypto/tls are added automatically, while insecure suites are disabled by default unless allow_insecure_cipher_suites is enabled.

Show release-note lines
Use cipher suites from crypto/tls : New cipher suites are now automatically added. Additionally, insecure cipher suites are disabled by default, but can be allowed when enabling allow_insecure_cipher_suites .
docs.nats.io/release-notes/whats_new/whats_new_212

Connection logging gains identity details

Affectsclient-connection-related and connection-closed logs(Inferred)

Client-connection-related logs include the account name and user; connection-closed logs include the remote server name.

Show release-note lines
Account name and user logging: Any logging related to a client connection, for example when reaching maximum connections or for authentication errors, will now include the account name and user of that client connection. Connection closed logging now includes the remote server name.
docs.nats.io/release-notes/whats_new/whats_new_212

Breaking changes6

JetStream meta layer waits for quorum before replying to peer-remove requests

Affectssetups issuing peer-remove requests handled by the JetStream meta layer(Inferred)

Previously, the meta leader could report success before peer removal reached quorum, leaving the cluster unchanged while users or automated processes believed its size had shrunk.

Show release-note lines
- The meta layer will now only respond to peer remove requests after quorum has been reached (#7581)
github.com/nats-io/nats-server/releases/tag/v2.12.3

Filestore removal accounting follows disk operations

Affectsfilestore message removal(Inferred)

Previously, failed tombstone writes could be silent, while failed secure erasure could leave accounting ahead of on-disk state. Tombstone-write failures now surface as errors.

Show release-note lines
- The filestore now will process message removal on disk before updating accounting, which improves error handling (#7595, #7601)
github.com/nats-io/nats-server/releases/tag/v2.12.3

Filestore and consumer operations propagate message-block load errors

Affectsfilestore and consumer operations that load uncached message blocks(Inferred)

When loading an uncached message block fails, affected operations now return or propagate the error instead of continuing.

Show release-note lines
- Improved error handling within the loading of message blocks if not already cached (#7631)
github.com/nats-io/nats-server/releases/tag/v2.12.3

MQTT maximum payload limit enforced

AffectsMQTT clients with a configured maximum payload size(Inferred)

Previously, an MQTT publish whose total NATS message size exceeded the maximum payload size could be silently accepted instead of failing the connection check. Such publishes now fail that check.

Show release-note lines
- The maximum payload size is now correctly enforced for MQTT clients (#7555, thanks to @yixianOu)
github.com/nats-io/nats-server/releases/tag/v2.12.3

Raft now blocks concurrent membership changes

AffectsSetups performing Raft membership changes, including JetStream peer-removal operations

Previously, a new membership change could be proposed while another was still in progress. Now, the leader drops a concurrent change, and JetStream peer removal can return a member-change-in-progress error.

Evidence“A simple approach based to avoid concurrent membership changes. The leader simply drops a membership change if there is another membership change in progress. A membership is in progress if it has been proposed, but not committed yet.” nats-io/nats-server/pull/7565 ↗
Show release-note lines
- Raft will no longer allow multiple membership changes to take place concurrently (#7565, #7609)
github.com/nats-io/nats-server/releases/tag/v2.12.3

More reliable replicated in-memory stream recovery

Affectsreplicated in-memory streams

After all but one server is restarted, the stream’s data can reliably catch up. During that recovery, every server replicating the stream must be available, not just a quorum.

Show release-note lines
-
Stream/consumer scaleup and reset disk/state protection: The server now has better protections against leader elections based on empty state. This also improves reliability of replicated in-memory streams. Usually a quorum of servers needs to be online and contain data. Now all but one server can be restarted and the in-memory stream's data can reliably be caught back up. However, during such a scenario all servers involved with replication of that stream will need to be available, not just what's needed for quorum. This lets the servers decide the best course of action to preserve all data.
docs.nats.io/release-notes/whats_new/whats_new_212

Important fixes27

  • Invalid subject filter matching fixed
    Affectsinvalid subject filters containing a non-terminating full wildcard

    The invalid filter foo.>.bar could unexpectedly match bar instead of producing zero matches. It no longer matches bar.

    - Invalid subject filters containing non-terminating full wildcard no longer produce unexpected matches (#7585)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Filestore whole-block purges now update subject and schedule tracking
    Affectsfilestores that purge whole message blocks

    When whole message blocks were purged, including to enforce limits, per-subject state could remain unadjusted and scheduled-message metadata could be left behind.

    - When purging whole message blocks, the subject tracking and scheduled messages are now updated correctly (#7593)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Raft quorum counting ignores responses from removed peers
    AffectsRaft groups with peer membership

    When Raft received an append-entry response from a node removed from peer membership, that response could incorrectly count toward quorum without an error.

    - Raft will no longer count responses from peer-removed nodes towards quorum (#7589)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Filestore pending-write loss fixed
    Affectsfilestores configured with AsyncFlush

    A sufficiently long process pause coinciding with syncBlocks at the sync_interval could leave pending writes lost. syncBlocks now flushes pending writes and avoids closing a block file descriptor while writes are pending, preventing that loss.

    - The filestore will no longer unexpectedly lose writes when `AsyncFlush` is enabled after a process pause (#7594)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Raft quorum counting checks leader membership for implicit acknowledgments
    AffectsRaft groups with a leader outside the membership(Inferred)

    Previously, quorum calculations could count the leader’s implicit acknowledgment even when the leader was no longer a member.

    - Raft quorum counting has been refactored so the implicit leader ack is now only counted if still a part of the membership (#7600)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Raft peer state now persists immediately on removal
    AffectsRaft peer removal through ProposePeerRemove

    Previously, a leader that removed a peer through ProposePeerRemove and then restarted could reload stale peer and quorum information and forget committed membership changes.

    - Raft now writes the peer state immediately when handling a peer-remove to ensure the removed peers cannot unexpectedly reappear after a restart (#7602)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Replicated stream discard-policy desynchronization fixed
    Affectsreplicated streams configured with DiscardNewPerSubject and MaxMsgsPerSubject

    During snapshot catch-up, if a message was deleted after the snapshot and a client repeatedly published to its subject while the discard policy blocked it, a catching-up follower could store a different message at that sequence and diverge from the other servers. The leader now rejects messages that fail the discard policy before proposing them to followers, reducing this chance of desynchronization.

    - The `DiscardNewPerSubject` retention policy is now enforced by the leader before proposing rather than by individual replicas, reducing the potential for stream desync (#7607)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Raft rejects removal of the last peer
    AffectsRaft peer-removal operations targeting the last remaining peer

    Previously, the removal could be accepted and leave the cluster in an invalid state; now the peer remains in membership.

    - Raft will no longer allow peer-removing the one remaining peer (#7610)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Filestore message loss during large compactions fixed
    AffectsFilestore blocks undergoing compaction

    When compaction reclaimed over half of a file's storage, a hard kill after truncation but before the compacted bytes were fully written could lose messages. The compacted bytes are now written to a separate file before it atomically replaces the original.

    - Compactions that reclaim over half of the available space now use an atomic write to avoid losing messages if killed (#7627)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Raft peer set no longer readmits removed leaders
    AffectsRaft groups undergoing peer removal and leadership transfer

    When a heartbeat occurred after peer removal was committed but before leadership transfer was processed, the follower could recreate the removed leader in its peer set; it no longer does so in that sequence.

    - Raft groups should no longer readmit a previously removed peer if a heartbeat occurs between the peer removal and the leadership transfer (#7649)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Replicated file-based stream snapshot desynchronization fixed
    Affectsreplicated file-based streams

    A message removal during a stream snapshot could desynchronize the stream, and removal was rejected while the snapshot was in progress.

    - Potential stream desyncs that could happen during stream snapshotting have been fixed (#7655)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Corrupted MQTT retained-message cache bodies fixed
    Affectsclustered MQTT deployments with retained-message caching

    When S-2 had cached a retained message after a matching MQTT subscription started, a newer retained message for the same subject from S-1 could leave extra \r\n or random data in the cached body. The new body is copied into the cache, and trailing \r\n is stripped.

    - A bug which could corrupt retained messages in clustered deployments has been fixed (#7622)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • MQTT QoS2 message delivery after restart fixed
    AffectsMQTT QoS2 subscriptions

    When a subscription was restarted after a server restart, it received neither messages persisted while offline nor new incoming messages. It can now retrieve the persisted messages and receive new ones.

    - A bug where QoS2 messages could not be retrieved after a server restart has been fixed (#7643)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Cross-account MQTT retained messages with subject transforms fixed
    AffectsMQTT retained-message streams sourced from another account with a subject transform

    During recovery, topics and subjects are recreated from the stream message subject with the prefix removed.

    - Retained messages will now work correctly even when sourced from a different account and has a subject transform (#7636)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Duplicate @<subject> suffix in JetStream acknowledgements fixed
    AffectsJetStream setups with gateway and route or leaf traffic and captured stream imports for local subscriptions

    When an acknowledgement reply crossed a gateway, a captured stream import was used for a local subscription, and the reply then went over a route or leaf, the duplicate suffix caused a protocol error.

    - A protocol error caused by an invalid transform of acknowledgement reply subjects when originating from a gateway connection has been fixed (#7579)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • JetStream snapshot processing no longer panics on missing assignments or nodes
    AffectsJetStream snapshot processing for streams with missing assignments or nodes

    It returns errCatchupStreamStopped instead of panicking.

    - A panic when processing snapshots with missing nodes or assignments has been fixed (#7588)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Sequence recovery fixed for almost-empty Filestore streams
    Affectsalmost-empty Filestore streams compacted or purged to sequence 2

    If the server was hard killed after compaction or purge but before writing a tombstone, the sequence could not be recovered. The tombstone is now written to allow recovery in this situation.

    - Tombstones are now correctly written for recovering the sequences after compacting or purging an almost-empty stream to seq 2 (#7627)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Filestore empty-block overwrite fixed
    Affectsfilestore streams

    After SkipMsg(seq), Compact(seq), and SkipMsg(seq+1), another SkipMsg(seq+1) on the empty block could overwrite data at the file head, making the on-disk file appear corrupted and logging indexCacheBuf corrupt record state. That sequence no longer overwrites the block at the wrong offset or produces the corruption error.

    - Combining skip sequences and compactions will no longer overwrite the block at the wrong offset, correcting a `corrupt record state` error (#7627)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Disjoint majorities from Raft peer addition fixed
    AffectsRaft groups adding peers during a partition

    During a partition, adding a peer could leave the Raft group with disjoint majorities.

    - Add peer operations to Raft can no longer result in disjoint majorities (#7632)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Filestore compaction now corrects stale sequences and deletion-map entries
    AffectsFilestore message blocks undergoing compaction

    Compaction could leave mb.last.seq too high and retain deleted tail entries in mb.dmap after the last sequence moved down, causing index mismatches that led to “no idx present” errors and a reload. It now updates the last sequence and cleans up tail deletions as needed.

    - Filestore compaction now correctly adjusts the high and low sequences for a message block, as well as cleaning up the deletion map accordingly (#7634)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Filestore syncBlocks scheduling during snapshots fixed
    Affectsfilestores using syncBlocks

    When syncBlocks ran during a snapshot, it would not run again until the server was restarted.

    - Potential stream desyncs that could happen during stream snapshotting have been fixed (#7655)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Retained-message permission check panic fixed
    AffectsMQTT retained-message permission checks(Inferred)

    During a configuration reload that updates accounts or users, checking stored retained messages could panic if a user lacked the permissions needed to access them, including when no permissions were defined.

    - Fixed a panic that could occur when reloading config if the user did not have permission to access retained messages (#7596)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • MQTT JetStream API mapping through non-JetStream servers fixed
    AffectsMQTT accounts mapped from a non-JetStream leaf account to a JetStream-enabled hub account

    On a leaf account that lacks JetStream but maps JS.API.> to JS.HUB.API.> on a JetStream-enabled hub, requests previously went out unmapped, so the MQTT client could not connect. They now traverse the server with the mapping applied, allowing the client to connect.

    - Fixed account mapping for JetStream API requests when traversing non-JetStream-enabled servers (#7598)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • QoS0 MQTT topics now follow account subject mappings
    AffectsQoS0 MQTT publishers and consumers using account imports/exports with subject mappings

    Previously, a publish on foo/x from account A reached account B as foo/x instead of the mapped bar/x. Consumers now receive the topic corresponding to the mapped subject, such as bar/x.

    - QoS0 messages are now mapped correctly across account imports/exports with subject mappings (#7605)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • MQTT retained-message restoration now checks the message count
    AffectsMQTT retained-message restoration(Inferred)

    After a restart, sequence gaps could make the restore-completion check time out even when all retained messages had been restored.

    - Loading retained messages no longer fails after restarting due to last sequence checks (#7616)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Elastic pointers for file-based stream caches
    Affectsfile-based streams

    During garbage collection and memory pressure, the server can evict filestore caches early, returning memory to the operating system and helping avoid out-of-memory conditions. Depending on the number of assets and publish/access patterns, reported RSS may be lower or higher.

    -
    Elastic pointers in the filestore: File-based streams now use elastic pointers for its write-through caches. This allows the server to better respond during garbage collection, these caches can be evicted early to avoid out-of-memory conditions (see upgrade considerations below).
    -
    With the new elastic pointers in the filestore, it is expected that a NATS Server running 2.12 may show a different memory usage pattern to before. In some systems this may result in lower resident set size (RSS) reported, in others it may result in higher, depending on the number of assets and publish/access patterns.
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Filestore caches freed on memory pressure
    AffectsNATS Server setups using filestore caches

    Freeing caches on demand reduces the chance that sudden utilization spikes cause an out-of-memory kill. When resources allow, caches can be retained more optimistically to improve read access times.

    For the first time, the server will be able to respond to memory pressure by freeing filestore caches on demand and returning the memory to the operating system. This reduces the chance that sudden spikes in utilisation will result in an out-of-memory (OOM) kill. However, this means that the server can more optimistically retain caches in memory when available resources allow in order to facilitate improved read access times.
    docs.nats.io/release-notes/whats_new/whats_new_212

Enhancements13

  • Configurable WebSocket ping interval

    To use A non-zero ping_interval in the websocket block

    ### Added
    General
    - Added WebSocket-specific ping interval configuration with `ping_internal` in the `websocket` block (#7614)
    github.com/nats-io/nats-server/releases/tag/v2.12.3
  • Atomic batch publishing for streams

    To use The stream configuration option AllowAtomicPublish

    -
    Atomic batch publish: The AllowAtomicPublish stream configuration option allows to atomically publish N messages into a stream. This includes support for replicated and non-replicated streams, as well as doing per-message consistency checks prior to committing the batch. See Advanced publishing and ADR-50 .
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Increment/decrement counter semantics for streams

    To use The AllowMsgCounter stream configuration option

    -
    Distributed Counter CRDT: The AllowMsgCounter stream configuration option allows increment/decrement counter semantics on a stream. These counter streams can also be mirrored or aggregated through stream mirroring and sourcing. More information is available in ADR-49 .
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Stream message scheduling

    To use AllowMsgSchedules stream configuration option

    -
    Delayed Message Scheduling: The AllowMsgSchedules stream configuration option allows the scheduling of messages. Users can use this feature for delayed publishing/scheduling of messages. More information is available in ADR-51 .
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Prioritized policy for pull consumers
    - Prioritized pull consumer policy: In addition to the consumer policies like overflow or client pinning, a new prioritized policy has been added. In contrast with the overflow policy, this allows a consumer to receive messages sooner instead of delaying failover, but at the cost of potentially flip-flopping work between clients. See Priority groups and ADR-42 .
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Adds the server_metadata map
    -
    Server metadata: Similar to server_tags which contains a set of tags describing the server, server_metadata is a map containing string keys and values describing metadata of the server.
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Mirroring streams can be promoted to primary
    -
    Promoting mirrors: A stream that's mirroring can now be promoted to be the primary, enabling new disaster recovery methodology. The current primary stream should be deleted or have its configured subjects removed prior to promoting mirrors, before configuring the promoted mirrors to start listening on those subjects. See Disaster recovery .
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Exponential backoff for cluster route and gateway reconnections

    To use Set connect_backoff to true for cluster routes or gateways.

    -
    Exponential backoff on route and gateway connections: Cluster routes and gateways can now use exponential backoff on reconnection attempts by setting connect_backoff . If true , will start exponential backoff at 1 second up to 30 seconds. This can slow down the speed of reconnection but significantly reduces the amount of DNS queries and general connection attempts during server restarts or outages.
    docs.nats.io/release-notes/whats_new/whats_new_212
  • System events from the global account
    System events for the $G account: The global account ( $G ) will now also produce system events, such as connect and disconnect events.
    docs.nats.io/release-notes/whats_new/whats_new_212
  • GOMAXPROCS and GOMEMLIMIT added to NATS server stats
    GOMAXPROCS and GOMEMLIMIT in server stats: The server stats already contained the CPU and memory usage of the server but now also contains the effective Go limits.
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Whole-subject partition(n) and random(n) subject-transform functions
    New subject transforms: partition(n) and random(n) : In addition to partition(n, …) which allows to determine a partition number based on tokens at specified indices, partition(n) and random(n) are convenience functions to create a partition or random number up to n based on the whole subject.
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Leaf-node interest isolation with isolate_leafnode_interest
    Isolated leaf node property: In a large deployment with lots of leaf nodes, propagating east-west interest can result in a lot of traffic, which is wasted if leaf nodes don't need to be able to publish/subscribe to each other directly. Instead of the workaround of setting the cluster name of those leaf nodes to be the same, the isolate_leafnode_interest property can now be used.
    docs.nats.io/release-notes/whats_new/whats_new_212
  • Remote leaf node disabling through configuration reload

    To use Set disabled: true through a configuration reload

    Disable leaf node connection through config reload: This allows disabling a remote leaf node using configuration reload, when using disabled: true . If changed from false to true, a solicited leaf node will be disconnected and will not reconnect. If changed from true to false, the leafnode will be solicited again.
    docs.nats.io/release-notes/whats_new/whats_new_212

Dependency updates8

    8 more, none mentioning security
    • - 1.25.5 (#7604)
    • - github.com/google/go-tpm v0.9.7 (#7578)
    • - github.com/nats-io/nkeys v0.4.12 (#7578)
    • - golang.org/x/crypto v0.45.0 (#7578)
    • - github.com/klauspost/compress v1.18.2 (#7604)
    • - github.com/antithesishq/antithesis-sdk-go v0.5.0-default-no-op (#7604)
    • - golang.org/x/crypto v0.46.0 (#7648)
    • - golang.org/x/sys v0.39.0 (#7648)
    Other changes11
    • Faster sequence scans for subject-filtered sources
      - The scan for the last sourced message sequence when setting up a subject-filtered source is now considerably faster (#7553)
      github.com/nats-io/nats-server/releases/tag/v2.12.3
    • JetStream metalayer stages and deduplicates recovery operations
      - The metalayer will now stage and deduplicate recovery operations at startup, instead of rapidly applying and then undoing conflicting assignments (#7540)
      github.com/nats-io/nats-server/releases/tag/v2.12.3
    • Faster JetStream consumer interest checks
      - Consumer interest checks on interest-based streams are now significantly faster when there are large gaps in interest (#7656)
      github.com/nats-io/nats-server/releases/tag/v2.12.3
    • Clustered stream-creation data race fixed
      - A data race when creating a stream in clustered mode has been fixed (#7586)
      github.com/nats-io/nats-server/releases/tag/v2.12.3
    • Filestore secure erase preserves correct subject tracking
      - The filestore now will process message removal on disk before updating accounting, which improves error handling (#7595, #7601)
      github.com/nats-io/nats-server/releases/tag/v2.12.3
    • Stream health check replica reads protected by a read lock
      - A data race has been fixed in the stream health check (#7619)
      github.com/nats-io/nats-server/releases/tag/v2.12.3
    • Filestore cache expiration after errNoCache
      - Filestore message lookups will now expire the cache if a cache error is encountered (#7630)
      github.com/nats-io/nats-server/releases/tag/v2.12.3
    • Filestore indexes rebuilt and loading retried on sequence mismatch
      - Filestore compaction should no longer result in `no idx present` cache errors (#7634)
      github.com/nats-io/nats-server/releases/tag/v2.12.3
    • Streams and consumers using v2.12 features marked unsupported on downgrade
      -
      Offline assets: When downgrading to an older version, the server can now recognize new features were used and puts the stream and/or consumer into an unsupported/offline mode. For more information, read also the downgrade considerations. More information is available in ADR-44 .
      docs.nats.io/release-notes/whats_new/whats_new_212
    • Replicated streams flush data to disk asynchronously
      -
      Async stream flushing: Replicated streams will now asynchronously flush data to the underlying store on disk, resulting in a significant improvement in performance. Writes to a replicated stream are still persisted synchronously in the Raft log prior to committing them, so the improved performance has no downsides with respect to consistency.
      docs.nats.io/release-notes/whats_new/whats_new_212
    • JetStream strict mode enabled by default
      Strict JetStream API ​
      Starting from version v2.11, the server would start logging the following statement if an invalid JetStream request was received:
      [WRN] Invalid JetStream request '$G > $JS.API.STREAM.CREATE.test-stream': json: unknown field "unknown"
      Starting from version v2.12, the server will not only log, but also return an error to the client as "strict mode" is now enabled by default. This means invalid JetStream requests will be rejected by default.
      If the above log message is observed, please make sure that the application or client is sending correct requests to the server and that NATS client libraries are up-to-date. Strict mode can be temporarily disabled in the server configuration, allowing you more time to fix the issue:
      jetstream {
      strict: false
      }
      docs.nats.io/release-notes/whats_new/whats_new_212

    Summaries are produced by AI, so they can be wrong, and they are provided without warranty.