Repository navigation
Auto-republish Hugging Face on contract drift; publish --follow - #42
Merged
Merged
Conversation
added 2 commits
October 23, 2026 16:54
… release A public export schema bump left production behind until someone dispatched the publisher, and HF parity failed in the meantime. On main pushes that touch huggingface/ (except release artifact commits, which the release script dispatches itself), run the parity check and dispatch publish-huggingface.yml only on a DATA_DRIFT verdict; a network failure fails without publishing.
…d IndexNow dry run After the pushes, -Follow waits for Hostinger to serve the Website commit (via the Website verify:live script), waits for the dispatched Hugging Face publish run and requires its production parity step to pass, then runs the IndexNow dry run and prints the --send command. Ends with PUBLISHED AND VERIFIED, or a non-zero exit naming the step that needs attention. Documents the contract auto-republish workflow.
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
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.
Items 5 and 8 of the release-chain hardening.
5. Auto-republish HF on contract drift —
.github/workflows/hf-contract-republish.yml: on main pushes touchinghuggingface/**, except release artifact commits (data: publish pricing artifacts…, which the release script dispatches itself), runcheck_hf_production_parity.py; only on aDATA_DRIFTverdict dispatchpublish-huggingface.yml(still the only workflow that publishes). Network failure fails the job without publishing. Permissions:contents: read,actions: write. Would have removed the manual HF dispatch after the schema 1.11.0 merge (#40).8.
publish --follow(daily-pricing-release.ps1 -Publish -Follow): after the pushesnpm run verify:live(linqiang-max/aicostbudget#96, reads the deployed commit from the bundle's Sentry release id);BUSINESS_PARITY: PASSin its log; reports the HF commit;--sendcommand (sending stays manual).Ends with
PUBLISHED AND VERIFIEDor exits 1 naming the step. Docs updated.Checks: unittest suite OK; release tests 34 pass (5 new follow tests, stubbed). Follow helpers run read-only against the last real release (95947f8 / website e4eb1e7): website
live-newer, HF run 39914333425 parity PASS (HF 469ac60), IndexNow dry run = the same 4 URLs that were sent.