Skip to content

v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241) #22281

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
ti-chi-bot merged 1 commit into from
Jan 8, 2026
Merged

v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241) #22281

ti-chi-bot merged 1 commit into from
Jan 8, 2026

Conversation

@ti-chi-bot
Copy link
Member

@ti-chi-bot ti-chi-bot commented Jan 8, 2026

This is an automated cherry-pick of #22241

First-time contributors' checklist

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot ti-chi-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-7.1 This PR is cherry-picked to release-7.1 from a source PR. labels Jan 8, 2026
@ti-chi-bot ti-chi-bot mentioned this pull request Jan 8, 2026
Merged
14 tasks
@ti-chi-bot
Copy link
Member Author

ti-chi-bot commented Jan 8, 2026

@Oreoxmt 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
Copy link

ti-chi-bot bot commented Jan 8, 2026

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

Details

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
Copy link

gemini-code-assist bot commented Jan 8, 2026

Summary of Changes

Hello @ti-chi-bot, I'm Gemini Code Assist1! 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 systematically updates all download links within the TiDB documentation from the old 'pingcap.org' domain to the new 'pingcap.com' domain. This change ensures that users are consistently directed to the correct and up-to-date resources for downloading TiDB components, tools, and related monitoring services. Additionally, some links have been refactored to use a version placeholder for better future maintainability.

Highlights

  • Domain Update: All download URLs in the documentation have been updated from 'download.pingcap.org' to 'download.pingcap.com' to reflect the current domain.
  • Version Templating: Several download links now utilize a '{{{ .tidb-version }}}' placeholder for dynamic versioning, enhancing maintainability and future-proofing the documentation.
  • Automated Cherry-Pick: This pull request is an automated cherry-pick, indicating the propagation of these changes from an upstream branch.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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[bot]
gemini-code-assist bot reviewed Jan 8, 2026
View reviewed changes
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates download URLs from pingcap.org to pingcap.com across several documentation files. While most changes are correct, the automated cherry-pick process has introduced merge conflicts in multiple files. These conflicts must be resolved to ensure the documentation renders correctly. I have left comments on each file with a conflict, suggesting the likely resolution.

dm/quick-start-create-task.md Outdated
Comment on lines 76 to 80
<<<<<<< HEAD
wget https://download.pingcap.org/tidb-community-server-v7.1.5-linux-amd64.tar.gz
=======
wget https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
Copy link

@gemini-code-assist gemini-code-assist bot Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This file contains merge conflict markers that need to be resolved. Based on the context of the pull request, the intended line is likely wget https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz.

Suggested change
<<<<<<< HEAD
wget https://download.pingcap.org/tidb-community-server-v7.1.5-linux-amd64.tar.gz
=======
wget https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
wget https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz

pd-control.md Outdated
Comment on lines 31 to 35
<<<<<<< HEAD
> `{version}` in the link indicates the version number of TiDB. For example, the download link for `v7.1.5` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-server-v7.1.5-linux-amd64.tar.gz`.
=======
> `{version}` in the link indicates the version number of TiDB. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz`.
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
Copy link

@gemini-code-assist gemini-code-assist bot Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This file contains merge conflict markers that need to be resolved. Based on the context of the pull request, the intended line is likely > {version} in the link indicates the version number of TiDB. For example, the download link for v{{{ .tidb-version }}} in the amd64 architecture is https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz..

Suggested change
<<<<<<< HEAD
> `{version}` in the link indicates the version number of TiDB. For example, the download link for `v7.1.5` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-server-v7.1.5-linux-amd64.tar.gz`.
=======
> `{version}` in the link indicates the version number of TiDB. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz`.
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
> `{version}` in the link indicates the version number of TiDB. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz`.

production-deployment-using-tiup.md Outdated
Comment on lines 101 to 105
<<<<<<< HEAD
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.1.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v7.1.0-linux-amd64.tar.gz`.
=======
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.5.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v7.5.0-linux-amd64.tar.gz`.
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
Copy link

@gemini-code-assist gemini-code-assist bot Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This file contains merge conflict markers that need to be resolved. Based on the context of the pull request, the intended line is likely > {version} in the link indicates the version number of TiDB and {arch} indicates the architecture of the system, which can be amd64 or arm64. For example, the download link for v7.5.0 in the amd64 architecture is https://download.pingcap.com/tidb-community-toolkit-v7.5.0-linux-amd64.tar.gz..

Suggested change
<<<<<<< HEAD
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.1.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v7.1.0-linux-amd64.tar.gz`.
=======
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.5.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v7.5.0-linux-amd64.tar.gz`.
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.5.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v7.5.0-linux-amd64.tar.gz`.

