Add DEFAULT_VALUE_CHANGED to configuration metadata changelog #48962
+73
−3
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.
Summary
DEFAULT_VALUE_CHANGEDtype toDifferenceTypeenumRelated Issue
Closes gh-47505
Changed Files
DifferenceType.javaDEFAULT_VALUE_CHANGEDenumDifference.javacompute()ChangelogWriter.javaChangelogTests.javasample-*.json,sample.adocTests
ChangelogTests- Verified DEFAULT_VALUE_CHANGED detectionChangelogWriterTests- Verified new section rendering./gradlew :configuration-metadata:spring-boot-configuration-metadata-changelog-generator:checkpassedDiscussion
I have asked the maintainers about how to handle cases where both deprecation and defaultValue changes occur simultaneously.
Currently implemented to display in both sections (Option 1).