[konlue]

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 [ISSUE #7311] Decouple registry core from implementations. #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.

[Aias00]

Review: Record registry core/implementation decoupling in release notes (#7585)

Docs-only change that accurately documents the shenyu-registry-core decoupling (#7578).

What's good

• The release note clearly explains the behavioral change: shenyu-registry-core no longer transitively provides registry implementations, so applications must declare the provider for their registerType explicitly. The XML snippet, the improved IllegalArgumentException message (naming the missing artifact + available SPI types), the unaffected shenyu-spring-boot-starter-registry aggregate, and the Apollo note are all correct and helpful for users upgrading.

Conclusion

Accurate, well-written documentation. Approving. The only red CI jobs are the usual infra e2e/compose runs — unrelated to a docs change.