kv: trigger release-nextgen-202603 CI without downstream cache

[lcwangchao]

What problem does this PR solve?

Issue Number: ref #70067

Problem Summary:

The Bazel coverage CI for #70067 has repeatedly been killed. This PR provides a minimal control change on the same release branch to check whether the CI can complete independently of #70067's diff and without relying on cached downstream build artifacts.

What changed and how does it work?

Add a cache-probe constant to the widely imported pkg/kv production package. The constant changes the package export data and compiled archive without adding runtime behavior, invalidating downstream Bazel action caches for packages that depend on pkg/kv.

This PR is only a CI control and is not intended to be merged.

Check List

Tests

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

  • I checked and no code files have been changed.

bazel build --noremote_upload_local_results //pkg/kv:kv

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

Summary by CodeRabbit

• Chores
  • Added release tracking metadata for the next-generation CI cache rollout.
  • No changes to application functionality, interfaces, or user workflows.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds the exported ReleaseNextGenCICacheProbe constant to the kv package with value release-nextgen-202603.

Changes

Next-generation CI cache probe

Layer / File(s)	Summary
Cache probe constant pkg/kv/kv.go	Exports ReleaseNextGenCICacheProbe with the value release-nextgen-202603.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: jmpotato

Poem

A rabbit found a cache key bright,
It stamped the release just right.
“Next-gen hops are ready to go!”
Through kv paths, the probe will glow.
Squeak! CI bounds ahead in sight.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly states the KV cache-probe CI trigger change and matches the PR's main purpose.
Description check	✅ Passed	The description follows the template, includes an issue reference, problem summary, changes, tests, side effects, and release note.

✨ 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.}

[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 hicqu 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

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

[lcwangchao]

/test pull-unit-test-next-gen

[codecov]

Codecov Report

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

⚠️ Current head 85df47c differs from pull request most recent head cce8072

Please upload reports for the commit cce8072 to get more accurate results.

Additional details and impacted files

@@                     Coverage Diff                     @@
##             release-nextgen-202603     #70144   +/-   ##
===========================================================
  Coverage                          ?   76.1893%           
===========================================================
  Files                             ?       1937           
  Lines                             ?     541219           
  Branches                          ?          0           
===========================================================
  Hits                              ?     412351           
  Misses                            ?     128868           
  Partials                          ?          0           

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

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

Components	Coverage Δ
dumpling	61.5065% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	48.7678% <0.0000%> (?)

🚀 New features to boost your workflow:

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

[lcwangchao]

/hold for this is only a test PR

[lcwangchao]

/test pull-unit-test-next-gen

[ti-chi-bot]

@lcwangchao: The following test 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-integration-realcluster-test-next-gen	cce8072	link	true	/test pull-integration-realcluster-test-next-gen

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.