Fixed CHANGELOG to correctly reflect 3.2.0, retargeted new cut as 3.2.1 - #86
Merged
Conversation
…w cut as 3.2.1 v3.2.0 was tagged 2025-11-25 (commit 2d1d6ef) but CHANGELOG.md was never updated at release time, so its content stayed under Unreleased. Moved the Added/Changed/Deprecated entries that were actually in that release (commits 7041cc7..2d1d6ef) into a "## [3.2.0] - 2025-11-25" section. The only entry added since that tag is the Security upgrade, so what was being prepared as 3.2.0 is actually 3.2.1. Updated the section header and the compare links at the bottom accordingly.
imnasnainaec
approved these changes
Aug 31, 2026
imnasnainaec
left a comment
imnasnainaec
left a comment
There was a problem hiding this comment.
In https://github.com/sillsdev/SIL.BuildTasks/releases/tag/v3.2.0, should we "Create release from tag"?
@imnasnainaec reviewed 1 file and all commit messages, and made 1 comment.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on tombogle).
tombogle
requested review from
ermshiperete
and removed request for
ermshiperete
August 31, 2026 12:57
Contributor
Author
|
Done — mostly for consistency, even though in practice people consume our releases via NuGet rather than GitHub Releases. |
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
v3.2.0was tagged at2d1d6ef9(2025-11-25), butCHANGELOG.mdwas never updated at release time, so that release's entries were left sitting under## [Unreleased]instead of being moved into a## [3.2.0]section.CHANGELOG.mdat thev3.2.0tag against master just before the previous release-prep PR (Prepared CHANGELOG for 3.2.0 release #85) merged: the only entry added in that span was the Security upgrade note, everything else predates the 3.2.0 tag.7041cc7c..2d1d6ef9) into## [3.2.0] - 2025-11-25.## [3.2.0]is retargeted as## [3.2.1], since the Security entry is the only thing that's actually new since the 3.2.0 tag.Test plan
v3.2.0tag vs. pre-Prepared CHANGELOG for 3.2.0 release #85 master to confirm exactly which entries were already releasedThis change is