build(deps): bump github.com/nats-io/nats-server/v2 from 2.14.5 to 2.15.0

[dependabot]

Bumps github.com/nats-io/nats-server/v2 from 2.14.5 to 2.15.0.

Release notes

Sourced from github.com/nats-io/nats-server/v2's releases.

Release v2.15.0

Changelog

Refer to the 2.15 Upgrade Guide for backwards compatibility notes with 2.14.x. This release also contains all changes up to and including v2.14.7.

Go Version

• 1.27.1 (#8551)

Added

JetStream

• Desired state metalayer (#8432, #8437, #8439, #8443, #8452, #8460, #8476, #8576, #8598, #8602, #8603)
  • A new desired state reconciliation engine for streams and consumers considerably improves the safety and reliability of asset moves and scales
  • Updating the placement or replication factor midway through an existing scale/move operation, cancelling an in-flight scale/move, or peer-removing is now much safer
  • ADR: https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-62.md
• Cancel stream move endpoint (#8476)
  • An in-flight scale/move operation on a stream can be cancelled and the asset returned to its original placement using the new $JS.API.STREAM.CANCEL_MOVE endpoint
  • ADR: https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-62.md
• Evacuate endpoints (#8443)
  • The new $JS.API.SERVER.EVACUATE endpoint can safely evacuate streams, and any consumers on those streams, from a node
  • The new $JS.API.STREAM.PEER.EVACUATE.* endpoint can safely evacuate a peer, and any consumers on that peer, from a stream
  • These operations combined allow for maintenance operations with full transfer of data and state without having to peer-remove first
  • ADR: https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-62.md
• Metalayer rescue for disaster recovery (#8408)
  • The new $JS.API.META.RESCUE endpoint can temporarily lower the quorum-needed for the metalayer, in order to facilitate the recovery of a system where nodes have been permanently lost and the metalayer cannot reach quorum
  • ADR: https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-61.md
• Stream backup and restore v2 (#7882, #8584, #8591, #8604)
  • A new backup format for stream snapshots which reads out per-message rather than per-block
  • The new backup format also now correctly includes non-replicated consumers on follower nodes
  • ADR: https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-63.md
• Detect source stream recreation (#8384)
  • The server now detects a source stream being recreated, restarting the sourcing back from the beginning, ensuring new messages are sourced
• Stream source indexing (#8282, #8516, #8283)
  • Restarts and leader changes previously required expensive backward scans through the stream to find the last sourced indices. These are now persisted in an index for instant lookup.
• Domain-prefixed JS API in system account (#8429)
  • When a system account is bridged between the hub and a leaf node, the domain-prefixed JS API can now be used to operate on the leaf node while directly connected to the hub

Changed

JetStream

• Streams now have a default limit of 1000 consumers, unless max_consumers is specified in the stream config or account limits (#8337, #8566)
  • Applications planning to use a large number of consumers on a stream should configure max_consumers in the stream config or account limits to an appropriately high number
  • The server-wide default of 1000 can be overridden by setting default_max_consumers in the JetStream limits, or can be disabled by setting to -1
  • This limit does not affect existing consumers and will not result in consumer deletions, only the creation of new consumers is prevented
• Sync changes for replicated streams (#8447)
  • When the sync_interval is set to always, replicated streams now sync their WAL entries but no longer sync upper stream layer writes
  • The synced log allows the stream to recover safely, but removing unnecessary syncs from the upper stream layer dramatically improves performance

... (truncated)

Commits

• eb76367 Release v2.15.0
• 8f3f31b [FIXED] Config reload disconnects operator mode clients sending an nkey (#8609)
• 7d77240 [FIXED] Stream scale down into a missing account tier was accepted (#8608)
• e46d21f [FIXED] Concurrent account updates invalidating stream imports (#8610)
• 2ecd77a De-flake TestJetStreamClusterHardKillAfterStreamAdd
• 901df78 De-flake TestJetStreamClusterAccountMaxConnectionsReconnect
• e133a1f De-flake TestJetStreamClusterMessageTTLCatchup
• 2990f6c [FIXED] Concurrent account updates invalidating stream imports
• 51fd55f De-flake TestJWTImportsOnServerRestartAndClientsReconnect
• 6a82cf9 De-flake TestNoRaceRouteSendSubs
• Additional commits viewable in compare view

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

🟢 Coverage ∅ diff coverage

Metric	Results
Coverage variation	Report missing for 17d665b1
Diff coverage	✅ ∅ diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (17d665b)	Report Missing	Report Missing	Report Missing
Head commit (afed081)	89062	21501	24.14%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#3576)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

¹ Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[rhafer]

@dependabot rebase