cloudbase-ai opened a new pull request, #7498:
URL: https://github.com/apache/shenyu/pull/7498

   ## Problem And Result
   
   Prepare the main-repository cutover for Motan, tracked in 
https://github.com/apache/shenyu/issues/7295. The runtime is already absent 
from main; remove stale Motan distribution LICENSE ownership metadata.
   
   Receiving PR: https://github.com/apache/shenyu-plugin-store/pull/8.
   
   ## Validation
   
   - Full store reactor: `./mvnw -B -ntp clean verify -Dapi.version=1.44` 
passed, with Checkstyle and RAT enabled.
   - Current cutover API: `./mvnw -B -ntp -pl 
shenyu-plugin/shenyu-plugin-proxy/shenyu-plugin-motan,shenyu-spring-boot-starter-plugin/shenyu-spring-boot-starter-plugin-motan
 -am verify -Dshenyu.version=2.7.2-SNAPSHOT -Dapi.version=1.44` passed.
   - Both ShenYu API lines, `2.7.0` and `2.7.2-SNAPSHOT`, run 19 Motan plugin 
tests (including actual provider-to-HTTP-gateway scenarios) and 5 starter 
tests. No skipped tests.
   - Minimal starter consumer class-loading check passed after all four vendor 
libraries were made transitive runtime dependencies.
   - Main cleanup only removes four obsolete distribution LICENSE references 
plus the unused Motan license document; `git diff --check` passed. No gateway 
implementation is removed in this main PR.
   - Logs: `motan/final-full-verify.log`, `motan/final-cutover-verify.log`, and 
`motan/final-*` in the local migration evidence directory.
   
   
   ## Blocked Cutover
   
   This PR intentionally remains DRAFT. Merge only after the receiving 
prerequisites, CI/E2E, artifact release/ownership, and documented 
upgrade/rollback gates are satisfied. This PR does not close the migration 
issue or authorize dual publication of the same Maven version.
   
   Roadmap: https://github.com/apache/shenyu/issues/7306.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to