Recall vs Transformers

Transformers ships day-0 architectures on every minor release — Muse Glimmer, Granite SWA variants, A.X-K1/K2 and Cosmos3 Edge in 5.15.0 alone — while the structural work happens underneath in the kernel and attention-backend layers. The 5.15.0 release made automatic kernel selection opt-in for linear attention models and stated plainly that the kernels package will very likely become a required dependency of transformers[torch]. The patch that followed is narrower than usual: candidate-generator fixes for speculative decoding and a Lanczos-to-bicubic image resize fallback on CUDA.

Two clocks run in parallel. The architecture clock adds models continuously and treats each one as routine, to the point that breaking changes get flagged with a siren emoji because they would otherwise be lost in the release notes. The infrastructure clock is where direction lives: kernels, attention backends, cache APIs and expert-parallelism contracts keep being reworked so the library can serve as the modelling backend for vLLM rather than merely be compatible with it. Several patch releases in this window exist for no other reason than unblocking a vLLM release, which is a telling inversion of who depends on whom.

Expect kernels to move from opt-in to a hard dependency of transformers[torch], with more model families migrated onto the shared attention backend path and the eager-only route treated as a fallback. Day-0 architecture additions continue at the current pace on every minor.