chore: re-add empty [Unreleased] section to CHANGELOG - #423
Merged
Merged
Conversation
After the v1.1.0 release, restore an empty [Unreleased] section at the top of the changelog (with a compare/v1.1.0...develop link) so future develop changes have a landing spot, per Keep a Changelog.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
1 participant
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.
Closes out the v1.1.0 release on
develop.The release cut (#421 / #422) turned
## [Unreleased]into## [1.1.0] - 2026-09-26and rewrote its compare link tov1.0.1...v1.1.0, which leftdevelopwith no landing spot for the next change —CHANGELOG.mdcontained the word "Unreleased" zero times. This restores it, exactly as #395 did after v1.0.1.Diff
Two insertions, no existing line touched, so the
[1.1.0]release notes stay as published:+[Unreleased]: https://github.com/shinji-san/SecretSharingDotNet/compare/v1.1.0...develop [1.1.0]: https://github.com/shinji-san/SecretSharingDotNet/compare/v1.0.1...v1.1.0Release state for the record
mainis atbb0405a(merge of Release v1.1.0 #422), taggedv1.1.0— lightweight, asv1.0.1was.developis at4d91c09(merge of chore: prepare v1.1.0 release #421) and carries the same release commitc865d08.SecretSharingDotNet 1.1.0is live on NuGet. The published nuspec recordscommit="bb0405a2bc954dc5a1c9fa77611e9969902cee1e", so the package provably comes from the tagged merge. Both the.nupkgand the.snupkgwere pushed for real (Created/Your package was pushed.), not swallowed by--skip-duplicate.failed: 0throughout.After this merges,
chore-prepare-v1.1.0-releasecan be deleted — it has reached bothmainanddevelop.