Skip to content

Conversation

@ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #20455

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.4 (TiDB 8.4 versions)
  • v8.3 (TiDB 8.3 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)?

  • This PR is translated from:
  • Other reference 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

3pointer and others added 3 commits August 12, 2025 08:23
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
@ti-chi-bot ti-chi-bot added area/br Indicates that the Issue or PR belongs to the area of BR (Backup & Restore). for-release This PR relates to a TiDB release but does not have a tracked feature. lgtm requires-version-specific-changes After cherry-picked, the cherry-picked PR requires further changes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. v9.0-beta.2 This PR/issue applies to TiDB v9.0-beta.2. labels Aug 12, 2025
@qiancai qiancai changed the title log backup: update metafile format (#20455) v8.5.3: log backup: update metafile format (#20455) Aug 12, 2025
@qiancai qiancai added the needs-cherry-pick-master Should cherry pick this PR to master branch. label Aug 12, 2025
@qiancai
Copy link
Collaborator

qiancai commented Aug 14, 2025

/approve

@ti-chi-bot
Copy link

ti-chi-bot bot commented Aug 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

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

The pull request process is described here

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 Aug 14, 2025
@ti-chi-bot ti-chi-bot bot merged commit f25c410 into pingcap:release-8.5 Aug 14, 2025
7 checks passed
@ti-chi-bot ti-chi-bot bot deleted the cherry-pick-20455-to-release-8.5 branch August 14, 2025 06:47
@ti-chi-bot
Copy link
Member Author

In response to a cherrypick label: new pull request created to branch master: #20782.
But this PR has conflicts, please resolve them!

ti-chi-bot added a commit to ti-chi-bot/docs-cn that referenced this pull request Aug 14, 2025
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved area/br Indicates that the Issue or PR belongs to the area of BR (Backup & Restore). for-release This PR relates to a TiDB release but does not have a tracked feature. lgtm needs-cherry-pick-master Should cherry pick this PR to master branch. requires-version-specific-changes After cherry-picked, the cherry-picked PR requires further changes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. v9.0-beta.2 This PR/issue applies to TiDB v9.0-beta.2.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants