-
Notifications
You must be signed in to change notification settings - Fork 824
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
Allow publishing packages without a module #3711
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
4ca3665
to
8dca69a
Compare
Also update the lockfile
Removes the check that requires a module to be specified when publishing a package. Removed because modules should not be mandatory - packages with just a file system, or with a command that uses the module of a dependency are perfectly valid.
These were introduced by an older version of targz-to-pirita depending on an older wasmer-registry
8dca69a
to
b114264
Compare
Closes #3712 |
@Michael-F-Bryan the changes here seem to regress the Python tests again. |
@theduke I'm guessing the regression is because #3690 fixes that by removing the |
The package validation changes were included in #3716, since that also moves the validation code. The webc version upgrades / deduplication should be handled in a dedicated PR. |
Removes the check that requires a module to be specified when publishing
a package.
Removed because modules should not be mandatory - packages with just a
file system, or with a command that uses the module of a dependency are
perfectly valid.