Repository navigation
build: open 2.3.0, and move the package-validation baseline to 2.2.0 - #66
Merged
Merged
Conversation
2.2.0 shipped on 2026-10-18 (tag v2.2.0 at f17e760, merged to main as aa5e68f). Version is 2.3.0, the next roadmap section, additive, and the changelog opens its section as Unreleased. The analyzer release files need nothing for an Unreleased section: ChangelogTests ties a shipped section to a dated one only. Package validation now compares with 2.2.0, restored from nuget.org (every .nupkg.metadata of the seven packages names api.nuget.org). The Release pack of all seven packages against it has no error and no warning, and there are no suppression files. ChangelogTests fails with the baseline left at 2.1.0 (The_package_validation_baseline_is_the_last_release, baseline should be "2.2.0" but was "2.1.0") and passes at 2.2.0. Conventions 1501/1501. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
CONTRIBUTING.md, "Releasing", step 4, after v2.2.0.
Problem
2.2.0 shipped on 2026-10-18, but
mainstill builds as 2.2.0 with the package-validation baseline at 2.1.0 and noUnreleasedsection in the changelog.ChangelogTestsfails onmainwhile the baseline trails the last version the changelog dates, and ApiCompat still compares every pack with 2.1.0 instead of the release just shipped.Change
Directory.Build.props:Version2.2.0 -> 2.3.0 (the roadmap's next section, additive);PackageValidationBaselineVersion2.1.0 -> 2.2.0.CHANGELOG.md:## 2.3.0 — Unreleasedabove the dated 2.2.0 section.ChangelogTeststies a## Release <version>section to a dated changelog section only.Tests
The_package_validation_baseline_is_the_last_releasefails (baseline should be "2.2.0" but was "2.1.0"); restored, it passes..nupkg.metadatanames api.nuget.org.Once merged,
release/2.3.0is cut frommainand pushed (step 4's last sentence).🤖 Generated with Claude Code