[Task] Add cross-repo compatibility test strategy

[Aias00]

Description

Background

Once Java client code is split into shenyu-client-java, normal unit tests in either repository are not enough to guarantee compatibility. We need a strategy for cross-repo compatibility testing.

The goal is to define how main repo changes and client repo changes are tested together before release.

Tasks

• Identify the minimum cross-repo compatibility scenarios.
• Define how main repo CI can test against a selected client artifact version.
• Define how client repo CI can test against a selected main repo admin/bootstrap version.
• Decide whether tests should run on every PR, nightly, or before release.
• Define required Docker/Testcontainers/local process setup.
• Define compatibility matrix dimensions: client version, main repo version, JDK version.
• Propose a minimal first implementation plan.

Suggested Scenarios

• Client registers Spring MVC metadata to admin.
• Client sends heartbeat and admin keeps the instance alive.
• Bootstrap receives route data and can proxy a request.
• New admin accepts old client registration.
• New client can register with the current stable admin.

Expected Output

A test strategy document or design proposal.

Acceptance Criteria

• The proposal distinguishes PR-level tests from release-level tests.
• The proposal includes a minimal implementable first phase.
• The proposal identifies expected runtime cost and CI impact.

Task List

No response

[github-actions]

👋 Hello @yuluo-yx

A new issue has been opened by @Aias00:

• Title: [Task] Add cross-repo compatibility test strategy
• Link: [Task] Add cross-repo compatibility test strategy #6367

Please review when you have time. Thank you! 🙏