feat: Add historic release caching and archival system

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>

Author: yeoldegrove

.github/workflows/archive_historic_releases.yml

@@ -0,0 +1,51 @@
+name: Archive Historic Releases
+
+on:
+    schedule:
+        # Run nightly at 2 AM UTC
+        - cron: "0 2 * * *"
+    workflow_dispatch: # Allow manual triggering
+
+jobs:
+    archive:
+        runs-on: ubuntu-latest
+        permissions:
+            contents: write
+
+        steps:
+            - name: Checkout repository
+              uses: actions/checkout@v4
+              with:
+                  fetch-depth: 0
+
+            - name: Setup Node.js
+              uses: actions/setup-node@v4
+              with:
+                  node-version: "20"
+
+            - name: Install dependencies
+              run: npm ci
+
+            - name: Collect historic release data
+              env:
+                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+              run: |
+                  node scripts/collect-historic.js --days 14 --start-from-yesterday
+
+            - name: Checkout historic-releases branch
+              run: |
+                  git fetch origin
+                  git checkout -B historic-releases origin/historic-releases || git checkout -b historic-releases
+
+            - name: Commit and push historic data
+              run: |
+                  git config user.email "release_historian@gardenlinux.io"
+                  git config user.name "release_historian"
+
+                  if [ -n "$(git status --porcelain historic/)" ]; then
+                    git add historic/
+                    git commit -m "Archive historic release data for last 14 days (starting from yesterday)"
+                    git push origin historic-releases
+                  else
+                    echo "No changes to commit"
+                  fi

.gitignore

@@ -1,4 +1,5 @@
 _site
+.cache
 .venv
 shell.nix
 vendor
@@ -15,3 +16,6 @@ dist/
 
 # packages are in packages branch
 packages/
+
+# historic releases are in historic-releases branch
+historic/

index.html

@@ -108,7 +108,7 @@ <h3>Historic Releases Settings</h3>
                                 type="number"
                                 id="historic-count-input"
                                 min="1"
-                                max="100"
+                                max="2000"
                                 step="1"
                                 value="14"
                                 onchange="updateHistoricCount()"
@@ -138,6 +138,27 @@ <h3>Historic Releases Settings</h3>
 
                 <hr class="settings-separator" />
 
+                <h3>Cache Settings</h3>
+                <div class="branch-settings">
+                    <div class="branch-toggle-group">
+                        <label for="force-cache" class="branch-toggle-label">
+                            <input
+                                type="checkbox"
+                                id="force-cache"
+                                onchange="toggleForceCache()"
+                            />
+                            Disable historic cache (force live GitHub API)
+                        </label>
+                        <small class="branch-help">
+                            When enabled, the dashboard ignores cached historic
+                            data and always fetches it directly from GitHub.
+                            This can be slower and may hit API rate limits.
+                        </small>
+                    </div>
+                </div>
+
+                <hr class="settings-separator" />
+
                 <h3>Workflow Branch Settings</h3>
                 <div class="branch-settings">
                     <div class="branch-toggle-group">

package.json

@@ -5,10 +5,12 @@
     "type": "module",
     "main": "dist/dashboard.js",
     "scripts": {
-        "packages": "git fetch origin && git checkout origin/packages packages",
+        "packages": "git fetch origin && git checkout origin/packages packages && git restore --staged packages",
+        "historic": "git fetch origin && git checkout origin/historic-releases historic && git restore --staged historic",
+        "historic:collect": "node scripts/collect-historic.js --days 14",
         "build": "rollup -c",
         "dev": "rollup -c -w",
-        "serve": "npm run packages && python3 -m http.server 8000",
+        "serve": "npm run packages && npm run historic && python3 -m http.server 8000",
         "start": "npm run build && npm run serve",
         "lint": "npm run lint:js; npm run lint:format",
         "lint:js": "eslint src/**/*.js",