Add release dates and lag metrics to mirror builds - #14
Merged
Merged
Conversation
Workflow now extracts upstream release timestamps, computes delay between upstream and mirror builds, and stamps each release body with ISO timestamp and machine-readable stats JSON. New patch displays the published date beside each changelog group in desktop and web update popover. Dates are read from a hidden marker in the release body; releases predating the marker simply show no date.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
The mirror Linux build workflow now captures and publishes release timestamps and calculates how far behind the upstream release this build lands. Each release body includes:
mirror-stats) with: tag, channel, publishedAt, upstreamPublishedAt, and delaySecondsThis lets in-app update changelogs display release dates without calling the GitHub API, and lets dashboards track how far behind the fork trails upstream over time.
Why
Users see "new version available" without knowing when it shipped or how stale it is. Dashboards tracking this fork had no reliable way to compare release timing across the fork and upstream without extra API calls or manual parsing. Encoding the data once at release time makes both problems solvable.
The JSON format includes a
versionfield so schema changes won't break parsers downstream.Checklist