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

   ## Problem And Result
   
   Prepare the main-repository cutover for Huawei LTS logging, tracked in 
https://github.com/apache/shenyu/issues/7302. Remove the active 
implementation/starter modules and their build, default-distribution, and 
current configuration metadata. Retain documented core API identifiers needed 
by external plugins, historical upgrade SQL, and release notes.
   
   Receiving PR: https://github.com/apache/shenyu-plugin-store/pull/13.
   
   ## Validation
   
   - Full store `./mvnw -B -ntp clean verify -Dapi.version=1.44` passed with 
Checkstyle/RAT enabled and no skipped tests.
   - 16 plugin tests and 3 starter tests passed, including actual gateway HTTP 
requests with local SDK-boundary fixtures. No cloud account credentials are 
required; live cloud-service delivery is outside this contract.
   - Main `PluginEnumTest`: 50 tests passed with no skips. The removed 
implementation's enum name/sort remains a documented compatibility contract 
used by the external logging plugin.
   - Main affected 172-module reactor and e2e-common compile/checkstyle passed. 
Main compile checks intentionally skip unrelated tests.
   - Current init SQL/menu/handle/relation cleanup covers all database 
dialects; historical upgrade SQL stays unchanged. RAT and `git diff --check` 
passed.
   - Logs: `logging-huawei-lts/final-full-verify.log`, 
`logging-huawei-lts/main-compat-pluginenum-test.log`, 
`logging-huawei-lts/main-removal-root-test.log`, 
`logging-huawei-lts/main-compat-rat.log`.
   
   
   ## 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