deps: update vulnerable modules - #5831
Conversation
Upgrade go-jose, x/crypto, x/net, x/text, and gRPC to fixed compatible versions. Keep the already-fixed AWS eventstream and S3 versions unchanged.
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What problem does this PR solve?
Issue Number: close #5830
TiCDC master still selected older go-jose, x/crypto, x/net, x/text, and gRPC
versions affected by reported security advisories.
What is changed and how it works?
v4.1.4.v0.53.0, x/net tov0.56.0, and x/text tov0.39.0.v1.82.1.AWS eventstream
v1.7.8and S3v1.97.3were already fixed on master andremain unchanged.
GO-2026-5932has no known fixed x/crypto version, but theaffected
x/crypto/openpgppackage is absent from TiCDC's complete packagegraph.
Check List
Tests
GOPROXY=https://proxy.golang.org,direct make unit_testmake cdcGOPROXY=https://proxy.golang.org,direct make checkQuestions
Will it cause performance regression or break compatibility?
No expected regression. This changes only module metadata and passes the full
build, unit-test, and presubmit targets.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note