3 ms·
Today I made a release of my npm package that gets 41k downloads a month. Something in the release process botched itself and a git tag was not made of the rel
by latchkey 5y ago
Today I made a release of my npm package that gets 41k downloads a month.
Something in the release process botched itself and a git tag was not made of the release, but it still made it to npm anyway. I immediately fixed the issue and made another release, with a tag.
I went to the npm website and didn't see an obvious way to remove the botched release or even mark it as botched. Maybe there is something on the cli, but I'm lazy.
I also got an automated issue created by "ChainAlert", whom I've never heard of before. "This issue was automatically created to inform you a new version (x.y.z) of yourproject was published without a matching tag in this repo."
It seems like some effort is going into at least bringing this issue to the attention of the maintainers, but I feel like it should somehow be integrated into NPM directly in addition to an issue being created in my project.
- girvo 5y ago`npm unpublish @your-package/name@vx.x.x` is what removes it, if I remember correctly, though yeah thats from the CLI.
- latchkey 5y agoThanks. Your command gave me this: You can no longer unpublish this package. npm ERR! Failed criteria: npm ERR! has dependent packages in the registry But it also suggested the solution: npm deprecate -f 'package@x.y.z' "this package has been deprecated" That seems to have worked. Not sure why there isn't a button on the website.