Move misplaced CHANGELOG entry to Unreleased (#607) - #608
Merged
Conversation
dayeon5470
approved these changes
Apr 16, 2026
Contributor
|
@dayeon5470 Thank you very much for catching this! |
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
2 participants
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
Move a misplaced CHANGELOG entry from the released 0.14.0 section to the Unreleased section so the changelog correctly reflects that the fix is part of upcoming/unreleased changes.
What changed
SelectComplex(pumpkin) label logic to show selected count for custom-only selections when the predefined list is empty, instead of always showingAll.Why
The entry was erroneously added under a released version (0.14.0). Moving it to Unreleased ensures the changelog accurately represents which fixes are part of the next release vs already released versions.
Notes
Closes #607
Issue: #607