Skip to content

CONTRIBUTING promises a parallel 9.x line after 10.0.0; SECURITY.md supports one #86

Closed

Description

@CaffeinatedCoder

SECURITY.md says security fixes land on the latest released minor only, and that older majors are not maintained. SecurityPolicyConventionTests allows exactly one supported row. CONTRIBUTING.md, AGENTS.md and the CI header comment in dotnet.yml call release/9.x "the maintained 9.x line", and CONTRIBUTING expects 9.x patches to come out after 10.0.0.

The policy: one supported version at a time. release/9.x is where 9.x patches go while main takes 10.0.0's breaking changes. It ends at the v10.0.0 tag and takes no changes after it.

Fix: say that in CONTRIBUTING's "Branches and releases", AGENTS.md and the comment in dotnet.yml. Reword the comment beside the release workflow's --latest=false guard. The guard stays, because it costs nothing and it still covers a tag pushed out of order. SECURITY.md needs no change.

Activity

  1. added this to the 9.1.0 milestone on Oct 17, 2026
  2. CaffeinatedCoder commented on Oct 18, 2026

    @CaffeinatedCoder
    OwnerAuthor

    Reversed on 2026-10-18: epic #147 opens a parallel 11.x line on .NET 11, so two versions are supported at a time again (10.x LTS and 11.x). #151 rewrites CONTRIBUTING, AGENTS.md, SECURITY.md and the convention tests accordingly, and replaces the silent-fix-takes-a-major rule for two lines. The wording this issue introduced stays correct until 11.0.0-preview.1 is published.

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