Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CLI: wasmer publish fails for private packages that don't exist yet #4329

Closed
theduke opened this issue Nov 27, 2023 · 0 comments · Fixed by #4331
Closed

CLI: wasmer publish fails for private packages that don't exist yet #4329

theduke opened this issue Nov 27, 2023 · 0 comments · Fixed by #4331
Assignees
@Michael-F-Bryan

Comments

@theduke
Copy link
Contributor

theduke commented Nov 27, 2023

Describe the bug

wasmer publish with a private = true package fails if the package does not exist yet, because it tries to check for package privacy status.

❯ wasmer publish
error: Unable to look up package information
╰─▶ 1: error sending query: no package version for "christoph/winterjs-test2"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Michael-F-Bryan Michael-F-Bryan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix visibility validation to work when publishing a new package wasmerio/wasmer
2 participants
@theduke @Michael-F-Bryan