npm publish, unpublish, and deprecate functionality needs/ requirement

[ganeshkbhat]

Version

v18.10.0

Platform

Microsoft Windows NT 10.0.22621.0 x64

Subsystem

NA

What steps will reproduce the bug?

npm publish, unpublish, and deprecate functionality needs/ requirement:

• When I publish a package v1.0.0 and deprecate it, it is deprecated correctly. I will not be able to publish any other version into v1.0.0.
• When I publish a package v1.0.0 and unpublish it, it is unpublished correctly. However, I am not able to re-publish any other codebase into V1.0.0. I will not be able to re-publish the same version v1.0.0.

How often does it reproduce? Is there a required condition?

Always.

What is the expected behavior? Why is that the expected behavior?

While being unable to republish a unpublished version v1.0.0 is the current behaviour, I believe being able to re-publish a different codebase with the same version v1.0.0 after unpublish should be possible. If you are archiving publish and unpublish logs plus codebase internally in your servers for security reasons and/ or other policy reasons, I suggest you could probably archive into the servers the published-unpublished version v1.0.0, the unpublished v1.0.0 codebase A, new v1.0.0 published codebase B, and future unpublish logs, so on, for the version v1.0.0, etc.

I recommend allowing republishing the same version v1.0.0 with a different codebase B after unpublishing a version v1.0.0 with codebase A; with a possibility to view the publish, unpublish, republish logs/ codebase, etc.

What do you see instead?

When I publish a package v1.0.0 and unpublish it, it is unpublished correctly. However, I am not able to re-publish any other codebase B/ C/ D into v1.0.0. I will not be able to re-publish the same version v1.0.0.

Additional information

NA.

I recommend allowing republishing the same version v1.0.0 with a different codebase B after unpublishing a version v1.0.0 with codebase A; with a possibility to view the publish, unpublish, republish logs/ codebase, etc.

[bnoordhuis]

Wrong repo, you should file this over at https://github.com/npm/cli.

[ganeshkbhat]

I am unsure if this is a node issue, npmjs website issue, or a npm/cli issue. This primarily is a major policy and data management issue of nodejs, npmjs package management; not possibily a bug.

Move now to npm/cli#6327