What should PyTorch teams do about it?

Upgrade ExecuTorch if cross-compiling for bare-metal targets - this was silently breaking downstream CMake builds • Review RL PRs 3910-3913 if you ship distributed RL training - four linked changes that reshape replay buffer semantics • Monitor torch.compile fixes for stream-dependent models heading to next release

Which PyTorch repositories shipped on June 28, 2026?

pytorch/executorch, pytorch/rl, pytorch/pytorch

EXECUTORCH CLOSES CROSS-COMPILE GAP, RL SUITE SHIPS MAJOR REPLAY BUFFER OVERHAUL

By RepoJournal · Filed 06:02 UTC on June 28, 2026 · About PyTorch

ExecuTorch fixes a critical cross-compilation bug that was pulling host libraries into bare-metal targets, while TorchRL lands four major features that reshape how distributed RL training manages memory and replay state.

The cross-compilation fix [1] stops CMake from linking the host's libdl into executorch_core when targeting bare-metal systems like ARM Cortex-M or ESP32, a bug that cascaded through the entire exported interface and broke downstream builds. In parallel, ExecuTorch adds WebGPU support for the cat operator with ValueList graph integration [2], expanding the ops available for browser-based inference. On the RL side, four interconnected PRs ship together: replay buffer consumption semantics [3] that let you recycle slots after sampling instead of only writing sequentially, MCAdvantage shared state fixes [4] so multi-actor setups don't duplicate buffer metadata, collector device normalization [5] for CPU LazyTensorStorage writes, and mjlab environment wrapper support [6] to integrate MuJoCo Lab physics-engine environments. PyTorch core continues hardening: the dataloader test suite becomes device-agnostic [7] so pin_memory and multiprocessing tests run on any accelerator backend, not just CUDA, and torch.compile's partitioner gets a fix [8] for models using explicit CUDA streams in training mode.

FAQ

What changed in PyTorch on June 28, 2026?: ExecuTorch fixes a critical cross-compilation bug that was pulling host libraries into bare-metal targets, while TorchRL lands four major features that reshape how distributed RL training manages memory and replay state.
What should PyTorch teams do about it?: Upgrade ExecuTorch if cross-compiling for bare-metal targets - this was silently breaking downstream CMake builds • Review RL PRs 3910-3913 if you ship distributed RL training - four linked changes that reshape replay buffer semantics • Monitor torch.compile fixes for stream-dependent models heading to next release
Which PyTorch repositories shipped on June 28, 2026?: pytorch/executorch, pytorch/rl, pytorch/pytorch

@pytorch

EXECUTORCH CLOSES CROSS-COMPILE GAP, RL SUITE SHIPS MAJOR REPLAY BUFFER OVERHAUL

The showcase is a teaser.
Your wire is the product.

EXECUTORCH CLOSES CROSS-COMPILE GAP, RL SUITE SHIPS MAJOR REPLAY BUFFER OVERHAUL

The showcase is a teaser. Your wire is the product.

The showcase is a teaser.
Your wire is the product.