Skip to content

Changelog cache is never refreshed, so late labeled issues are dropped from release notes #809

Description

@hramosdev

Description

ChangelogBuilder caches the resolved issues per release in cache/releases/<source>/<version>/changelog.json. Once that file exists it is read as is and GitHub is never queried again for that version. Any issue labeled release/<version> after the first successful build never makes it into the release notes.

Impact

Security advisories are the common case. They are frequently labeled release/<version> a day or two after the release, once the embargo lifts, so those fixes end up missing from the published notes.

Concrete example: the 26.7.1 announcement lists 5 security fixes, while the version actually resolves 12. The 7 missing advisories were labeled release/26.7.1 the day after the release.

Suggested fix

Re-query the changelog for releases published within a recent window (for example 30 days) so late entries are picked up on the next scheduled build, while older releases keep their cached changelog untouched for reproducible builds and fewer API calls.

The immediate data correction for 26.7.1 is in #808.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions