konlue opened a new pull request, #7642: URL: https://github.com/apache/shenyu/pull/7642
Fixes #7585 ## Modifications Adds one entry under `## Unreleased` → `### Behavior Changes` in `RELEASE-NOTES.md`, covering the behavior change from #7578 (`refactor(registry): decouple core from registry implementations`, merged as `a7d80b7`). Documentation only — no Java, POM, or configuration change. ## What the entry records - `shenyu-registry-core` no longer transitively provides registry implementations; applications depending on it (or on `shenyu-sdk-core` / `shenyu-sdk-feign`) must declare the provider matching their configured `registerType` explicitly, with an example `<dependency>` block. - The failure mode when a `registerType` has no SPI provider on the classpath is now an `IllegalArgumentException` naming the missing artifact, replacing the previous `ExtensionLoader.getJoin` failure. - `ShenyuInstanceRegisterRepositoryFactory#loadRepository(String)` is public API, and `AbstractDiscoveryProcessor#createDiscovery` resolves its repository through it. - Compatibility: `shenyu-admin` and `shenyu-spring-boot-starter-registry` re-declare all five providers, so existing users of the compatibility starter are unaffected. Apollo was never part of that aggregate. - Migration guidance is delegated to `shenyu-registry/README.md`, added by #7578. ## Scope Only the `### Behavior Changes` section is touched. The existing `### API Changes` entries (`MemorySafeLRUMap` deprecation, `DiscoveryUpstreamDataSubscriber#unSubscribe` signature replacement) look unrelated to #7578, so I left them as they are — happy to move the entry elsewhere if that's the convention you prefer. ## Verifying this change `git diff --stat` → `1 file changed, +25 insertions(-)`. No build is required for a documentation-only change. -- 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]