tidb-binlog/get-started-with-tidb-binlog.md Outdated
Comment on lines 45 to 49
<<<<<<< HEAD
curl -L https://download.pingcap.org/tidb-community-server-v7.1.5-linux-amd64.tar.gz | tar xzf -
=======
curl -L https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz | tar xzf -
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
Copy link

@gemini-code-assist gemini-code-assist bot Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This file contains merge conflict markers that need to be resolved. Based on the context of the pull request, the intended line is likely curl -L https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz | tar xzf -.

Suggested change
<<<<<<< HEAD
curl -L https://download.pingcap.org/tidb-community-server-v7.1.5-linux-amd64.tar.gz | tar xzf -
=======
curl -L https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz | tar xzf -
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
curl -L https://download.pingcap.com/tidb-community-server-v{{{ .tidb-version }}}-linux-amd64.tar.gz | tar xzf -

upgrade-monitoring-services.md Outdated
Comment on lines 39 to 43
<<<<<<< HEAD
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.1.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v7.1.0-linux-amd64.tar.gz`.
=======
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`.
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
Copy link

@gemini-code-assist gemini-code-assist bot Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This file contains merge conflict markers that need to be resolved. Based on the context of the pull request, the intended line is likely > {version} in the link indicates the version number of TiDB and {arch} indicates the architecture of the system, which can be amd64 or arm64. For example, the download link for v{{{ .tidb-version }}} in the amd64 architecture is https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz..

Suggested change
<<<<<<< HEAD
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.1.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v7.1.0-linux-amd64.tar.gz`.
=======
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`.
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`.

upgrade-monitoring-services.md Outdated
Comment on lines 92 to 96
<<<<<<< HEAD
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.1.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v7.1.0-linux-amd64.tar.gz`.
=======
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`.
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
Copy link

@gemini-code-assist gemini-code-assist bot Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This file contains merge conflict markers that need to be resolved. Based on the context of the pull request, the intended line is likely > {version} in the link indicates the version number of TiDB and {arch} indicates the architecture of the system, which can be amd64 or arm64. For example, the download link for v{{{ .tidb-version }}} in the amd64 architecture is https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz..

Suggested change
<<<<<<< HEAD
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v7.1.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v7.1.0-linux-amd64.tar.gz`.
=======
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`.
>>>>>>> e6cc410e73 (v6.5-v8.1: update download URL from pingcap.org to pingcap.com (#22241))
> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v{{{ .tidb-version }}}-linux-amd64.tar.gz`.

@Oreoxmt Oreoxmt force-pushed the cherry-pick-22241-to-release-7.1 branch from c7fbbc0 to 80c6661 Compare January 8, 2026 10:54
@Oreoxmt
Copy link
Collaborator

Oreoxmt commented Jan 8, 2026

/approve

@Oreoxmt
Copy link
Collaborator

Oreoxmt commented Jan 8, 2026

/unhols

@Oreoxmt
Copy link
Collaborator

Oreoxmt commented Jan 8, 2026

/unhold

@ti-chi-bot ti-chi-bot bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 8, 2026
@ti-chi-bot
Copy link

ti-chi-bot bot commented Jan 8, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Oreoxmt

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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 ti-chi-bot bot added the approved label Jan 8, 2026
@ti-chi-bot ti-chi-bot bot merged commit 28b688e into pingcap:release-7.1 Jan 8, 2026
9 checks passed
@ti-chi-bot ti-chi-bot bot deleted the cherry-pick-22241-to-release-7.1 branch January 8, 2026 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Oreoxmt Oreoxmt Oreoxmt approved these changes

+1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@Oreoxmt Oreoxmt

Labels

approved lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-7.1 This PR is cherry-picked to release-7.1 from a source PR.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ti-chi-bot @Oreoxmt