Add auto-sync workflow for default seid node configs#508
Open
alexander-sei wants to merge 9 commits intomainfrom
Open
Add auto-sync workflow for default seid node configs#508alexander-sei wants to merge 9 commits intomainfrom
alexander-sei wants to merge 9 commits intomainfrom
Conversation
Builds the latest seid release in CI, runs `seid init`, and regenerates content/node/default-configs.mdx with the unmodified app.toml, config.toml, client.toml, and folder tree. Opens a PR if anything changed. Triggers: weekly schedule, manual dispatch (with optional version override), and repository_dispatch from sei-chain releases. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Embedding today's date caused the weekly cron to open a no-op PR every Monday. The metadata now only changes when SEI_VERSION or SEI_COMMIT change. Git history is the source of truth for "last synced". Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Lets us exercise the full workflow end-to-end on the feature branch before merging. To be reverted once we have one green run. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
When exercised via a push to a feature branch, peter-evans/create-pull-request previously failed with a modify/delete cherry-pick conflict because main didn't yet contain default-configs.mdx. Make the base dynamic: feat branch in test mode, main everywhere else. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
End-to-end test on feat/sync-default-configs-workflow passed (run 25460404106): seid v6.4.4 built, configs regenerated, bot PR #507 opened. Reverting the test scaffolding so the workflow is back to its production trigger set (workflow_dispatch + weekly cron + repository_dispatch). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-authored-by: alexander-sei <184418786+alexander-sei@users.noreply.github.com>
The workflow already supports manual dispatch via workflow_dispatch (with optional version override) plus the weekly schedule. The repository_dispatch path required wiring sei-chain to send events, which we don't have set up. Trim it. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
What is the purpose of the change?
Add new content: a GitHub workflow that keeps the documented default
app.toml,config.toml, andclient.tomlin sync with whateverseid initactually produces in the latest tagged release. Previously the Node Operators Guide and the Node Operations landing page only had hand-curated, drift-prone snippets.Describe the changes to the documentation
.github/workflows/sync-default-configs.yml— clonessei-protocol/sei-chainat its latest GitHub release tag, buildsseidviamake install, runsseid init docs-example --chain-id pacific-1, regenerates the docs page, and opens a PR if anything changed.workflow_dispatch(with optionalsei_versionoverride), weekly schedule (Mon 06:00 UTC), andrepository_dispatchof typesei-chain-release(so sei-chain can poke this on cut).scripts/sync-default-configs.mjs— zero-dep Node ESM that reads~/.sei/config/{app,config,client}.toml, generates a folder tree, and replaces marker blocks (<!-- AUTO-GENERATED:NAME:START/END -->) in the MDX. Idempotent — re-running with the same inputs produces zero diff.content/node/default-configs.mdx— canonical, auto-generated reference. Shipping with the populated v6.4.4 contents (a05b00b) so the page is useful from day one. Hand-written prose lives outside the markers and is preserved across runs.content/node/node-operators.mdxand thecontent/node/index.mdxNode Resources card so readers can find the canonical defaults from the existing guides.content/node/_meta.js.Notes
Tested end-to-end on this branch before opening this PR:
make install, ranseid init, ran the script. Generated the full 1303-line MDX. Verified idempotent (second run = zero diff). Caught a bug along the way (an embeddedtodaydate would have caused weekly no-op PRs) and fixed it in819df79.push:trigger on this branch (3978cfa) to exercise the workflow before merging. Run 25460404106 passed in 3m43s; the bot opened #507, which has been squash-merged into this branch (875be28). The temporary trigger has been removed (20e7daa).Two repo settings need to be on for the post-merge schedule/dispatch runs to open PRs:
To kick off the next sync after merge: Actions tab → "Sync default seid configs" → Run workflow.
🤖 Generated with Claude Code