Bump github.com/nats-io/nats-server/v2 from 2.10.25 to 2.11.0 in /sdks

[dependabot]

Bumps github.com/nats-io/nats-server/v2 from 2.10.25 to 2.11.0.

Release notes

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

Release v2.11.0

Changelog

Refer to the 2.11 Upgrade Guide for backwards compatibility notes with 2.10.x.

Go Version

• 1.24.1 (#6629)

Dependencies

• golang.org/x/crypto v0.36.0 (#6618)
• golang.org/x/sys v0.31.0 (#6618)
• golang.org/x/time v0.11.0 (#6618)
• github.com/google/go-tpm v0.9.3 (#6295)
• github.com/antithesishq/antithesis-sdk-go v0.4.3-default-no-op (#6164)

Added

General

• Distributed message tracing (#5014, #5057)
  • A message with the Nats-Trace-Dest header set to a valid subject will receive events representing what happens to the message as it moves through the system
  • Events contain information such as ingress, subject mapping, stream exports, service imports, egress to subscriptions, routes, gateways or leafnodes
  • An additional Nats-Trace-Only header, if set to true, will produce the same tracing events but will not deliver the message to the final destination
• Configuration state digest (#4325)
  • A hash of the configuration file can be generated using the -t option on the command line
  • The hash of the currently running configuration file can be seen in the config_digest option in varz
• Enable scoped users to have templates that are not limited to a subject token (#5981)
• New js-meta-only option for healthz healthcheck (#6649)

JetStream

• Per-message TTLs (#6272, #6354, #6363, #6370, #6376, #6385, #6400)
  • The Nats-TTL header, provided either as a string duration (1m, 30s) or an integer in seconds, will age out the message independently of stream limits
  • More information on this is available in ADR-43
• Subject delete markers on MaxAge (#6378, #6389, #6393, #6400, #6404, #6428, #6432)
  • The SubjectDeleteMarkerTTL stream configuration option determines whether to place marker messages and how long they should live for
  • The marker message will have a Nats-Marker-Reason header explaining which limit caused the marker to be left behind
  • More information on this is available in ADR-43
• Pull consumer priority groups with pinning and overflow (#5814, #6078, #6081)
  • Allows patterns such as one consumer receiving all messages, but handing over to a second consumer if the first one fails, or groups of clients accessing the same consumer should have different priorities
  • The PriorityGroups and PriorityPolicy options in the consumer configuration control the policy
  • More information on this is available in ADR-42
• Consumer pausing (#5066)
  • The PauseUntil consumer configuration option and $JS.API.CONSUMER.PAUSE endpoint suspends message delivery to the consumer until the time specified is reached, after which point it will resume automatically
• Asset versioning (#5850, #5855, #5857)
  • More information on this is available in ADR-44
• Multi-get directly from a stream (#5107)
  • More information on this is available in ADR-31

... (truncated)

Commits

• 99e836e Release v2.11.0
• 71b9b45 Updates to NATS Server Tests GHA pipeline (#6692)
• 3f97b33 Updates to NATS Server Tests GHA pipeline
• 68dbdcc Release v2.11.0-RC.5
• 2392787 Fix timing inconsistency between Nats-TTL and MaxAge timers (#6690)
• 00ea787 Fix timing inconsistency between Nats-TTL and MaxAge timers
• 78d477f Proposed subject delete markers (#6689)
• 5bbdd87 Add unit tests modelling TTL and rollup behaviour with and without MaxAge
• db52166 Test clustered subject delete marker ordering
• 7a1f5b9 Proposed subject delete markers
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @jrmccluskey for label go.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).