build(dependencies): update Tomca version (#912) - #913
Merged
mc-nv merged 1 commit intoJul 29, 2026
Merged
Conversation
This was referenced Jul 29, 2026
mc-nv
marked this pull request as ready for review
July 29, 2026 15:11
Greptile SummaryUpdates
Confidence Score: 5/5The PR appears safe to merge because the dependency-only update is consistent across both Java POMs and introduces no identified build or runtime defect. The changed POM entries retain the same artifact and provided scope while consistently advancing the patch version in both generated Java projects. Important Files Changed
Reviews (1): Last reviewed commit: "build(dependencies): update Tomca versio..." | Re-trigger Greptile |
yinggeh
approved these changes
Jul 29, 2026
mc-nv
deleted the
mchornyi/TRI-1601/before-ngc-release-advance-master-branch-to-next-upstream-release
branch
July 29, 2026 17:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does the PR do?
Cherry-picks the Tomcat bump that landed on
r26.07intomainas part of the post-26.07default-branch advance:
tomcat-annotations-api11.0.21 → 11.0.24 in the generated Javaexample and library POMs.
The companion jackson-databind pick from
r26.07(33cc7d5) is not included —mainalready carries identical content via
9a5593f"build(security): bump jackson-databind to2.21.4 and @grpc/grpc-js to 1.14.4".
git cherryflags it becauser26.07'spackage-lock.jsonbase differed, butgit diff origin/main 33cc7d5 --over the threeaffected files is empty.
Checklist
<commit_type>: <Title>Commit Type:
Check the conventional commit type
box here and add the label to the github PR.
Related PRs:
Where should the reviewer start?
Both
pom.xmlfiles — a single<version>line each.Test plan:
Dependency-only change; covered by the existing Java client build in CI.
Caveats:
None.
Background
Release step "[Before NGC Release] Advance master branch to next upstream release" — the
release branch accumulated dependency bumps that
mainmust carry forward.Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
- Relates to: TRI-1601
CI (internal): [#60058404](http://tritonserver.local/ci/pipelines/60058404)