Skip to content

build: open 2.4.0 again, and move the package-validation baseline to 2.3.1 - #263

Merged
CaffeinatedCoder merged 1 commit into
mainfrom
build/open-2-4-0-after-2-3-1
Oct 31, 2026
Merged

CaffeinatedCoder merged 1 commit into
mainfrom
build/open-2-4-0-after-2-3-1

Conversation

@CaffeinatedCoder

Copy link
Copy Markdown
Owner

Closes #259

Problem

2.3.1 shipped on 2026-10-31 (tag v2.3.1 at ad25baa). To take the tag, main went back to Version 2.3.1 (#257), so it neither says 2.4.0 nor validates the packages against the release just shipped. CONTRIBUTING "Releasing", step 5.

Change

  • Directory.Build.props: Version 2.4.0, PackageValidationBaselineVersion 2.3.1.
  • CHANGELOG.md: ## 2.4.0 — Unreleased, opened with its first line, because pack fails while the section is empty.

Once this is on main, main is merged into release/2.4.0, which carries the 2.3.1 fixes there and moves its baseline to 2.3.1.

Tests

build-verdict test --project test/CodoMetis.TypeKit.Conventions.Tests: 2018 passed, packing all seven packages against 2.3.1. Every baseline .nupkg.metadata names api.nuget.org, and there are no suppression files.

🤖 Generated with Claude Code

…2.3.1

2.3.1 shipped on 2026-10-31 (tag v2.3.1 at ad25baa, the merge of
release/2.3.1 into main), and main went back to Version 2.3.1 to take the
tag. Version is 2.4.0 again, and the changelog opens its section as
Unreleased with its first line, since pack fails while the section is empty.

Package validation now compares with 2.3.1, restored from nuget.org.

Closes #259

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@CaffeinatedCoder CaffeinatedCoder added this to the 2.4.0 milestone Oct 31, 2026
@CaffeinatedCoder CaffeinatedCoder added chore Build, CI, tooling, packaging, refactoring with no behaviour change area/release Versioning, changelogs, packaging and release wiring labels Oct 31, 2026
@CaffeinatedCoder
CaffeinatedCoder merged commit e2e1124 into main Oct 31, 2026
18 checks passed
@CaffeinatedCoder
CaffeinatedCoder deleted the build/open-2-4-0-after-2-3-1 branch October 31, 2026 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/release Versioning, changelogs, packaging and release wiring chore Build, CI, tooling, packaging, refactoring with no behaviour change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Open 2.4.0 again on main after 2.3.1, the baseline at 2.3.1, and merge main into release/2.4.0

1 participant