-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
feat: remove dependency on pgsodium #37
base: main
Are you sure you want to change the base?
Conversation
696992d
to
f61cd0a
Compare
6fa22da
to
ac58861
Compare
ac58861
to
f525592
Compare
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.
Creating a separate version here as an alternative to 0.2.8 -> 0.3.0
. This lets the extension be created without first creating pgsodium
, which would be necessary when creating 0.2.8
.
@@ -0,0 +1 @@ | |||
requires = pgsodium |
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.
Only 0.2.8
(the current latest version) requires pgsodium
- future versions won't require it.
postgresql_14 | ||
postgresql_15 | ||
postgresql_16 | ||
# ourPg.postgresql_17 |
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.
PG17 is borked atm, affects other repos as well
Add a new version 0.3.0 that doesn't depend on pgsodium. All the needed pgsodium functionalities are baked directly into supabase_vault.