Skip to content

Bump the maven-minor-2-x group with 10 updates - #4311

Merged
github-actions[bot] merged 2 commits into
2.xfrom
dependabot/maven/2.x/maven-minor-2-x-63d9606b30
Sep 10, 2026
Merged

Bump the maven-minor-2-x group with 10 updates#4311
github-actions[bot] merged 2 commits into
2.xfrom
dependabot/maven/2.x/maven-minor-2-x-63d9606b30

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 9, 2026

Copy link
Copy Markdown
Contributor

Bumps the maven-minor-2-x group with 10 updates:

Package From To
ch.qos.logback:logback-core 1.3.15 1.3.16
org.apache.groovy:groovy-bom 4.0.27 4.0.33
org.apache.activemq:activemq-broker 6.3.1 6.3.2
ch.qos.logback:logback-classic 1.3.15 1.3.16
co.elastic.clients:elasticsearch-java 9.5.2 9.5.3
org.elasticsearch.client:elasticsearch-rest-client 9.5.2 9.5.3
org.mongodb:bson 5.10.0 5.11.0
org.mongodb:mongodb-driver-core 5.10.0 5.11.0
org.mongodb:mongodb-driver-sync 5.10.0 5.11.0
org.springframework.cloud:spring-cloud-context 4.3.0 4.3.3

Updates ch.qos.logback:logback-core from 1.3.15 to 1.3.16

Commits

Updates org.apache.groovy:groovy-bom from 4.0.27 to 4.0.33

Commits

Updates org.apache.activemq:activemq-broker from 6.3.1 to 6.3.2

Release notes

Sourced from org.apache.activemq:activemq-broker's releases.

Apache ActiveMQ 6.3.2

What's Changed

Performance

Fixes

Dependencies

Tasks

Full Changelog: apache/activemq@activemq-6.3.1...activemq-6.3.2

Commits

Updates ch.qos.logback:logback-core from 1.3.15 to 1.3.16

Commits

Updates ch.qos.logback:logback-classic from 1.3.15 to 1.3.16

Commits

Updates co.elastic.clients:elasticsearch-java from 9.5.2 to 9.5.3

Release notes

Sourced from co.elastic.clients:elasticsearch-java's releases.

v9.5.3

What's Changed

Full Changelog: elastic/elasticsearch-java@v9.5.2...v9.5.3

Commits

Updates org.elasticsearch.client:elasticsearch-rest-client from 9.5.2 to 9.5.3

Release notes

Sourced from org.elasticsearch.client:elasticsearch-rest-client's releases.

Elasticsearch 9.5.3

Downloads: https://elastic.co/downloads/elasticsearch Release notes: https://www.elastic.co/docs/release-notes/elasticsearch#elasticsearch-9.5.3-release-notes

Commits

Updates org.elasticsearch.client:elasticsearch-rest-client from 9.5.2 to 9.5.3

Release notes

Sourced from org.elasticsearch.client:elasticsearch-rest-client's releases.

Elasticsearch 9.5.3

Downloads: https://elastic.co/downloads/elasticsearch Release notes: https://www.elastic.co/docs/release-notes/elasticsearch#elasticsearch-9.5.3-release-notes

Commits

Updates org.mongodb:bson from 5.10.0 to 5.11.0

Release notes

Sourced from org.mongodb:bson's releases.

Java Driver 5.11.0 (August 28, 2026)

What's Changed

CSFLE/QE Http proxies notes

  • The driver always negotiates TLS with the KMS host itself, using the SSLContext configured for the KMS provider. Implementations must not negotiate TLS with the KMS host; doing so would let an intermediary read the key material in transit.
  • An implementation may use TLS for its own connection to the intermediary, in which case it returns an SSLSocket and the driver layers the KMS host's TLS session on top of it.
  • Ownership of the returned socket passes to the driver, which closes it when the KMS request completes. A socket that is never returned must be closed by the implementation.
  • Applicable only to the synchronous driver. The reactive streams driver rejects(RuntimeException) a configured callback.

Code example

Code example uses only the JDK API , so no HTTP client dependency is required. If you use your own HTTP client, it must return the tunnelled socket without negotiating TLS with the KMS host

First define the callback

private static final String PROXY_HOST = "proxy.example.com";
private static final int PROXY_PORT = 8080;
private static final int TIMEOUT_MILLIS = 10_000;

