[BUG] 503 when publishing a new version when we have too many existing versions #6509
Open
2 tasks done
Labels
Bug
thing that needs fixing
Priority 2
secondary priority issue
Release 9.x
work is associated with a specific npm 9 release
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
npm publish returns a 503 when trying to publish a new package version.
Expected Behavior
I had the exact same problem with sfdx-hardis some months ago , and now I can't publish a new version of mega-linte-runner (quite impacting while releasing a new major version ... )
The solution was that support manually deletes hundreds of alpha and beta versions, which was impossible through CLI (503 again)
I posted ticket 2177911 on npm support but nobody replied yet and I'm still unable to publish a newer version.
Would it at least be possible to return a meaningful error message ?
And why not provide a workaround allowing to solve the problem without going through support ?
Many thanks
Steps To Reproduce
Same failure in CI or local CLI
Environment
The text was updated successfully, but these errors were encountered: