docs: add latest tags back and improve workflow#2363
Merged
Conversation
Contributor
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Contributor
|
🚀 Preview Deployment Your preview is ready: https://celestiaorg.github.io/docs-preview/pr-2363/ |
gbarros
approved these changes
Dec 17, 2025
Contributor
gbarros
left a comment
gbarros
left a comment
There was a problem hiding this comment.
These look good. Only way to be certain they are 100%, is to run it 👍
Suggestion for another iteration:
Manual Trigger: Currently, you must go to the GitHub Actions "Actions" tab, select "Latest Tags," click "Run workflow," and choose a network (mainnet, arabica, or mocha).
Watching Changes: It is absolutely possible to automate this "watching" behavior.
Since GitHub Actions events (like on: release) only fire for the repository they are in (not external ones like celestia-app), we typically use one of two approaches:
Option A: Scheduled Polling (Easiest & Recommended) We add a schedule trigger (Cron) to run this workflow periodically (e.g., every 6 or 24 hours). It would check usage for all networks (mainnet, arabica, mocha) and only create a PR if it finds a new version that you don't have yet.
Option B: Repository Dispatch (Real-time) If you control the celestia-app and celestia-node repositories, you can add a workflow to them that "pings" this repository whenever a release is published. This is instant but requires changes in the other repositories.
jcstein
changed the title
Member
Author
|
thank you. I'm implementing this suggestion along with some custom logic to, for example, not try to update mocha if it is just an arabica release. |
Member
Author
|
when no new release: when there is a new release: |
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
3 participants
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.
Summary
Restores the manual “Latest Tags” workflow and updates it for the new docs constants layout. The workflow fetches the latest
celestia-appandcelestia-noderelease tags (per selected network) and resolves them to commit SHAs, then writes the results to the network JSON file and opens a PR.Changes
.github/workflows/latest-tags.yaml(manual workflow_dispatch withnetwork: mainnet|arabica|mocha).constants/${network}_versions.jsonto match the new directory structure and JSON-based constants usage.How to run
Actions → Latest Tags → Run workflow → select network.
Creates/updates a PR from
gh-action/latest-tags-${network}with the updatedconstants/${network}_versions.json.Requirements
PAT_CREATE_PRsecret with permissions to push a branch and open PRs in this repo.GITHUB_TOKENfor GitHub API reads.