feat: Add weekly cron to fetch upstream schema#179
Merged
Conversation
This was referenced Jun 12, 2026
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.
Description:
Add the weekly schema-sync mentioned in #177. The workflow runs
npm run schema:syncand opens a PR when the upstream schema's drifted.Additions:
.github/workflows/schema-sync.yml: on a cron, plus a manual dispatchKnown limitation:
If PRs are opened, they won't yet trigger the
pull-requests.ymlbuild. This is something for us in a follow-up when we actually consume the schema for something (if and when a new schema could break the build).Related issues and pull requests:
Part of #177
Relates to #178