Feature Request: Yanking an entire package

[andriemc]

Currently, you can only yank one specific version of a package, and depending on the amount of versions in that package, it is gonna take a while, yanking the entire package, wouldn't mean yanking all of the versions, but basically making all of them (including the package) act yanked, so the versions aren't yanked, but the package is, so they'll all act as if they were yanked, and yanked packages could perhaps be hidden in a tab or checkbox when looking at a scope.

[ry]

I also want this feature. There are likely going to be packages we deprecate from @std and I would like a way to prevent them from being displayed on the index page: https://jsr.io/@std

[lucacasonato]

So I think this is not quite the same as yanking - this is a package level "archiving". Would do multiple things:

• not show up in search
• not show up in scope overview (except maybe when you check a "show archived" checkbox)
• not affect semver resolution like "Yanking" does though

Oh and it would show a warning on the package page that this package is archived.

[andriemc]

So I think this is not quite the same as yanking - this is a package level "archiving". Would do multiple things:

• not show up in search
• not show up in scope overview (except maybe when you check a "show archived" checkbox)
• not affect semver resolution like "Yanking" does though

Oh and it would show a warning on the package page that this package is archived.

yeah, Basically that, maybe also allow adding a optional message? and maybe also send a warning message when installing that package (and maybe also for the usual yanked version feature?) also?

(Like how currently npm allows you to "deprecate" packages, and basically all npm package managers say it's deprecated, also showing that "optional message" as well.)

[rojvv]

Possible duplicate of #208?

[andriemc]

So I think this is not quite the same as yanking - this is a package level "archiving". Would do multiple things:

• not show up in search
• not show up in scope overview (except maybe when you check a "show archived" checkbox)
• not affect semver resolution like "Yanking" does though

Oh and it would show a warning on the package page that this package is archived.

yeah, Basically that, maybe also allow adding a optional message? and maybe also send a warning message when installing that package (and maybe also for the usual yanked version feature?) also?

(Like how currently npm allows you to "deprecate" packages, and basically all npm package managers say it's deprecated, also showing that "optional message" as well.)

The optional message thingy could also be added to yanking individual versions too, since you might want to tell the people who use your package why you yanked that individual version

[vwkd]

+1 Archiving is also desirable for renaming an old package by creating a new package. As of now at least, renaming a package directly like a GitHub repo isn't possible. Without archiving, the old package clutters the package list and search which creates unnecessary confusion.