fix: select domain release metadata constructor - #1364
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Marks the production
DomainCollectionReleaseMetadataconstructor as the Spring injection constructor and adds a real application-context regression.Root cause
The component has a public production constructor plus a package-private test seam. Spring Framework 7 did not infer which constructor to use and attempted a no-arg constructor, causing guarded candidate startup to fail before cutover publication.
Validation
No default constructor foundfailure:website:test :website:bootJarBUILD SUCCESSFULgit diff --checkThe guarded cutover recovered automatically; production is healthy on the legacy release and no legacy collection was deleted.