feat: add automated release index generator and GitHub Pages deployment #879
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
.github/workflows/release-index.yaml
Outdated
| - name: Build Release Index | ||
| working-directory: .github/scripts/release-index | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.TOKEN_GITHUB }} |
denis-codefresh
approved these changes
Nov 3, 2025
Member
Author
|
/e2e |
mikhail-klimko
approved these changes
Nov 4, 2025
Member
Author
|
/e2e |
denis-codefresh
approved these changes
Nov 5, 2025
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
Adds a GitHub Action workflow that automatically generates and publishes a release index to GitHub Pages. The index tracks both
stableandlatestrelease channels, including security fix information and upgrade availability.build-releases.js) that fetches releases via GitHub API, processes them intostable/latestchannels, and generates a structured JSON indexreleases.jsonto GitHub Pages (gh-pagesbranch)Why
Simplifies release tracking by moving the complexity out of the backend. Instead of implementing complex release processing logic and caching in api-graphql, we use a simple pull model - api-graphql just fetches the pre-built JSON from GitHub Pages. The heavy lifting (GitHub API pagination, version normalization, channel detection, security scanning) happens once in CI and gets cached as static JSON.