You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There have been a couple incidents recently where hundreds of crates were procedurally published to squat their names, and crates.io decided to delete the squatted crates after the spam attack was stopped. However, their records still exist on docs.rs, which may cause issues later on if someone else tries to register the same crate and publish the same version number. We should track crate deletions from the crates.io index and scrub the crate from our database when that happens.
This will likely need work in the crates-index-diff crate, since IIRC it doesn't currently check for crate deletions, just new publishes and yanks.
The text was updated successfully, but these errors were encountered:
There have been a couple incidents recently where hundreds of crates were procedurally published to squat their names, and crates.io decided to delete the squatted crates after the spam attack was stopped. However, their records still exist on docs.rs, which may cause issues later on if someone else tries to register the same crate and publish the same version number. We should track crate deletions from the crates.io index and scrub the crate from our database when that happens.
This will likely need work in the
crates-index-diff
crate, since IIRC it doesn't currently check for crate deletions, just new publishes and yanks.The text was updated successfully, but these errors were encountered: