Skip to content

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 #259

Closed

Description

@CaffeinatedCoder

2.3.1 shipped on 2026-10-31 (tag v2.3.1 at ad25baa, the merge of release/2.3.1 into main). To tag it, main went back to Version 2.3.1 (#257), so CONTRIBUTING "Releasing", step 5, runs again:

  • Directory.Build.props: Version 2.4.0, PackageValidationBaselineVersion 2.3.1.
  • CHANGELOG.md: ## 2.4.0 — Unreleased, opened with its first line.

Then main is merged into release/2.4.0 (decision 94: a patch release's fixes reach the open release branch by merging main once it is tagged), with the baseline at 2.3.1 there too.

Activity

  1. added this to the 2.4.0 milestone on Oct 31, 2026
  2. added
    choreBuild, CI, tooling, packaging, refactoring with no behaviour change
    area/releaseVersioning, changelogs, packaging and release wiring
    on Oct 31, 2026
  3. CaffeinatedCoder commented on Oct 31, 2026

    @CaffeinatedCoder
    OwnerAuthor

    Reopened: #263 opened 2.4.0 on main; merging main into release/2.4.0 is still to do.

  4. CaffeinatedCoder commented on Oct 31, 2026

    @CaffeinatedCoder
    OwnerAuthor

    Done: #263 opened 2.4.0 on main with the baseline at 2.3.1, and #264 merged main into release/2.4.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/releaseVersioning, changelogs, packaging and release wiringchoreBuild, CI, tooling, packaging, refactoring with no behaviour change

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions