[BUG] Can't npm publish: "is not in this registry"

[paulmillr]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

Here's the github action: https://github.com/paulmillr/micro-sr25519/actions/runs/12851615516/job/35832555399

It was working perfectly fine before.

[revelt]

I got the same problem. Old monorepo, setup suddenly stopped. If I delete the .npmrc I can trigger 2FA and do npm publish from my local machine, but effectively, CI publishing is broken due to E404.

[wraithgar]

There is not enough here to reproduce the issue. Please fill out all of the info in the new issue template, and please give us enough steps to reproduce the issue you are having.

[paulmillr]

@wraithgar if you don’t want to help us that’s fine. I knew that NPM became mostly useless for support.

I develop OPEN SOURCE, which means this issue is trivially reproducible if you spend THREE minutes of your time. The logs contain all necessary information. The package is there. The files are there. I've specifically used npm provenance for transparency.

The hell you want from me? My NPM keys? It's been 1.5 months since this issue was created and writing such a response is a joke.

[revelt]

@paulmillr I'm having the same issue and I'm chasing it, and there are other gh issues raised about this, so in a bigger picture, relax, we'll get this fixed =)

If you look from a different angle, this is just a gh ticket management, — the reason guys closed it doesn't mean they're not looking, they're just cleaning up the tickets. Also, the fact that this ticket got attention is because I went to GH support and referenced it in my case (same E404 error), so that's good news too, cogwheels are finally turning =)

[paulmillr]

Well I can't see any "gh ticket management". I reported malware in one of pkgs a few months ago. No one cares. No response, no transparency.

[revelt]

Yes, but the same situation is everywhere; my libs have 13, probably worth a whole holiday length, and I haven't triaged those tickets. It's hard. I can't imagine supporting an issue tracker on other devs code.

[paulmillr]

duplicating in #8144 since support is useless