Further hide deprecated versions in version listing

[gbaz]

An unfortunate consequence of an accidental upload of a nightly ghc lib to hackage:

It would be nice if we could set hackage to make deprecated versions much more hidden -- i.e. perhaps not listed directly in that section at all, but just hidden behind a link...

[fgaz]

In a <del> tag maybe? A strikethrough is more noticeable than a slight change of color

[ulysses4ever]

I'd prefer deprecated versions hidden behind one more link or a collapsible section on that page.

[phadej]

Accidental upload is why e.g. cabal have changed to upload candidates by default. I'd be ok to require human click to publish packages. (amazonka monster uploads is a bit of chore to click through then, but OTOH, if mistake is made in automatic upload there, it's a major mistake).

[phadej]

Note: solver is free to pick up deprecated packages! it's a soft preference. To "completely" prevent a package version from being used, you'd need to make a revision with unsatisfiable constraint (like base <0), but even that is not enough, as if package makes through into e.g. stackage nightly snapshot, they pin revisions, so even if a package versions is later deprecated or/and revised, it will still be in that snapshot (that's the point of snapshotting).

It would be very confusing if version doesn't appear, or is hidden.

I'm in favor of <del> or/and semantic markup, accessibility should be a top priority for sites like Hackage.

EDIT: Note that versions with unsatisfiable constraints (which are numerous) dont' have any visual clue in the version listing. They could.