docs(changelog): file the sync corroboration fix under 3.8.0 - #2331
Merged
Conversation
#2322 merged into develop after the release commit, so it is inside the develop -> main promotion (#2317) and ships in the v3.8.0 tag. The entry was filed under [Unreleased], which would have shipped a changelog telling users the fix was not yet released while the code was in their install. Move the entry verbatim into the 3.8.0 Bug Fixes section. No wording changes. The [Unreleased] link definition still points at v3.7.1...HEAD; it was already stale before this change and belongs to the tag step, so it is left alone here.
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
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.
Why
#2322 merged into
developafter the release commit for 3.8.0.develop's tip and #2317's head are the same SHA (7d1088c), so the fix is already inside thedevelop → mainpromotion and will ship in thev3.8.0tag.The changelog entry was filed under
## [Unreleased], which was the right call on the assumption it would land after the release — but because #2317 promotesdevelopwholesale, that assumption does not hold. As it stood,pip install mempalace==3.8.0would ship a significant data-loss fix alongside a changelog telling the user it was not yet released.What
Moves the entry verbatim from
[Unreleased]into the[3.8.0]Bug Fixes section, as the first bullet. No wording changes — I verified the line is byte-identical before and after, and that the edit introduces no new blank-line runs.Net:
-8/+1. The now-empty[Unreleased]heading and its---separator are removed, matching how the 3.8.0 release commit (32567b7) handled the same transition.Not done here
[Unreleased]: …/compare/v3.7.1...HEADat the bottom of the file still points at v3.7.1. It was already stale before this change and updating it belongs to the tag step, so it is left alone rather than widening this diff.Refs #2320, #2322. Companion to #2317 — the release notes on that PR are being updated to match.