ci: match all nextgen release branches in GitHub Actions

[wuhuizuo]

What problem does this PR solve?

Issue Number: Ref #10560

What is changed and how does it work?

ci(actions): match all nextgen release branches

Port the GitHub Actions branch filter update to release-nextgen-202603 by replacing the hardcoded release-nextgen-20250815 workflow filter with release-nextgen-* in:

• .github/workflows/pd-tests.yaml
• .github/workflows/tso-function-test.yaml

This keeps the existing non-nextgen branch coverage unchanged while allowing future nextgen release branches to trigger the same GitHub Actions workflows.

Check List

Tests

• Manual test (add detailed scripts or steps below)
  • git diff --check
  • verified only the two workflow branch filters changed
  • confirmed the nextgen workflow branch filters now use release-nextgen-*

Code changes

• Has the configuration change

Release note

None.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 61c6033d-dbad-494c-8680-cf370a96226f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ti-chi-bot]

Hi @wuhuizuo. Thanks for your PR.

I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[wuhuizuo]

/retest

[ti-chi-bot]

@wuhuizuo: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

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.

[okJiang]

/ok-to-test

[wuhuizuo]

/retest

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (release-nextgen-202603@048f0d8). Learn more about missing BASE report.

Additional details and impacted files

@@                    Coverage Diff                    @@
##             release-nextgen-202603   #10550   +/-   ##
=========================================================
  Coverage                          ?   78.95%           
=========================================================
  Files                             ?      531           
  Lines                             ?    71634           
  Branches                          ?        0           
=========================================================
  Hits                              ?    56557           
  Misses                            ?    11054           
  Partials                          ?     4023           

Flag	Coverage Δ
unittests	78.95% <ø> (?)

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bufferflies, rleungx

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:

• OWNERS [bufferflies,rleungx]

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]

[LGTM Timeline notifier]

Timeline:

• 2026-04-03 03:47:31.82191778 +0000 UTC m=+496057.027277837: ☑️ agreed by bufferflies.
• 2026-04-07 02:38:59.139814811 +0000 UTC m=+837544.345174868: ☑️ agreed by rleungx.

[ti-chi-bot]

@wuhuizuo: 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-unit-test-next-gen-2	81070d1	link	unknown	/test pull-unit-test-next-gen-2
pull-unit-test-next-gen-3	81070d1	link	unknown	/test pull-unit-test-next-gen-3
pull-unit-test-next-gen-1	81070d1	link	unknown	/test pull-unit-test-next-gen-1

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.