Skip to content

Open 5.6.1 on release/5.x #200

Closed
Closed

Description

@CaffeinatedCoder

Change

5.6.0 shipped from release/5.x at v5.6.0 (8975493) on 2026-10-23. Open 5.6.1 on it, as #177 opened 5.5.1:

  • Version: Version 5.6.1, PackageValidationBaselineVersion 5.6.0.
  • SECURITY.md: the supported-versions table names 5.6.x ✅ / < 5.6 ❌, the latest release on NuGet. SecurityPolicyConsistencyTests holds that row against the baseline.
  • Changelogs: a ## [5.6.1] heading in all four. The root section stays empty and the package sections say "No change in this package." until a fix lands. The heading's date is set again in the commit that gets tagged.

Done when

release/5.x prepares 5.6.1, so a fix PR into it adds its changelog line under 5.6.1.

Activity

  1. added this to the 5.6.1 milestone on Oct 23, 2026
  2. added
    choreBuild, CI, packaging, refactoring with no behaviour change
    package/coreAffects EFCore.ComplexIndexes
    package/postgresqlAffects EFCore.ComplexIndexes.PostgreSQL
    package/sqlserverAffects EFCore.ComplexIndexes.SqlServer
    area/releaseVersioning, changelogs, release wiring
    on Oct 23, 2026
  3. CaffeinatedCoder commented on Oct 23, 2026

    @CaffeinatedCoder
    OwnerAuthor

    Done by #201: release/5.x prepares 5.6.1 (baseline 5.6.0, SECURITY.md 5.6.x). Closed by hand: Closes acts only on merges into main.

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 wiringchoreBuild, CI, packaging, refactoring with no behaviour changepackage/coreAffects EFCore.ComplexIndexespackage/postgresqlAffects EFCore.ComplexIndexes.PostgreSQLpackage/sqlserverAffects EFCore.ComplexIndexes.SqlServer

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions