Uh oh!
There was an error while loading. Please reload this page.
Close the books on 1.1.0 - #4
Merged
Merged
Conversation
The three post-release steps from docs/releasing.md, now that the packages are on nuget.org: PackageValidationBaselineVersion goes back to 1.1.0, so every later build is diffed against what actually shipped rather than against nothing. The public API moves from Unshipped to Shipped — AnsiCss into it, HtmlCss's two *REMOVED* lines out of it — so the analyzer treats 1.1.0's surface as the one that has to hold. CHANGELOG's Unreleased entries become the 1.1.0 section. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Warning Review limit reachedNext included review available in 3 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Your 55 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Essentials Run ID: 📒 Files selected for processing (7)
Comment |
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
The three post-release steps from
docs/releasing.md, now that 1.1.0 is on nuget.org.PackageValidationBaselineVersionback to1.1.0in all three packages. It came off for the release that removedHtmlCss, because the surface being removed from was the surface it would have validated against. With it back, every later build is diffed against what actually shipped, so an unintended removal or signature change fails at build time instead of in a consumer's restore.AnsiCssmoves intoPublicAPI.Shipped.txt;HtmlCss's two*REMOVED*lines come out of it. 1.1.0's surface is now the one the analyzer holds you to.Unreleasedentries become the1.1.0 — 2026-09-07section.Verified with
dotnet pack: all three build as 1.1.0 and validate clean against the published baseline.🤖 Generated with Claude Code