Skip to content

[Docs]: CHANGELOG — pre-1.0 entries under the wrong version, and 47 dates that are not the release day #2619

Description

@laurentiu021

Problem

Two kinds of drift in the history, both before the release workflow started checking the date:

Expected behavior

Every heading names the version that shipped it, and every date is the release day in UTC, as Keep a Changelog defines it. Re-derive each mapping from the tags before editing, keep the content of each entry, and note the renumbering once where the 0.47 block starts. The contiguity guard keeps excluding pre-1.0, so this changes no test.

Affected tab

Docs

Activity

  1. laurentiu021 commented on Oct 10, 2026

    @laurentiu021
    OwnerAuthor

    Fixed in #2666.

    Every entry is now under the version that shipped it, re-derived from the tags: 0.47.2 to 0.48.1 take their own numbers (they had been written as 0.49.0 to 0.53.1, and 0.47.1 as 0.48.0), 0.28.6 gives back 0.28.2 to 0.28.5's fixes and the Startup Manager one it repeated from 0.28.1, and 0.36.0 gives back 0.35.12's and 0.35.13's notes, which this issue had only half spotted. The note under 0.48.2 said those versions were released from the previous repository; they were tagged and published here, so it now says what happened, once, where the block starts. Every tag has a heading.

    The dates follow the day each GitHub release was published, in UTC, except where the release was published after the fact: the 100 re-published on 2026-05-08, when the history moved here, and three backfills of releases that had failed. On that reading 49 headings changed rather than the 47 counted above. 1.99.0's was right, since it was released the day after its commit, and 1.75.3, 1.65.14 and 1.18.3 were published the day after theirs.

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

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions