Skip to content

docs: SECURITY.md supported-versions table is five release lines stale #3603

Closed

Description

SECURITY.md still says "As of March 17, 2026 ... v1.1.x - Current stable release line", while v1.6.1 was tagged 2026-08-05. The supported-versions table needs a refresh, and it may be worth bumping it as part of the release process so it cannot go stale again.

Surfaced while reviewing #2666, which describes the current release lines accurately and thereby leaves the repo with two conflicting supported-versions stories.

Activity

  1. added
    kind/documentationCategorizes issue or PR as related to documentation
    triage/not-reproducibleIndicates an issue can not be reproduced as described
    and removed
    triage/needs-triageIndicates an issue needs triage by a maintainer
    on Sep 23, 2026
  2. lexfrei commented on Sep 23, 2026

    @lexfrei
    ContributorAuthor

    Fixed by #3572: SECURITY.md now states a rule (latest stable minor and the two before it) instead of a list of versions.

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

    kind/documentationCategorizes issue or PR as related to documentationtriage/not-reproducibleIndicates an issue can not be reproduced as described

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions