*: bump jwt (#12343)

[ti-chi-bot]

This is an automated cherry-pick of #12343

What problem does this PR solve?

Issue Number: close #12340 ref #12249

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

`None`.

[ti-chi-bot]

@wk989898 This PR has conflicts, I have hold it.
Please resolve them or ask others to resolve them, then comment /unhold to remove the hold label.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign wizardxiao for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

@ti-chi-bot: ## If you want to know how to resolve it, please read the guide in TiDB Dev Guide.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[gemini-code-assist]

Summary of Changes

Hello @ti-chi-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a significant dependency update across the project's Go modules. The core change involves migrating the golang-jwt/jwt library to its major version 5, which often entails API changes and improvements. Alongside this, several other direct and indirect dependencies have been bumped to their latest versions. This automated update aims to ensure the project benefits from the latest features, bug fixes, and security patches provided by its underlying libraries, maintaining overall system health and compatibility.

Highlights

• JWT Library Upgrade: The primary change involves upgrading the golang-jwt/jwt library to its v5 version, specifically updating the import path in cmd/oauth2-server/main.go and the module version in go.mod.
• Dependency Bumps: Numerous other Go module dependencies have been updated in go.mod and go.sum, including apache/pulsar-client-go, aws/aws-sdk-go, go-mysql-org/go-mysql, and go-oauth2/oauth2/v4, among others.
• Automated Update: This pull request is an automated cherry-pick, indicating a routine maintenance update to keep the project's dependencies current and address issue CDC: Outdated third-party component reference #12340.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to update dependencies, notably the jwt library. However, it has introduced unresolved merge conflicts into go.mod and go.sum. These conflict markers are a critical issue that will prevent the project from building and must be resolved. Please fix the merge conflicts in these files and then run go mod tidy to ensure they are in a valid and consistent state.

[gemini-code-assist]

This file contains unresolved merge conflict markers (<<<<<<<, =======, >>>>>>>). This is a critical issue that will cause Go tooling to fail and break the build. Please resolve these conflicts by choosing the correct dependency versions, remove the conflict markers, and then run go mod tidy to clean up the go.mod and go.sum files.

[gemini-code-assist]

Similar to go.mod, this file also contains unresolved merge conflict markers. This will break the build. After resolving the conflicts in go.mod, this file should be regenerated by running go mod tidy. Please ensure all conflict markers are removed.

[ti-chi-bot]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-verify	900188e	link	true	/test pull-verify
pull-dm-integration-test	900188e	link	true	/test pull-dm-integration-test
pull-cdc-integration-mysql-test	900188e	link	true	/test pull-cdc-integration-mysql-test
pull-cdc-integration-pulsar-test	900188e	link	true	/test pull-cdc-integration-pulsar-test
pull-cdc-integration-kafka-test	900188e	link	true	/test pull-cdc-integration-kafka-test
pull-cdc-integration-storage-test	900188e	link	true	/test pull-cdc-integration-storage-test
pull-dm-compatibility-test	900188e	link	true	/test pull-dm-compatibility-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.