Document v2.1.1 stable release and update landing - #149
Merged
Merged
Conversation
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.
The stable v2.1.1 release is public, but the README, compatibility matrix, roadmap, and Signalboard landing page still advertise v2.1.0. Update those references and record the signed-tag, workflow, public-package, and consumer verification that supports the new version.
Validation: all 13 v2.1.1 package IDs appeared in NuGet's public flat-container index; a fresh net8 consumer restored from nuget.org and ran with
OK; the public Tooling package installed and passed the safe dashboard fixture.python scripts/check-released-version.py,dotnet build samples/Signalboard/Signalboard.csproj -c Release --no-restore, andgit diff --checkpassed.