feat: Add historic release caching and archival system #42
Conversation
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
Each dot represents an individual workflow status: - Stage 2: Repo Update (top), Repo Build (bottom) - Stage 3: Garden Linux Nightly - Schedule (top), Build and publish a release - Manual (bottom) - Stage 4: Publish to ghcr.io (top), Publish to S3 (bottom) Signed-off-by: Eike Waldt <waldt@b1-systems.de> On-behalf-of: SAP <eike.waldt@sap.com>
Add option to configure how many historic daily releases are displayed. The count can be set via settings panel or URL parameter (historic_count). Default remains 14 days. Signed-off-by: Eike Waldt <waldt@b1-systems.de> On-behalf-of: SAP <eike.waldt@sap.com>
yeoldegrove
force-pushed
the
feat/hist_release_cache
branch
3 times, most recently
from
a4d11a1 to
dcd4fa2
Compare
Implement caching and archival system for historic Garden Linux releases to improve dashboard performance and enable offline viewing of past releases. Features: - Historic release data collector script with pagination support (up to 200 pages) - Local filesystem caching for API responses and collected GL day data - Dashboard integration with automatic cache loading and force bypass option - GitHub Actions workflow for nightly automated archival - Minimum GL version enforcement (GL 1825) due to workflow structure changes Performance: - Reduced API calls through intelligent caching - Faster dashboard loading for historic releases - Smart date-based pagination stopping Breaking Changes: - Minimum supported GL version is now 1825 Signed-off-by: Eike Waldt <waldt@b1-systems.de> On-behalf-of: SAP <eike.waldt@sap.com>
yeoldegrove
force-pushed
the
feat/hist_release_cache
branch
from
dcd4fa2 to
ebba020
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 this PR does / why we need it:
Implement caching and archival system for historic Garden Linux releases to improve dashboard performance and enable offline viewing of past releases.
Features:
scripts/collect-historic.js)createddate filter for efficient server-side filteringhistoric-releasesbranch (similar topackages)?force=trueURL parameter to bypass cache and fetch live dataPerformance:
createdparameter (eliminates unnecessary API requests)Bug Fixes:
Breaking Changes:
Special notes for your reviewer:
Needs #40 and #41 merged first.