Skip to content

Release 10.4.0: date the changelogs, tag v10.4.0, carry the sections to main #519

Closed

Description

@CaffeinatedCoder

Change

These are the release steps now that every in-scope PR of #472 has merged into release/10.x, as #470 did for 10.3.0. Version is already 10.4.0 (#473). The last merges were #518 (#517) and #516 (#512) on 2026-10-26, so the release commit to check is release/10.x at 07d92df or later.

  1. Check before the tag. All of the following must hold on the release commit, with every fix merged, so the fixes are checked together rather than one PR at a time:
  2. Date the five changelogs. Set ## [10.4.0] — yyyy-mm-dd in all five, in the commit that gets tagged.
  3. Tag v10.4.0 (annotated, like v10.3.0) on that commit. The release workflow publishes the packages, and the nuget environment approval is the maintainer's.
  4. Check that no 10.x-only issue is left open. Closes #n acts only on main. Every sub-issue of Epic: 10.4.0 #472 is closed already, so this step only re-checks.
  5. Carry 10.4.0 to main in one PR, as chore: carry the 10.3.0 sections to main (#470) #474 did for 10.3.0. It can't build until 10.4.0 is on nuget.org, because the baseline bump restores it.
  6. Open 10.5.0 on release/10.x, as Open 10.4.0 on release/10.x #473 did after 10.3.0: Version, the baseline, the SECURITY.md row and the sample move on. Translate ToRangeSet() from Int32Set, Int64Set, DateSet, LocalDateSet and YearMonthSet (split from #407) #487 is already deferred to 10.5.0.

Done when

  • v10.4.0 is on nuget.org for all four packages.
  • GitHub's Latest release is still the highest stable version.
  • Epic: 10.4.0 #472 is closed with a summary.
  • main carries the 10.4.0 sections.

Activity

  1. added this to the 10.4.0 milestone on Oct 26, 2026
  2. added
    choreBuild, CI, packaging, refactoring with no behaviour change
    package/nodatimeAffects CodoMetis.ValueRanges.NodaTime
    package/efcoreAffects CodoMetis.ValueRanges.EFCore.PostgreSQL
    area/releaseVersioning, changelogs, release wiring
    package/coreAffects CodoMetis.ValueRanges
    package/efcore-nodatimeAffects CodoMetis.ValueRanges.EFCore.PostgreSQL.NodaTime
    on Oct 26, 2026
  3. CaffeinatedCoder commented on Oct 26, 2026

    @CaffeinatedCoder
    OwnerAuthor

    Step 1: dotnet run tools/oracles.cs seeds on release/10.x at 07d92df (the release commit's tree minus the changelog dates): every seed is caught. CI on 07d92df and on the date PR #520 is green on every lane (PostgreSQL 16 and 18, EF Core floor and 10.0.14, both smoke-test modes).

  4. added 2 commits that reference this issue on Oct 26, 2026
  5. added a commit that references this issue on Oct 26, 2026
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 CodoMetis.ValueRangespackage/efcoreAffects CodoMetis.ValueRanges.EFCore.PostgreSQLpackage/efcore-nodatimeAffects CodoMetis.ValueRanges.EFCore.PostgreSQL.NodaTimepackage/nodatimeAffects CodoMetis.ValueRanges.NodaTime

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions