RepoJournal
PyTorch @pytorch
117 wires and counting

$ follow PyTorch

Keep up with PyTorch in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

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.

$ status

wire 2026-06-01
stories 39
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

PYTORCH ROLLS BACK NAMED TENSOR REMOVAL, FIXES CHROMIUM PROFILER LEAK

By RepoJournal · Filed · About PyTorch · Composed from the cited sources · methodology

PyTorch reverted a breaking change that tanked internal signals, while the core team patched a profiler bug that was nuking outer event context.

The named tensor removal [1] is back after it broke internal infrastructure, a significant signal that the community still depends on this API. In parallel, the profiler team fixed a scoped Chromium event bug [2] where exiting a nested profiling context was wiping the entire thread-local event stack, collapsing outer events in the process. On the schema front, error messages for future annotations now surface the actual NameError [3] instead of swallowing it behind a bare exception handler, making debugging type resolution issues dramatically less painful. Inductor's accumulate_grad op got a state modeling fix [4] that makes functionalization explicit: the op now takes current grad as input and returns updated grad, killing hidden Tensor.grad reads that were breaking compiled autograd. The XPU team also standardized their oneDNN integration [5], swapping C API calls for C++ equivalents in DnnlExt.h to eliminate the inconsistent mixing of styles. TensorRT's dependency lockfile got a routine update.

Action items

References

  1. [1] Revert "Remove named tensor (#173895)" pytorch/pytorch ↗
  2. [2] Fix scoped Chromium event reset (#184973) pytorch/pytorch ↗
  3. [3] [library] Improve infer_schema error message when future annotations cause NameError (#185694) pytorch/pytorch ↗
  4. [4] Fix functional accumulate_grad state modeling (#184082) pytorch/pytorch ↗
  5. [5] [xpu] Refactor OneDNN C API to C++ API (#184486) pytorch/pytorch ↗

$ ls pytorch/reviews/ # the step-back reads

the week in review torch.compile dtype fix, two Arm CVEs patched the month in review PyTorch 2.14.0 ships, TorchRL 0.14 lands
Full archive → Weekly reviews →

Quick answers

What shipped in PyTorch on June 1, 2026?
PyTorch reverted a breaking change that tanked internal signals, while the core team patched a profiler bug that was nuking outer event context. In total, 39 commits landed.
What were the notable PyTorch updates?
Revert "Remove named tensor (#173895)", Fix scoped Chromium event reset (#184973), and [library] Improve infer_schema error message when future annotations cause NameError (#185694).
♥

$ log @pytorch --recent

Tensordict compiles masked indexing under fullgraph; ExecuTorch links WebGPU into the Wasm build 138 shipped TensorDict 0.15.0 goes pure Python, 1.77x faster 183 shipped Inductor hands Triton kernels to the worker pool, RL rollout KV cache persists across turns 219 shipped ExecuTorch drops Python 3.10, TensorRT trims compile startup, tensordict fixes silent h5 loss 164 shipped

$ log --all # elsewhere on the wire

Alignment & Post-training verl rejects conflicting vLLM engine_kwargs, open-instruct adds MILES OPD behind a Megatron learner Interpretability nnsight 0.8.0 cuts import time from 7.6s to 1.6s

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.