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.

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

Depend on a specific version of the supabase-wrappers project instead of a path based dependency #174

Open
imor opened this issue Oct 12, 2023 · 2 comments

Comments

@imor
Copy link
Contributor

imor commented Oct 12, 2023

Chore

Describe the chore

Depend on a specific version of the supabase-wrappers project instead of a path based dependency

Additional context

The path based dependency can stay as it is useful during dev, but we should build against a released version of supabase-wrappers to better dogfood the crate.

@StanGirard
Copy link

Would love to ! Especially that


-- Disable the "wrappers" extension
drop extension if exists wrappers CASCADE;

-- Enable the "wrappers" extension
create extension wrappers with version "0.1.17";


Doesn't work

image

And would be interesting for projects that need consistency :)

@imor
Copy link
Contributor Author

imor commented Nov 21, 2023

@StanGirard this chore was about updating this line in Cargo.toml to use a specific version instead of a relative path. It wouldn't change anything about how drop/create extension works.

For the error you see, can you check whether select * from pg_available_extensions where name = 'wrappers'; shows version 0.1.17?

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

No branches or pull requests

2 participants