Add missing entry to wait_states_1.5_rel_notes.mdx #6918
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
Commit e4c4b54d1462cf9f115ada932a9d19fa592359b7, contained in the release of 1.5.0, fixed a miscalculation (integer overflow) of retention time for larger values, that caused history files to be pruned sooner than they should have been. For some reason, this was not listed in the release notes of 1.5.0. A customer has just reported the issue, so it's best to have it mentioned in the release notes, so we can reference the bug fix in customer cases.
nidhibhammar
approved these changes
Jul 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Commit e4c4b54d1462cf9f115ada932a9d19fa592359b7, contained in the release of 1.5.0, fixed a miscalculation (integer overflow) of retention time for larger values, that caused history files to be pruned sooner than they should have been.
For some reason, this was not listed in the release notes of 1.5.0.
A customer has just reported the issue while using an older version, so it's best to have it mentioned in the release notes, so we can reference the bug fix in customer cases.