Stamp the release heading for 11.0.0.0 - #143
Merged
Merged
Conversation
The section going out in this release was still titled "Unreleased". Merging dev into release with it that way leaves the 11.0.0.0 tag pointing at a changelog whose top section carries neither a version nor a date, and by then it is too late to fix for that tag. Stamped the way every previous release was, and at the same point in the process: on dev, in an ordinary PR, before promotion - "## 10.12.0.0 08/16/2026" arrived that way in #94. The date follows the same convention as the headings above it, which track the commit date in UTC. Nothing else changes. CHANGES.md is not packed into any NuGet package, so this affects the repository and the tag rather than what gets published.
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.
Release preparation for #142. One line.
CHANGES.mdstill opened with## Unreleased. Promotingdevintoreleasein that state would leave the11.0.0.0tag pointing at a changelog whose top section carries neither a version nor a date — and once the tag exists, that is no longer fixable for it.Why here and not in the promotion PR
The promotion PR's head is
dev, so any commit added there lands ondevanyway. Past practice stamps the heading ondevin an ordinary PR before promotion:## 10.12.0.0 08/16/2026arrived that way in #94.The date
08/26/2026, following the convention of the headings above it — those track the commit date in UTC (the 10.12.0.0 heading matches its commit at2026-08-16 19:52 +0000). If the promotion slips by more than a day, refresh it before merging #142.Scope
CHANGES.mdis not packed into any NuGet package —Xrpl.csprojis SDK-style with no<Content>or<None Pack>— so this changes the repository and the tag, not what gets published. No code, no version numbers: those were already bumped ondev(XrplandXrpl.BinaryCodecto 11.0.0.0;Xrpl.AddressCodecandXrpl.Keypairsdeliberately left at 10.9.0.0, untouched).