Repository navigation
Fix 500 for npm packages without any accessible versions - #1149
Merged
Merged
Conversation
ezekg
force-pushed
the
fix/npm-missing-version
branch
from
September 9, 2026 22:02
b85b10f to
a0087c9
Compare
ezekg
force-pushed
the
fix/npm-missing-version
branch
from
September 9, 2026 22:07
a0087c9 to
598e423
Compare
ezekg
marked this pull request as ready for review
September 9, 2026 22:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes a
NoMethodErrorfrom the npm package metadata endpoint when none of a package's artifacts are within the bearer's authz scope, e.g. an anonymous request for a package whose only versions are yanked. Now returns a 404, matching a package with no versions at all.