Hugging FaceLucain Pouget, Célina HanoutiProblem & solution
Shipping huggingface_hub every week with AI, open tools, and a human in the loop
Summary
huggingface_hub, the Python client underlying libraries such as transformers, datasets, diffusers, and sentence-transformers, moved from releases every four to six weeks to a weekly cadence. A single manually triggered GitHub Actions workflow now computes versions, manages branches, tags and publishes both huggingface_hub and the hf CLI, creates downstream RC test branches, and handles post-release tasks. An open-weights model drafts structured release notes and Slack announcements using PR metadata and documentation diffs, while OpenCode, HF Inference Providers, PyPI Trusted Publishing, and pinned, checksum-verified tooling provide the stack. Deterministic manifest validation checks missing or extra PR references, then a human reviews and publishes the drafts. The reported result is weekly shipping at about $0.25 per full release, with more consistent notes, earlier downstream breakage detection, and shorter contributor feedback loops.
Context
The previous release process took four to six weeks and combined automated publishing with manual versioning, branching, downstream CI triage, release-note writing, announcements, and post-release updates. Writing notes across tens of PRs and preparing announcements could consume a half-day of focused work, while the team needed safeguards against AI-generated notes dropping or inventing PRs.
Approach / What changed
A hand-triggered GitHub Actions workflow automates versioning, tagging, publishing, downstream RC branches, announcements, archiving, post-release bumps, shipped-PR comments, and CLI documentation updates. An open-weights model drafts notes and announcements; deterministic code builds a PR manifest, validates references, and requests corrections, while a human reviews and publishes the final materials. PyPI Trusted Publishing uses GitHub OIDC, and the OpenCode runtime is pinned and SHA256-verified.
Takeaways
The workflow validates AI-generated release notes against a deterministic manifest of PRs from squash-merge commits, identifying missing or extra references and re-prompting the agent to correct discrepancies.
Documentation diffs from changed Markdown files under docs/ are supplied to the model so release-note details such as CLI examples are grounded in the actual PR documentation.
The reported cadence increased to weekly releases, with full release-note and announcement generation costing about $0.25; downstream RC branches also surface integration breakages earlier.
Source and freshness
- Source
- huggingface.co
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.