Skip to content

[ISSUE #15451] Upgrade compatible dependencies for v2.x#15501

Merged
KomachiSion merged 1 commit into
alibaba:v2.x-developfrom
KomachiSion:codex/2x-issue-15451-dependency-analysis
Jul 13, 2026
Merged

[ISSUE #15451] Upgrade compatible dependencies for v2.x#15501
KomachiSion merged 1 commit into
alibaba:v2.x-developfrom
KomachiSion:codex/2x-issue-15451-dependency-analysis

Conversation

@KomachiSion

Copy link
Copy Markdown
Collaborator

What is the purpose of the change

For #15451

Upgrade dependency versions that are compatible with the v2.x JDK8 baseline to reduce known vulnerability reports without moving v2.x to Spring Boot 3 / JDK17+.

Brief changelog

  • Upgrade gRPC Java from 1.64.2 to 1.75.0.
  • Upgrade Jackson from 2.16.2 to 2.18.9.
  • Upgrade Spring Security from 5.8.15 to 5.8.16, the latest available 5.8.x line on Maven Central.
  • Keep incompatible major-line upgrades out of v2.x, such as Spring Framework 6 / Spring Boot 3, Derby 10.17.x, and Logback 1.3.x.

Verifying this change

  • JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_411.jdk/Contents/Home mvn -B clean package apache-rat:check findbugs:findbugs -DskipTests -e -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
  • mvn -B -pl client -am -DskipTests dependency:tree -Dincludes=io.grpc:grpc-netty-shaded,com.fasterxml.jackson.core:jackson-databind,com.fasterxml.jackson.core:jackson-core,org.springframework.security:spring-security-crypto
  • Verified the JDK8 standalone startup path with the generated server jar after the gRPC 1.75.0 adjustment.

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
  • Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module. Dependency-only change; covered by dependency tree, full package check, and startup verification.
  • Run mvn -B clean package apache-rat:check findbugs:findbugs -Dmaven.test.skip=true to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.

@KomachiSion
KomachiSion merged commit 71b46af into alibaba:v2.x-develop Jul 13, 2026
2 checks passed
@KomachiSion KomachiSion added this to the 2.5.3 milestone Jul 13, 2026
@KomachiSion KomachiSion added the dependencies Pull requests that update a dependency file label Jul 13, 2026
@KomachiSion
KomachiSion deleted the codex/2x-issue-15451-dependency-analysis branch July 13, 2026 12:35
@github-actions

Copy link
Copy Markdown

Thanks for your this PR. 🙏
Please check again for your PR changes whether contains any usage/api/configuration change such as Add new API , Add new configuration, Change default value of configuration.
If so, please add or update documents(markdown type) in docs/next/ for repository nacos-group/nacos-group.github.io


感谢您提交的PR。 🙏
请再次查看您的PR内容,确认是否包含任何使用方式/API/配置参数的变更,如:新增API新增配置参数修改默认配置等操作。
如果是,请确保在提交之前,在仓库nacos-group/nacos-group.github.io中的docs/next/目录下添加或更新文档(markdown格式)。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant