-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Forbidden 403 errors on specific package versions #1294
Comments
We are experiencing this as well, did you ever find a solution to this? |
@erango Nope, it's a bug completely obscure to me. It's not in the client -- pretty sure it's a server issue, so there's nothing for me to look at. But it's intermittent enough that our devs just re-publish until it works. It did seem to only affect pre-release versions. |
@dindurthy for me it was 100% of the time for certain packages, and never for other (older) packages. I just gave up and tested locally then went on to a normal release 🤷 |
Any news on this ? We are experimenting it 100% of the tries... Does a republish solves it ? |
It didn't for me. I just stopped using pre-releases for the affected packages. |
npm If your bug is reproducible on If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo Closing: This is an automated message. |
What / Why
We have been seeing Forbidden 403 errors on specific versions of several private packages. The problem versions appear to have successfully published, but we can't npm install them.
When
I was able to reproduce a package version that works and a package version that errors, but I have no idea how to do so reproducibly. As far as I can tell, I published both package versions exactly the same way. We've only seen this with pre-release versions -- just an observation.
Where
One affected package is
@redoxengine/rid
Here are npm views for the version that works and the version that doesn't. Same .npmrc file is used for both. It's the same package, just different versions, so I don't think scope would come into play. I ran
npm cache clean --force
before this:How
Current Behavior
Some versions of @redoxengine/rid encounter 403 errors when installing.
Steps to Reproduce
Except this only sometimes results in 403s.
Expected Behavior
npm install
installs the prerelease version successfully.The text was updated successfully, but these errors were encountered: