$ cat huggingface/week/2026-09-14.log
the week in review · Sep 14 – Sep 20, 2026
OpenEnv 0.5.0 ships as typed clients get fixed
By RepoJournal · composed from the cited sources · human-reviewed weekly · methodology
A silent reward bug in typed clients, S3 ownership and CVE fixes, and a Transformers base_model_prefix load fix round out the period.
v0.5.0 huggingface/OpenEnv
The release lands with the RFC 008 manifest and validation contracts restored. Pin or upgrade deliberately: paired with the typed-client fix below, it changes what gets returned from step.
fix(envs): read reward and done from the step envelope in typed clients huggingface/OpenEnv
serialize_observation() deliberately excludes reward and done from the nested observation dict and surfaces them on the response envelope, but three typed clients read them from the observation dict instead and silently received the field defaults. chess_env is described as the worst case. If you train against typed clients, check your reward signal is real before trusting a run.
Fix silently random-initializing `RTDetrModel`/`SEWDForCTC` loads (wrong `base_model_prefix`) huggingface/transformers
RTDetrModel and SEWDForCTC were loading with the wrong base_model_prefix, so weights were silently dropped and the models random-initialized. A load that fails loudly is better than one that reports success with garbage weights; this is that class of bug.
fix(train): enforce S3 ownership on ai_registry default bucket huggingface/sagemaker-python-sdk
The ai_registry and finetune_utils modules derive a predictable default bucket name, sagemaker-{region}-{account_id}, and read and write to it without verifying ownership, unlike sagemaker-core which enforces ExpectedBucketOwner. Because S3 bucket names are globally unique, another account could take that name. If you use ai_registry or finetune_utils, assume the default bucket is untrusted unt...
Bump `peft` version requirement (#48716) huggingface/transformers
peft==0.19.1 cannot correctly load adapter weights, so support for peft<0.20.0 is dropped from Transformers. The release notes state that previously peft>=0.19.1 was supported but that version is "fundamentally broken"; bump your pins or adapter loads will not be correct on that build.
fix: restore mouse input inside herdr huggingface/tau
Herdr 0.9.0 can advertise SGR pixel mouse support while forwarding cell coordinates, so Tau now defaults Textual to cell-coordinate input when running inside Herdr and preserves an explicit TEXTUAL_SMOOTH_SCROLL setting. The interoperability failure and workaround are documented.
Strip invisible and control bytes before matching, in scrub and in redact huggingface/ghlore
scrub_counted matched sentinels and chat tokens before stripping invisible and control bytes, so <<<GHLORE-UNTRUSTED-END>>> came back out as the exact END delimiter and retrieved content could close its own envelope. The same ordering one layer earlier meant redact() missed secrets. Untrusted retrieved content could escape its envelope; update ghlore before putting it in front of a model.
Fix `egg_info.writers` entry point module path (#829) huggingface/kernels
With kernels installed, any setuptools source build in the same environment failed, including builds of unrelated packages, because the egg_info.writers entry point pointed at the wrong module path. A bad entry point in one package breaking every sdist build in the venv is worth the patch.
$ ls huggingface/week/ # the briefings behind this review
Keep up with Hugging Face in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.
Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.