WhatBrokeToday
FAQ
Today's Trends
minorWorkaround availablecrates.iov1.54.0

Tokio 1.54.0 Yanked from Crates.io

  1. Investigating(done)
  2. Trending(skipped)
  3. Workaround available(current)
  4. Resolved(upcoming)

Executive summary

Tokio version 1.54.0 has been yanked from crates.io without a specific reason provided, and version 1.54.1 is now the current release. Existing lockfiles pinning 1.54.0 will continue to build unless updated.

Workaround available

cargo update -p tokio

Reported inRegistryevidence [1]
Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 RegistryShow
  1. [1]
    Registry First report
    [Yanked] tokio 1.54.0: no reason given(opens package registry notice in a new tab)

    tokio 1.54.0 was yanked from crates.io. Cargo no longer picks it for new lockfiles, but a Cargo.lock that already pins it keeps building with it: run cargo update -p tokio. The current release is 1.54.1.

    by crates.io 0upvotes 0comments

Timeline

  1. First report on package registry notice

    [Yanked] tokio 1.54.0: no reason given

    Source
  2. Workaround discovered

    Workaround reported: cargo update -p tokio

    Source
  3. Status changed

    Status changed: new → workaround_available (workaround reported in source signals).