Sure. I came to the original discussion when something a project I work
on disappeared without notice - it wasn’t totally fatal it was a CI
dependency, not a project dependency, but it still broke our workflow.
Furious at the time… turns out the package used a web service the
submitter-org wasn’t going to keep providing, so you couldn’t win either
way: delete the package and break people; leave it there so people can
continue to pull it automatically and then fail anyway once the service
went away. Probably the abrupt removal was handled poorly. This is just
to show there’s never going to be a nice way to handle every case. I
tend to lean in the direction of “you can’t rewrite history, even if
historical versions are broken”, but that’s just one opinion.
1 Like