Hugging Face has released version 1.30.0 of its Hub client, adding practical controls for scheduled jobs and making revision resolution repository-aware. The changes matter most to teams automating model workflows, where a small ambiguity can become a surprisingly large Friday afternoon.
Hugging Face Watch analysis
What happened
The release, published on 3 September, updates the command-line and Python interfaces for scheduled jobs, changes how resolved revisions retain repository context, and loosens one requirement for chat completion through hf-inference. It also includes fixes for Hub-host redirects, documentation and release tooling.
Our top picks
- Scheduled-job filters
List jobs by status, label or name, bringing the command into line with existing job-listing behaviour. - A safer revision pin
ResolvedRevision remembers its repository, so the same resolved object is not silently misapplied elsewhere. - Broader chat-completion support
Models tagged text-generation or image-text-to-text can now be served without the conversational tag. - Cleaner migration path
The older -f/–filter option is deprecated and now ignored, with guidance towards the newer flags. - More reliable Hub redirects
Redirects between Hub hosts are followed without sending authorisation to external CDNs. - Sandbox clarity
Experimental Sandbox API markings and trust-boundary guidance are now clearer in docs and help text.
Why it matters
None of this is a moon landing, which is precisely the point. These are the seams where automated model operations tend to fray: filtering the wrong jobs, reusing a revision in the wrong repository, or discovering that an apparently compatible model needs a different tag.
The release also quietly improves the security shape of file resolution. Redirects work more predictably while authorisation remains on the Hub side of the fence.
Our read
Worth adopting for teams using scheduled jobs or programmatic revision handling. Audit any scripts still passing -f/–filter, then test revision reuse across repositories before rolling the update through production. Small release, useful housekeeping, fewer traps.
What to watch
- Whether the deprecated scheduled-job filter is removed in the next release.
- Any downstream assumptions about ResolvedRevision objects being repository-agnostic.
- Provider-specific behaviour as broader inference tag support reaches real workloads.
Discussion spark: Which change is most likely to save you debugging time: scheduled-job filters, repository-aware revisions or broader inference tag support?
Sources and evidence
- [v1.30.0] Scheduled job filters, repo-aware revision pinning and more (3 September 2026, 10:02 UTC)
not affiliated with or endorsed by Hugging Face