feat: extend status page history up to 365 days - #4333
Open
orangeCatDeveloper wants to merge 1 commit into
Open
Conversation
Raise the history range cap from 90 to 365 days and add 60/180/365 dropdown options. Spans over 90 days render as a contiguous strip - 365 blocks with the 2px gap would exceed the container width, leaving sub-pixel blocks (apache#3052).
orangeCatDeveloper
force-pushed
the
feat/3052-status-page-365-days
branch
from
August 18, 2026 07:30
9cc8ad0 to
9975459
Compare
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.
Fixes #3052
A public status page cannot show more than 90 days of availability history.
What's changed?
Raises the history range cap from 90 to 365 days and adds 60/180/365 dropdown options.
Spans over 90 days render as a contiguous strip: with the existing 2px gap, 365 blocks would be sub-pixel and invisible. 90 days and below keep the current look.
Note: on the public endpoint, the first query of a long span runs the pre-existing lazy history merge up to 365 times - idempotent, later queries take the fast path.
30 / 90 days (unchanged):
365 days (contiguous strip):
Checklist
Add or update API