dependabot[bot] opened a new pull request, #36105: URL: https://github.com/apache/beam/pull/36105
Bumps [github.com/nats-io/nats-server/v2](https://github.com/nats-io/nats-server) from 2.11.6 to 2.11.9. <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.9</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.7 (<a href="https://redirect.github.com/nats-io/nats-server/issues/7273";>#7273</a>)</li> </ul> <h3>Dependencies</h3> <ul> <li>golang.org/x/time v0.13.0 (<a href="https://redirect.github.com/nats-io/nats-server/issues/7273";>#7273</a>)</li> <li>golang.org/x/sys v0.36.0 (<a href="https://redirect.github.com/nats-io/nats-server/issues/7273";>#7273</a>)</li> </ul> <h3>Improved</h3> <p>JetStream</p> <ul> <li>Offline assets support (<a href="https://redirect.github.com/nats-io/nats-server/issues/7158";>#7158</a>) <ul> <li>Server version 2.12 will introduce new features that would otherwise break a 2.11 server after a downgrade. The server now reports the streams/consumers as offline and unsupported, keeping the data safe, but allowing to either delete the asset or upgrade back to the supported version without changes to the data itself.</li> </ul> </li> <li>The <code>raftz</code> endpoint now reports the cluster traffic account (<a href="https://redirect.github.com/nats-io/nats-server/issues/7186";>#7186</a>)</li> <li>The stream info and consumer info endpoints now return <code>leader_since</code> (<a href="https://redirect.github.com/nats-io/nats-server/issues/7189";>#7189</a>)</li> <li>The stream info and consumer info endpoints now return <code>system_account</code> and <code>traffic_account</code> (<a href="https://redirect.github.com/nats-io/nats-server/issues/7193";>#7193</a>)</li> <li>The <code>jsz</code> monitoring endpoint now returns <code>system_account</code> and <code>traffic_account</code> (<a href="https://redirect.github.com/nats-io/nats-server/issues/7193";>#7193</a>)</li> </ul> <h3>Fixed</h3> <p>General</p> <ul> <li>Fix a panic that could happen at startup if building from source using non-Git version control (<a href="https://redirect.github.com/nats-io/nats-server/issues/7178";>#7178</a>)</li> <li>Fix an issue where issuing an account JWT update with a connection limit could cause older clients to be disconnected instead of newer ones (<a href="https://redirect.github.com/nats-io/nats-server/issues/7181";>#7181</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/7185";>#7185</a>)</li> <li>Route connections with invalid credentials will no longer rapidly reconnect (<a href="https://redirect.github.com/nats-io/nats-server/issues/7200";>#7200</a>)</li> <li>Allow a <code>default_sentinel</code> JWT from a scoped signing key instead of requiring it to solely be a bearer token for auth callout (<a href="https://redirect.github.com/nats-io/nats-server/issues/7217";>#7217</a>)</li> <li>Subject interest would not always be propagated for leaf nodes when daisy chaining imports/exports (<a href="https://redirect.github.com/nats-io/nats-server/issues/7255";>#7255</a>)</li> <li>Subject interest would sometimes be lost if the leaf node is a spoke (<a href="https://redirect.github.com/nats-io/nats-server/issues/7259";>#7259</a>)</li> <li>Lowering the max connections limit should no longer result in streams losing interest (<a href="https://redirect.github.com/nats-io/nats-server/issues/7258";>#7258</a>)</li> </ul> <p>JetStream</p> <ul> <li>The <code>Nats-TTL</code> header will now be correct if the subject delete marker TTL overwrites it (<a href="https://redirect.github.com/nats-io/nats-server/issues/7177";>#7177</a>)</li> <li>In operator mode, the <code>cluster_traffic</code> state for an account is now restored correctly when enabling JetStream at startup (<a href="https://redirect.github.com/nats-io/nats-server/issues/7191";>#7191</a>)</li> <li>A potential data race during a consumer create or update when reading its paused state has been fixed (<a href="https://redirect.github.com/nats-io/nats-server/issues/7201";>#7201</a>)</li> <li>A race condition that could allow creating a consumer with more replicas than the stream has been fixed (<a href="https://redirect.github.com/nats-io/nats-server/issues/7202";>#7202</a>)</li> <li>A race condition that could allow creating the same stream with different configurations has been fixed (<a href="https://redirect.github.com/nats-io/nats-server/issues/7210";>#7210</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/7212";>#7212</a>)</li> <li>Raft will now correctly reject delayed entries from an old leader when catching up in the meantime (<a href="https://redirect.github.com/nats-io/nats-server/issues/7209";>#7209</a>, <a href="https://redirect.github.com/nats-io/nats-server/issues/7239";>#7239</a>)</li> <li>Raft will now also limit the amount of cached in-memory entries as the leader, avoiding excessive memory usage (<a href="https://redirect.github.com/nats-io/nats-server/issues/7233";>#7233</a>)</li> <li>A potential race condition delaying shutdown if a stream/consumer monitor goroutine was not started (<a href="https://redirect.github.com/nats-io/nats-server/issues/7211";>#7211</a>)</li> <li>A benign underflow when using an infinite (-1) MaxDeliver for consumers (<a href="https://redirect.github.com/nats-io/nats-server/issues/7216";>#7216</a>)</li> <li>A potential panic to send a leader elected advisory when shutting down before completing startup (<a href="https://redirect.github.com/nats-io/nats-server/issues/7246";>#7246</a>)</li> <li>Stopping a stream should no longer wait indefinitely if the consumer monitor goroutine wasn’t stopped (<a href="https://redirect.github.com/nats-io/nats-server/issues/7249";>#7249</a>)</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/3c10f160f4d7dc09074b457ffa38f5d786501bf1";><code>3c10f16</code></a> Release v2.11.9</li> <li><a href="https://github.com/nats-io/nats-server/commit/e7ee3f182a7046408cf1750302825b35df5b695e";><code>e7ee3f1</code></a> Cherry-picks for 2.11.9 (<a href="https://redirect.github.com/nats-io/nats-server/issues/7286";>#7286</a>)</li> <li><a href="https://github.com/nats-io/nats-server/commit/009def03a41cc92bca142aea67dfdfc8b2c2abdf";><code>009def0</code></a> fix url encoding for ocsp requests</li> <li><a href="https://github.com/nats-io/nats-server/commit/39d48b8d6400ac92f25603fe4da964cfb125a065";><code>39d48b8</code></a> Release v2.11.9-RC.3</li> <li><a href="https://github.com/nats-io/nats-server/commit/cfd563e6e05ec2a20ba5a71c5476b10afe7b6b54";><code>cfd563e</code></a> Cherry-picks for 2.11.9-RC.3 (<a href="https://redirect.github.com/nats-io/nats-server/issues/7252";>#7252</a>)</li> <li><a href="https://github.com/nats-io/nats-server/commit/5c202683336d812cc010bfe47e25dc8d7d89c329";><code>5c20268</code></a> [FIXED] Empty placement triggers move request</li> <li><a href="https://github.com/nats-io/nats-server/commit/a0875d45e114516cc06d5d5180ef5079f5ebaf5b";><code>a0875d4</code></a> Fix internal JS clients disconnecting on account updates</li> <li><a href="https://github.com/nats-io/nats-server/commit/94f4d992ba0add9ccfdab764c2072ffe1aec81d5";><code>94f4d99</code></a> Add TestJetStreamClusterAccountMaxConnectionsReconnect</li> <li><a href="https://github.com/nats-io/nats-server/commit/3464f3fee76b7fc3fe064820bead08960b6e1658";><code>3464f3f</code></a> Update to Go 1.24.7</li> <li><a href="https://github.com/nats-io/nats-server/commit/343e983e0d7b1f0deaa556d54851473360d50b09";><code>343e983</code></a> Update GHA workflow dependencies</li> <li>Additional commits viewable in <a href="https://github.com/nats-io/nats-server/compare/v2.11.6...v2.11.9";>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