// Routes every KMS request through an HTTP proxy using the HTTP CONNECT method

// refer to the docs https://www.rfc-editor.org/info/rfc9110/#section-9.3.6

KmsConnectCallback proxyCallback = context -> {

Socket socket = new Socket();

try {

// 1. Connect to the proxy, not to the KMS host.

socket.connect(new InetSocketAddress(PROXY_HOST, PROXY_PORT), TIMEOUT_MILLIS);

socket.setSoTimeout(TIMEOUT_MILLIS);


    // 2. Ask the proxy to open a tunnel to the KMS host the driver wants to reach. Only the
    //    driver knows which host that is, so always take it from the context rather than
    //    hard-coding it.
    String target = context.getHost() + ":" + context.getPort();
    String connectRequest = "CONNECT " + target + " HTTP/1.1\r\n"
            + "Host: " + target + "\r\n"
            // If the proxy requires authentication, add the appropriate header, for example:
            // + "Proxy-Authorization: Basic " + base64("user:password") + "\r\n"
            + "\r\n";
    socket.getOutputStream().write(connectRequest.getBytes(StandardCharsets.US_ASCII));

// 3. Check the proxy accepted the tunnel before handing the socket back.
checkProxyAcceptedTunnel(socket.getInputStream());



} catch (IOException | RuntimeException e) {

// The driver never received this socket, so it cannot close it for you.

socket.close();

throw e;




</tr></table>

... (truncated)

Commits

Updates org.mongodb:mongodb-driver-core from 5.10.0 to 5.11.0

Release notes

Sourced from org.mongodb:mongodb-driver-core's releases.

Java Driver 5.11.0 (August 28, 2026)

What's Changed

CSFLE/QE Http proxies notes

  • The driver always negotiates TLS with the KMS host itself, using the SSLContext configured for the KMS provider. Implementations must not negotiate TLS with the KMS host; doing so would let an intermediary read the key material in transit.
  • An implementation may use TLS for its own connection to the intermediary, in which case it returns an SSLSocket and the driver layers the KMS host's TLS session on top of it.
  • Ownership of the returned socket passes to the driver, which closes it when the KMS request completes. A socket that is never returned must be closed by the implementation.
  • Applicable only to the synchronous driver. The reactive streams driver rejects(RuntimeException) a configured callback.

Code example

Code example uses only the JDK API , so no HTTP client dependency is required. If you use your own HTTP client, it must return the tunnelled socket without negotiating TLS with the KMS host

First define the callback

private static final String PROXY_HOST = "proxy.example.com";
private static final int PROXY_PORT = 8080;
private static final int TIMEOUT_MILLIS = 10_000;

// Routes every KMS request through an HTTP proxy using the HTTP CONNECT method

// refer to the docs https://www.rfc-editor.org/info/rfc9110/#section-9.3.6

KmsConnectCallback proxyCallback = context -> {

Socket socket = new Socket();

try {

// 1. Connect to the proxy, not to the KMS host.

socket.connect(new InetSocketAddress(PROXY_HOST, PROXY_PORT), TIMEOUT_MILLIS);

socket.setSoTimeout(TIMEOUT_MILLIS);


    // 2. Ask the proxy to open a tunnel to the KMS host the driver wants to reach. Only the
    //    driver knows which host that is, so always take it from the context rather than
    //    hard-coding it.
    String target = context.getHost() + &quot;:&quot; + context.getPort();
    String connectRequest = &quot;CONNECT &quot; + target + &quot; HTTP/1.1\r\n&quot;
            + &quot;Host: &quot; + target + &quot;\r\n&quot;
            // If the proxy requires authentication, add the appropriate header, for example:
            // + &quot;Proxy-Authorization: Basic &quot; + base64(&quot;user:password&quot;) + &quot;\r\n&quot;
            + &quot;\r\n&quot;;
    socket.getOutputStream().write(connectRequest.getBytes(StandardCharsets.US_ASCII));

// 3. Check the proxy accepted the tunnel before handing the socket back.
checkProxyAcceptedTunnel(socket.getInputStream());



} catch (IOException | RuntimeException e) {

// The driver never received this socket, so it cannot close it for you.

socket.close();

throw e;




</tr></table>

... (truncated)

Commits

Updates org.mongodb:mongodb-driver-sync from 5.10.0 to 5.11.0

Release notes

Sourced from org.mongodb:mongodb-driver-sync's releases.

Java Driver 5.11.0 (August 28, 2026)

What's Changed

CSFLE/QE Http proxies notes

  • The driver always negotiates TLS with the KMS host itself, using the SSLContext configured for the KMS provider. Implementations must not negotiate TLS with the KMS host; doing so would let an intermediary read the key material in transit.
  • An implementation may use TLS for its own connection to the intermediary, in which case it returns an SSLSocket and the driver layers the KMS host's TLS session on top of it.
  • Ownership of the returned socket passes to the driver, which closes it when the KMS request completes. A socket that is never returned must be closed by the implementation.
  • Applicable only to the synchronous driver. The reactive streams driver rejects(RuntimeException) a configured callback.

Code example

Code example uses only the JDK API , so no HTTP client dependency is required. If you use your own HTTP client, it must return the tunnelled socket without negotiating TLS with the KMS host

First define the callback

private static final String PROXY_HOST = "proxy.example.com";
private static final int PROXY_PORT = 8080;
private static final int TIMEOUT_MILLIS = 10_000;

// Routes every KMS request through an HTTP proxy using the HTTP CONNECT method

// refer to the docs https://www.rfc-editor.org/info/rfc9110/#section-9.3.6

KmsConnectCallback proxyCallback = context -> {

Socket socket = new Socket();

try {

// 1. Connect to the proxy, not to the KMS host.

socket.connect(new InetSocketAddress(PROXY_HOST, PROXY_PORT), TIMEOUT_MILLIS);

socket.setSoTimeout(TIMEOUT_MILLIS);


    // 2. Ask the proxy to open a tunnel to the KMS host the driver wants to reach. Only the
    //    driver knows which host that is, so always take it from the context rather than
    //    hard-coding it.
    String target = context.getHost() + &quot;:&quot; + context.getPort();
    String connectRequest = &quot;CONNECT &quot; + target + &quot; HTTP/1.1\r\n&quot;
            + &quot;Host: &quot; + target + &quot;\r\n&quot;
            // If the proxy requires authentication, add the appropriate header, for example:
            // + &quot;Proxy-Authorization: Basic &quot; + base64(&quot;user:password&quot;) + &quot;\r\n&quot;
            + &quot;\r\n&quot;;
    socket.getOutputStream().write(connectRequest.getBytes(StandardCharsets.US_ASCII));

// 3. Check the proxy accepted the tunnel before handing the socket back.
checkProxyAcceptedTunnel(socket.getInputStream());



} catch (IOException | RuntimeException e) {

// The driver never received this socket, so it cannot close it for you.

socket.close();

throw e;




</tr></table>

... (truncated)

Commits

Updates org.mongodb:mongodb-driver-core from 5.10.0 to 5.11.0

Release notes

Sourced from org.mongodb:mongodb-driver-core's releases.

Java Driver 5.11.0 (August 28, 2026)

What's Changed

CSFLE/QE Http proxies notes

  • The driver always negotiates TLS with the KMS host itself, using the SSLContext configured for the KMS provider. Implementations must not negotiate TLS with the KMS host; doing so would let an intermediary read the key material in transit.
  • An implementation may use TLS for its own connection to the intermediary, in which case it returns an SSLSocket and the driver layers the KMS host's TLS session on top of it.
  • Ownership of the returned socket passes to the driver, which closes it when the KMS request completes. A socket that is never returned must be closed by the implementation.
  • Applicable only to the synchronous driver. The reactive streams driver rejects(RuntimeException) a configured callback.

Code example

Code example uses only the JDK API , so no HTTP client dependency is required. If you use your own HTTP client, it must return the tunnelled socket without negotiating TLS with the KMS host

First define the callback

private static final String PROXY_HOST = "proxy.example.com";
private static final int PROXY_PORT = 8080;
private static final int TIMEOUT_MILLIS = 10_000;

// Routes every KMS request through an HTTP proxy using the HTTP CONNECT method

// refer to the docs https://www.rfc-editor.org/info/rfc9110/#section-9.3.6

KmsConnectCallback proxyCallback = context -> {

Socket socket = new Socket();

try {

// 1. Connect to the proxy, not to the KMS host.

socket.connect(new InetSocketAddress(PROXY_HOST, PROXY_PORT), TIMEOUT_MILLIS);

socket.setSoTimeout(TIMEOUT_MILLIS);


    // 2. Ask the proxy to open a tunnel to the KMS host the driver wants to reach. Only the
    //    driver knows which host that is, so always take it from the context rather than
    //    hard-coding it.
    String target = context.getHost() + &quot;:&quot; + context.getPort();
    String connectRequest = &quot;CONNECT &quot; + target + &quot; HTTP/1.1\r\n&quot;
            + &quot;Host: &quot; + target + &quot;\r\n&quot;
            // If the proxy requires authentication, add the appropriate header, for example:
            // + &quot;Proxy-Authorization: Basic &quot; + base64(&quot;user:password&quot;) + &quot;\r\n&quot;
            + &quot;\r\n&quot;;
    socket.getOutputStream().write(connectRequest.getBytes(StandardCharsets.US_ASCII));

// 3. Check the proxy accepted the tunnel before handing the socket back.
checkProxyAcceptedTunnel(socket.getInputStream());



} catch (IOException | RuntimeException e) {

// The driver never received this socket, so it cannot close it for you.

socket.close();

throw e;




</tr></table>

... (truncated)

Commits

Updates org.mongodb:mongodb-driver-sync from 5.10.0 to 5.11.0

Release notes

Sourced from org.mongodb:mongodb-driver-sync's releases.

Java Driver 5.11.0 (August 28, 2026)

What's Changed

CSFLE/QE Http proxies notes

  • The driver always negotiates TLS with the KMS host itself, using the SSLContext configured for the KMS provider. Implementations must not negotiate TLS with the KMS host; doing so would let an intermediary read the key material in transit.
  • An implementation may use TLS for its own connection to the intermediary, in which case it returns an SSLSocket and the driver layers the KMS host's TLS session on top of it.
  • Ownership of the returned socket passes to the driver, which closes it when the KMS request completes. A socket that is never returned must be closed by the implementation.
  • Applicable only to the synchronous driver. The reactive streams driver rejects(RuntimeException) a configured callback.

Code example

Code example uses only the JDK API , so no HTTP client dependency is required. If you use your own HTTP client, it must return the tunnelled socket without negotiating TLS with the KMS host

First define the callback

private static final String PROXY_HOST = "proxy.example.com";
private static final int PROXY_PORT = 8080;
private static final int TIMEOUT_MILLIS = 10_000;

// Routes every KMS request through an HTTP proxy using the HTTP CONNECT method

// refer to the docs https://www.rfc-editor.org/info/rfc9110/#section-9.3.6

KmsConnectCallback proxyCallback = context -> {

Socket socket = new Socket();

try {

// 1. Connect to the proxy, not to the KMS host.

socket.connect(new InetSocketAddress(PROXY_HOST, PROXY_PORT), TIMEOUT_MILLIS);

socket.setSoTimeout(TIMEOUT_MILLIS);


    // 2. Ask the proxy to open a tunnel to the KMS host the driver wants to reach. Only the
    //    driver knows which host that is, so always take it from the context rather than
    //    hard-coding it.
    String target = context.getHost() + &quot;:&quot; + context.getPort();
    String connectRequest = &quot;CONNECT &quot; + target + &quot; HTTP/1.1\r\n&quot;
            + &quot;Host: &quot; + target + &quot;\r\n&quot;
            // If the proxy requires authentication, add the appropriate header, for example:
            // + &quot;Proxy-Authorization: Basic &quot; + base64(&quot;user:password&quot;) + &quot;\r\n&quot;
            + &quot;\r\n&quot;;
    socket.getOutputStream().write(connectRequest.getBytes(StandardCharsets.US_ASCII));

// 3. Check the proxy accepted the tunnel before handing the socket back.
checkProxyAcceptedTunnel(socket.getInputStream());



} catch (IOException | RuntimeException e) {

// The driver never received this socket, so it cannot close it for you.

socket.close();

throw e;




</tr></table>

... (truncated)

Commits

Updates org.springframework.cloud:spring-cloud-context from 4.3.0 to 4.3.3

Release notes

Sourced from org.springframework.cloud:spring-cloud-context's releases.

4.3.3

❤️ Contributors

Thank you to all the contributors who worked on this release:

@​dependabot[bot]

What's Changed

Full Changelog: spring-cloud/spring-cloud-commons@v4.3.2...v4.3.3

4.3.2

🐞 Bug Fixes

  • Properties decryption not working correctly when they are on a list (yaml) #1253

❤️ Contributors

Thank you to all the contributors who worked on this release:

@​dependabot[bot]

4.3.1

❤️ Contributors

Thank you to all the contributors who worked on this release:

@​dependabot[bot]

What's Changed

... (truncated)

Commits
  • abe9961 Update SNAPSHOT to 4.3.3
  • 598c1c1 Merge pull request #1693 from spring-cloud/dependabot/npm_and_yarn/docs/4.3.x...
  • 83d9abe Bump @​springio/antora-extensions from 1.14.11 to 1.14.12 in /docs
  • 25913b1 Bumping versions
  • e01eae5 Runs test on random port
  • af85f20 Merge pull request #1690 from spring-cloud/dependabot/maven/4.3.x/org.apache....
  • ff2f8ca Bump org.apache.maven:maven-resolver-provider from 3.9.15 to 3.9.16
  • c693965 Upgrading antora to 3.2.0-alpha.12
  • d13e9c3 Bump bouncycastle-bcprov-jdk18on version to 1.80.2
  • 3ee3533 Merge pull request #1686 from spring-cloud/dependabot/maven/4.3.x/org.apache....
  • 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the maven-minor-2-x group with 10 updates
6478c26 
Bumps the maven-minor-2-x group with 10 updates:

| Package | From | To |
| --- | --- | --- |
| [ch.qos.logback:logback-core](https://github.com/qos-ch/logback) | `1.3.15` | `1.3.16` |
| [org.apache.groovy:groovy-bom](https://github.com/apache/groovy) | `4.0.27` | `4.0.33` |
| [org.apache.activemq:activemq-broker](https://github.com/apache/activemq) | `6.3.1` | `6.3.2` |
| [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) | `1.3.15` | `1.3.16` |
| [co.elastic.clients:elasticsearch-java](https://github.com/elastic/elasticsearch-java) | `9.5.2` | `9.5.3` |
| [org.elasticsearch.client:elasticsearch-rest-client](https://github.com/elastic/elasticsearch) | `9.5.2` | `9.5.3` |
| [org.mongodb:bson](https://github.com/mongodb/mongo-java-driver) | `5.10.0` | `5.11.0` |
| [org.mongodb:mongodb-driver-core](https://github.com/mongodb/mongo-java-driver) | `5.10.0` | `5.11.0` |
| [org.mongodb:mongodb-driver-sync](https://github.com/mongodb/mongo-java-driver) | `5.10.0` | `5.11.0` |
| [org.springframework.cloud:spring-cloud-context](https://github.com/spring-cloud/spring-cloud-commons) | `4.3.0` | `4.3.3` |


Updates `ch.qos.logback:logback-core` from 1.3.15 to 1.3.16
- [Release notes](https://github.com/qos-ch/logback/releases)
- [Commits](qos-ch/logback@v_1.3.15...v_1.3.16)

Updates `org.apache.groovy:groovy-bom` from 4.0.27 to 4.0.33
- [Commits](https://github.com/apache/groovy/commits)

Updates `org.apache.activemq:activemq-broker` from 6.3.1 to 6.3.2
- [Release notes](https://github.com/apache/activemq/releases)
- [Commits](apache/activemq@activemq-6.3.1...activemq-6.3.2)

Updates `ch.qos.logback:logback-core` from 1.3.15 to 1.3.16
- [Release notes](https://github.com/qos-ch/logback/releases)
- [Commits](qos-ch/logback@v_1.3.15...v_1.3.16)

Updates `ch.qos.logback:logback-classic` from 1.3.15 to 1.3.16
- [Release notes](https://github.com/qos-ch/logback/releases)
- [Commits](qos-ch/logback@v_1.3.15...v_1.3.16)

Updates `co.elastic.clients:elasticsearch-java` from 9.5.2 to 9.5.3
- [Release notes](https://github.com/elastic/elasticsearch-java/releases)
- [Changelog](https://github.com/elastic/elasticsearch-java/blob/main/CHANGELOG.md)
- [Commits](elastic/elasticsearch-java@v9.5.2...v9.5.3)

Updates `org.elasticsearch.client:elasticsearch-rest-client` from 9.5.2 to 9.5.3
- [Release notes](https://github.com/elastic/elasticsearch/releases)
- [Changelog](https://github.com/elastic/elasticsearch/blob/main/docs/changelog.yml)
- [Commits](elastic/elasticsearch@v9.5.2...v9.5.3)

Updates `org.elasticsearch.client:elasticsearch-rest-client` from 9.5.2 to 9.5.3
- [Release notes](https://github.com/elastic/elasticsearch/releases)
- [Changelog](https://github.com/elastic/elasticsearch/blob/main/docs/changelog.yml)
- [Commits](elastic/elasticsearch@v9.5.2...v9.5.3)

Updates `org.mongodb:bson` from 5.10.0 to 5.11.0
- [Release notes](https://github.com/mongodb/mongo-java-driver/releases)
- [Commits](mongodb/mongo-java-driver@r5.10.0...r5.11.0)

Updates `org.mongodb:mongodb-driver-core` from 5.10.0 to 5.11.0
- [Release notes](https://github.com/mongodb/mongo-java-driver/releases)
- [Commits](mongodb/mongo-java-driver@r5.10.0...r5.11.0)

Updates `org.mongodb:mongodb-driver-sync` from 5.10.0 to 5.11.0
- [Release notes](https://github.com/mongodb/mongo-java-driver/releases)
- [Commits](mongodb/mongo-java-driver@r5.10.0...r5.11.0)

Updates `org.mongodb:mongodb-driver-core` from 5.10.0 to 5.11.0
- [Release notes](https://github.com/mongodb/mongo-java-driver/releases)
- [Commits](mongodb/mongo-java-driver@r5.10.0...r5.11.0)

Updates `org.mongodb:mongodb-driver-sync` from 5.10.0 to 5.11.0
- [Release notes](https://github.com/mongodb/mongo-java-driver/releases)
- [Commits](mongodb/mongo-java-driver@r5.10.0...r5.11.0)

Updates `org.springframework.cloud:spring-cloud-context` from 4.3.0 to 4.3.3
- [Release notes](https://github.com/spring-cloud/spring-cloud-commons/releases)
- [Changelog](https://github.com/spring-cloud/spring-cloud-commons/blob/main/release-train-settings.xml)
- [Commits](spring-cloud/spring-cloud-commons@v4.3.0...v4.3.3)

---
updated-dependencies:
- dependency-name: ch.qos.logback:logback-core
  dependency-version: 1.3.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-2-x
- dependency-name: org.apache.groovy:groovy-bom
  dependency-version: 4.0.33
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-2-x
- dependency-name: org.apache.activemq:activemq-broker
  dependency-version: 6.3.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-2-x
- dependency-name: ch.qos.logback:logback-core
  dependency-version: 1.3.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-2-x
- dependency-name: ch.qos.logback:logback-classic
  dependency-version: 1.3.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-2-x
- dependency-name: co.elastic.clients:elasticsearch-java
  dependency-version: 9.5.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: maven-minor-2-x
- dependency-name: org.elasticsearch.client:elasticsearch-rest-client
  dependency-version: 9.5.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: maven-minor-2-x
- dependency-name: org.elasticsearch.client:elasticsearch-rest-client
  dependency-version: 9.5.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: maven-minor-2-x
- dependency-name: org.mongodb:bson
  dependency-version: 5.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-2-x
- dependency-name: org.mongodb:mongodb-driver-core
  dependency-version: 5.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-2-x
- dependency-name: org.mongodb:mongodb-driver-sync
  dependency-version: 5.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-2-x
- dependency-name: org.mongodb:mongodb-driver-core
  dependency-version: 5.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-2-x
- dependency-name: org.mongodb:mongodb-driver-sync
  dependency-version: 5.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: maven-minor-2-x
- dependency-name: org.springframework.cloud:spring-cloud-context
  dependency-version: 4.3.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: maven-minor-2-x
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added dependencies Related to third party dependency updates or migrations java Pull requests that update Java code labels Sep 9, 2026
@github-actions
github-actions Bot enabled auto-merge (squash) September 9, 2026 13:06
@github-actions
github-actions Bot merged commit 8c50211 into 2.x Sep 10, 2026
12 checks passed
@github-actions
github-actions Bot deleted the dependabot/maven/2.x/maven-minor-2-x-63d9606b30 branch September 10, 2026 01:28
@github-project-automation github-project-automation Bot moved this from Approved to Merged in Log4j pull request tracker Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ramanathan1504 ramanathan1504 ramanathan1504 approved these changes

Assignees

No one assigned

Labels

dependencies Related to third party dependency updates or migrations java Pull requests that update Java code

Projects

Log4j pull request tracker
Status: Merged

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@ramanathan1504