dependabot[bot] opened a new pull request, #34358: URL: https://github.com/apache/beam/pull/34358
Bumps [github.com/nats-io/nats-server/v2](https://github.com/nats-io/nats-server) from 2.10.25 to 2.11.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/nats-io/nats-server/releases";>github.com/nats-io/nats-server/v2's releases</a>.</em></p> <blockquote> <h2>Release v2.11.0</h2> <h2>Changelog</h2> <p>Refer to the <a href="https://docs.nats.io/release-notes/whats_new/whats_new_211";>2.11 Upgrade Guide</a> for backwards compatibility notes with 2.10.x.</p> <h3>Go Version</h3> <ul> <li>1.24.1 (<a href="https://redirect.github.com/nats-io/nats-server/issues/6629";>#6629</a>)</li> </ul> <h3>Dependencies</h3> <ul> <li>golang.org/x/crypto v0.36.0 (<a href="https://redirect.github.com/nats-io/nats-server/issues/6618";>#6618</a>)</li> <li>golang.org/x/sys v0.31.0 (<a href="https://redirect.github.com/nats-io/nats-server/issues/6618";>#6618</a>)</li> <li>golang.org/x/time v0.11.0 (<a href="https://redirect.github.com/nats-io/nats-server/issues/6618";>#6618</a>)</li> <li>github.com/google/go-tpm v0.9.3 (<a href="https://redirect.github.com/nats-io/nats-server/issues/6295";>#6295</a>)</li> <li>github.com/antithesishq/antithesis-sdk-go v0.4.3-default-no-op (<a href="https://redirect.github.com/nats-io/nats-server/issues/6164";>#6164</a>)</li> </ul> <h3>Added</h3> <p>General</p> <ul> <li>Distributed message tracing (<a href="https://redirect.github.com/nats-io/nats-server/issues/5014";>#5014</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/5057";>#5057</a>) <ul> <li>A message with the <code>Nats-Trace-Dest</code> header set to a valid subject will receive events representing what happens to the message as it moves through the system</li> <li>Events contain information such as ingress, subject mapping, stream exports, service imports, egress to subscriptions, routes, gateways or leafnodes</li> <li>An additional <code>Nats-Trace-Only</code> header, if set to <code>true</code>, will produce the same tracing events but will not deliver the message to the final destination</li> </ul> </li> <li>Configuration state digest (<a href="https://redirect.github.com/nats-io/nats-server/issues/4325";>#4325</a>) <ul> <li>A hash of the configuration file can be generated using the <code>-t</code> option on the command line</li> <li>The hash of the currently running configuration file can be seen in the <code>config_digest</code> option in <code>varz</code></li> </ul> </li> <li>Enable scoped users to have templates that are not limited to a subject token (<a href="https://redirect.github.com/nats-io/nats-server/issues/5981";>#5981</a>)</li> <li>New <code>js-meta-only</code> option for <code>healthz</code> healthcheck (<a href="https://redirect.github.com/nats-io/nats-server/issues/6649";>#6649</a>)</li> </ul> <p>JetStream</p> <ul> <li>Per-message TTLs (<a href="https://redirect.github.com/nats-io/nats-server/issues/6272";>#6272</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6354";>#6354</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6363";>#6363</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6370";>#6370</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6376";>#6376</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6385";>#6385</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6400";>#6400</a>) <ul> <li>The <code>Nats-TTL</code> header, provided either as a string duration (<code>1m</code>, <code>30s</code>) or an integer in seconds, will age out the message independently of stream limits</li> <li>More information on this is available in <a href="https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-43.md";>ADR-43</a></li> </ul> </li> <li>Subject delete markers on <code>MaxAge</code> (<a href="https://redirect.github.com/nats-io/nats-server/issues/6378";>#6378</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6389";>#6389</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6393";>#6393</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6400";>#6400</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6404";>#6404</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6428";>#6428</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6432";>#6432</a>) <ul> <li>The <code>SubjectDeleteMarkerTTL</code> stream configuration option determines whether to place marker messages and how long they should live for</li> <li>The marker message will have a <code>Nats-Marker-Reason</code> header explaining which limit caused the marker to be left behind</li> <li>More information on this is available in <a href="https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-43.md";>ADR-43</a></li> </ul> </li> <li>Pull consumer priority groups with pinning and overflow (<a href="https://redirect.github.com/nats-io/nats-server/issues/5814";>#5814</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6078";>#6078</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/6081";>#6081</a>) <ul> <li>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</li> <li>The <code>PriorityGroups</code> and <code>PriorityPolicy</code> options in the consumer configuration control the policy</li> <li>More information on this is available in <a href="https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-42.md";>ADR-42</a></li> </ul> </li> <li>Consumer pausing (<a href="https://redirect.github.com/nats-io/nats-server/issues/5066";>#5066</a>) <ul> <li>The <code>PauseUntil</code> consumer configuration option and <code>$JS.API.CONSUMER.PAUSE</code> endpoint suspends message delivery to the consumer until the time specified is reached, after which point it will resume automatically</li> </ul> </li> <li>Asset versioning (<a href="https://redirect.github.com/nats-io/nats-server/issues/5850";>#5850</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/5855";>#5855</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/5857";>#5857</a>) <ul> <li>More information on this is available in <a href="https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-44.md";>ADR-44</a></li> </ul> </li> <li>Multi-get directly from a stream (<a href="https://redirect.github.com/nats-io/nats-server/issues/5107";>#5107</a>) <ul> <li>More information on this is available in <a href="https://github.com/nats-io/nats-architecture-and-design/blob/main/adr/ADR-31.md";>ADR-31</a></li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/nats-io/nats-server/commit/99e836e9afca6fce007094c44af434dd7afde02d";><code>99e836e</code></a> Release v2.11.0</li> <li><a href="https://github.com/nats-io/nats-server/commit/71b9b45269960abf2183ef55f71b73c5402950de";><code>71b9b45</code></a> Updates to NATS Server Tests GHA pipeline (<a href="https://redirect.github.com/nats-io/nats-server/issues/6692";>#6692</a>)</li> <li><a href="https://github.com/nats-io/nats-server/commit/3f97b339e16810f879fe1a9013f2df6ab2267d56";><code>3f97b33</code></a> Updates to NATS Server Tests GHA pipeline</li> <li><a href="https://github.com/nats-io/nats-server/commit/68dbdcc450b80da7ee63fd944a56ffc7e25f919b";><code>68dbdcc</code></a> Release v2.11.0-RC.5</li> <li><a href="https://github.com/nats-io/nats-server/commit/23927873c337f34280c06bed2ddb0fb56f142c7f";><code>2392787</code></a> Fix timing inconsistency between <code>Nats-TTL</code> and <code>MaxAge</code> timers (<a href="https://redirect.github.com/nats-io/nats-server/issues/6690";>#6690</a>)</li> <li><a href="https://github.com/nats-io/nats-server/commit/00ea7876c951c6db6f177b482b66a6fef1a49bac";><code>00ea787</code></a> Fix timing inconsistency between <code>Nats-TTL</code> and <code>MaxAge</code> timers</li> <li><a href="https://github.com/nats-io/nats-server/commit/78d477f00de1d3a024ff3f20174137a82abfc0ad";><code>78d477f</code></a> Proposed subject delete markers (<a href="https://redirect.github.com/nats-io/nats-server/issues/6689";>#6689</a>)</li> <li><a href="https://github.com/nats-io/nats-server/commit/5bbdd87abd91d8a6c92f00d060b3a4c11e7be8ac";><code>5bbdd87</code></a> Add unit tests modelling TTL and rollup behaviour with and without <code>MaxAge</code></li> <li><a href="https://github.com/nats-io/nats-server/commit/db521664ef59d7f6ed7d51525daf349b35d63b2d";><code>db52166</code></a> Test clustered subject delete marker ordering</li> <li><a href="https://github.com/nats-io/nats-server/commit/7a1f5b92b369fdfd61457cceb0bcf6133fcc4a7c";><code>7a1f5b9</code></a> Proposed subject delete markers</li> <li>Additional commits viewable in <a href="https://github.com/nats-io/nats-server/compare/v2.10.25...v2.11.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@beam.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
