allows requires
key in control file to specify only certain allow-listed extensions
#143
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.
What kind of change does this PR introduce?
Feature
What is the current behavior?
requires
andrelocatable
keys were not sent to the backend when publishing a package.requires
key in the control file.Nothing to publish
was shown by the CLI even though package's properties were updated.What is the new behavior?
requires
andrelocatable
will be sent to the backend when publishing a package. These are optional for now for backward compatibility with older CLI versions. We will remove thepublish_package(package_name app.valid_name, package_description varchar(1000)
function once the newer CLI version is widely abopted.app.allowed_extensions
table are allowed in therequires
key in the control file. Currently extensions available on Supbase and AWS RDS are allow-listed.Updated package properties
will now be shown to indicate thatrelocatable
andrequires
keys have been updated.Additional context
Fixes #131