Skip to content

Conversation

@feelepxyz
Copy link
Contributor

Some registries (e.g. GH packages) require auth to check visibility, and always return 404 when no auth is supplied. In this case we assume the package is always private and require --access public to publish.

I've also updated this to only perform a visibility check when this is actually needed (i.e. when provenance is true and access is not public).

Fixes #6436

feelepxyz added 2 commits May 9, 2023 15:50
Some registries (e.g. GH packages) require auth to check visibility,
and always return 404 when no auth is supplied. In this case we assume
the package is always private and require `--access public` to publish.

I've also updated this to only perform a visibility check when this is
actually needed (i.e. when `provenance` is true and `access` is not `public`).

Fixes #6436

Signed-off-by: Philip Harrison <[email protected]>
Signed-off-by: Philip Harrison <[email protected]>
@feelepxyz feelepxyz changed the title Update publish /w provenance to ignore pkg vis 404 fix: Update publish /w provenance to ignore pkg vis 404 May 9, 2023
feelepxyz added 2 commits May 9, 2023 16:05
Signed-off-by: Philip Harrison <[email protected]>
Signed-off-by: Philip Harrison <[email protected]>
@feelepxyz feelepxyz marked this pull request as ready for review May 10, 2023 10:45
@feelepxyz feelepxyz requested a review from a team as a code owner May 10, 2023 10:45
@wraithgar wraithgar merged commit f064696 into npm:latest May 10, 2023
@github-actions github-actions bot mentioned this pull request May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Package visibility fails on GH packages with provenance

2 participants