don't retry if change is a deletion
don't retry if change is a deletion

When a deletion/unpublish happens, the change rev will always be greater
than the one on registry.npmjs.org, so the rev-checking logic would get
into an infinite loop. This is now short-circuited in the case of
deletions, to prevent that infinite loop.

bengl/follow-registry