Release-testing: v8.5.5 tiflow repo CI trigger

[stevenayu]

What problem does this PR solve?

Issue Number: close #xxx

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Questions

Will it cause performance regression or break compatibility?

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

Release note

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

[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 LGTMed and approved by the reviewers firstly.
2. For pull requests to TiDB-x branches, it must have no failed tests.
3. AFTER it has lgtm and approved labels, please wait for the cherry-pick merging approval from triage owners.

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 kubernetes-sigs/prow repository.

[gemini-code-assist]

Summary of Changes

Hello @stevenayu, 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 serves primarily as a mechanism to initiate the CI pipeline for release testing of version "v8.5.5" of the "tiflow" repository. The code modification itself is trivial, involving the addition of a single blank line, and does not introduce any functional changes to the codebase.

Highlights

• CI Trigger: This pull request contains a minimal, non-functional change intended to trigger the Continuous Integration (CI) pipeline for release testing of "v8.5.5" within the "tiflow" repository.

🧠 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]

Code Review

This pull request introduces a minor cosmetic change by adding a blank line to the license header in tests/utils/checksum_checker/main.go. As indicated by the title, this change appears to be intended to trigger the CI pipeline for release testing. The change has no functional impact and looks fine for its purpose.

[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 gmhdbjd 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.

Details

Needs approval from an approver in each of these files:

• OWNERS
• dm/OWNERS

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (release-8.5@62c10c0). Learn more about missing BASE report.

Additional details and impacted files

Components	Coverage Δ
cdc	57.9003% <0.0000%> (?)
dm	48.6869% <0.0000%> (?)
engine	50.6885% <0.0000%> (?)

Flag	Coverage Δ
unit	53.4676% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

@@               Coverage Diff                @@
##             release-8.5     #12471   +/-   ##
================================================
  Coverage               ?   53.4676%           
================================================
  Files                  ?       1004           
  Lines                  ?     137023           
  Branches               ?          0           
================================================
  Hits                   ?      73263           
  Misses                 ?      58305           
  Partials               ?       5455           

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[stevenayu]

/retest

[stevenayu]

/test ?

[ti-chi-bot]

@stevenayu: The following commands are available to trigger required jobs:

/test pull-cdc-integration-kafka-test

/test pull-cdc-integration-mysql-test

/test pull-cdc-integration-pulsar-test

/test pull-cdc-integration-storage-test

/test pull-dm-compatibility-test

/test pull-dm-integration-test

/test pull-verify

Use /test all to run all jobs.

Details

In response to this:

/test ?

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.

[stevenayu]

/test pull-cdc-integration-kafka-test pull-cdc-integration-mysql-test pull-cdc-integration-pulsar-test pull-cdc-integration-storage-test pull-dm-compatibility-test pull-dm-integration-test pull-verify

This is an automated do-test comment triggered by a release-testing robot.
Every evening at 11 PM, if there are updates to the PR in the repo, then perform the `/test CI FT` test.
Commented on: 2026-01-06 16:37:42.

[stevenayu]

/retest

[stevenayu]

/retest

[stevenayu]

/retest

[stevenayu]

/retest

[stevenayu]

/retest

[stevenayu]

/retest