search

denoland / dotland

[Archived] deno.land website
https://deno.land
MIT License
957 stars 626 forks source link

Undo accidental tag of testing branch causing 'latest' version of 3rd party package to look updated #2512

Closed JamesBroadberry closed 2 years ago

JamesBroadberry commented 2 years ago

Hi,

I'm the maintainer of https://deno.land/x/bcrypt and I've recently tagged a commit on a branch that no longer exists with the name "test".

It now looks like it's the latest version of the package.

How do I go about removing that?

Thanks, James

kitsonk commented 2 years ago

The registry is immutable by design. To update the latest version, you would need to publish a newer tag.

JamesBroadberry commented 2 years ago

So because of an accidental tag pushed, I've got to release a new version with no changes made at all and still have this accidental push listed in the history, even though the source doesn't exist?

kitsonk commented 2 years ago

Immutable does mean immutable. When someone says "publish this tag" we copy the code into the registry and ensure it is available, so people can depend on ensuring the code will exist in the future.

The only reason we would remove code is if there is a legal requirement to do so.

JamesBroadberry commented 2 years ago

Just created a new release with nothing changed. Would be good if tagging branches other than the default/main branch didn't cause this kind of mess though.

kitsonk commented 2 years ago

It is hard to predict what people mean. Some people keep a branch seperate for a build of code specifically tailored to Deno. So we presume nothing as any presumption would be wrong. If someone sends a registry a message that they published a new tag, the registry takes their word for it.

This is un-actionable, so respectfully closing.