yangjj-iso opened a new pull request, #7628: URL: https://github.com/apache/shenyu/pull/7628
Prepare the later Apollo main-repository removal for #7599, after the staged deprecation in https://github.com/apache/shenyu/pull/7627. Receiving extension: https://github.com/apache/shenyu-plugin-store/pull/28. Remove the four Apollo runtime/starter modules, their aggregator entries and core-managed Apollo SDK dependencies. Update README/registry docs to point to the external extension, retire Apollo example configuration (preserved in the receiving repo), update the registry CI provider list, and transfer Apollo client licensing to the extension. No active main reactor module or POM dependency references Apollo's SDK after this change. Retain `ApolloPathConstants` unchanged in `shenyu-common` as a small compatibility shim. Preserve historical release notes, enum/type keys, keyspaces and configuration semantics. The existing registry SPI factory is unchanged; the receiving tests prove it resolves the external `apollo` provider. Documentation covers exact install/enable settings, the preceding-release deprecation requirement, one-owner publication, later cutover and rollback. Validation: - Affected 166-module reactor `clean package -DskipTests -Dmaven.javadoc.skip=true -Djacoco.skip=true -DskipRemoteResources=true` passed, including test compilation, Checkstyle and RAT. - 29 targeted tests passed across registry factory, compatibility starter, Admin discovery and HTTP/WebSocket/ZooKeeper/Nacos synchronization. Seven Python dependency-boundary tests passed. - Receiving Apollo reactor passed 30 tests with zero failures/errors/skips; all four final JARs passed implementation/SPI/auto-configuration/core-API packaging checks. `git diff --check` passed. **Do not merge this draft in the deprecation release.** It is based on the advance-notice commit from #7627, but neither that commit nor its PR constitutes a released deprecation cycle. Before removal: link the dev-list decision, ship the notice while retaining Apollo for one core release, merge and verify the receiving extension, announce/publish compatible artifacts without duplicate Maven coordinates, validate the staging deployment and announce a rollback window. No release, upstream merge or artifact publication has been performed. #7599 remains open until those release gates are satisfied. -- 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]
