Skip to content

Tag-time branch steps assume a net11 branch that was never created #280

Closed

Description

@CaffeinatedCoder

Problem

origin has only main and release/9.x. No net11 branch has ever existed, and no v11.0.0-preview.* tag either: #103 (preview.1) and #157 are still open under #147. These places describe net11 as if it existed:

So the tag-time procedure can't be followed as written: only "cut release/10.x" is possible. After the cut, main is "the 11 line" but still says Version 10.0.0, so the retarget (#103) has to land on main directly.

Change (needs a maintainer decision)

Either:

(a) matches what actually happened. It also makes #157 moot, because 10.0.0 will be on NuGet before the first preview.

Done when

AGENTS.md, CONTRIBUTING.md, SECURITY.md, dotnet.yml, #58 and #147 describe the same procedure, and it can be followed at the tag.

Activity

  1. added this to the 10.0.0 milestone on Oct 19, 2026
  2. CaffeinatedCoder commented on Oct 19, 2026

    @CaffeinatedCoder
    OwnerAuthor

    Decision (maintainer, 2026-10-19): option (a). There is no net11 branch. At the v10.0.0 tag, release/10.x is cut from the tag, and the retarget to .NET 11 (#103) lands on main right after it. That makes #157 moot, because 10.0.0 will be on NuGet before the first preview. The docs fix lands before the tag, so the tagged CONTRIBUTING.md describes the steps actually followed.

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, release wiringdocumentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions