From 662324ea1c5c90152bf847408426de00bc272606 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ricardo=20Gro=C3=9F?= Date: Sun, 18 Oct 2026 15:46:51 +0200 Subject: [PATCH] build: open 2.3.0, and move the package-validation baseline to 2.2.0 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 --- CHANGELOG.md | 2 ++ Directory.Build.props | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9a9278d9..19cb7e37 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,8 @@ A version's heading reads `## — Unreleased` until the release is pre the release date. The release workflow refuses a tag whose section still says `Unreleased`, and the section is the GitHub release's notes. +## 2.3.0 — Unreleased + ## 2.2.0 — 2026-10-18 ### Fixed diff --git a/Directory.Build.props b/Directory.Build.props index 1cc0c833..3f40888e 100644 --- a/Directory.Build.props +++ b/Directory.Build.props @@ -1,6 +1,6 @@ - 2.2.0 + 2.3.0 CaffeinatedCoder Copyright (c) 2026 CaffeinatedCoder MIT @@ -43,7 +43,7 @@ --> true - 2.1.0 + 2.2.0