This repository has been archived by the owner on Apr 29, 2024. It is now read-only.
fix: reconciling the Cargo.lock for wrappers to fix build #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
This project would not build locally due to Cargo.lock mismatch
This pr introduces the Cargo.lock file from the specific commit for the most current version of supabase/wrapper used in HEAD of the main branch of this project
for reference it is https://github.com/supabase/wrappers/blob/079922e536df0f4d827a0b35fc0432e7e20c6e1c/wrappers/Cargo.lock
This PR does not yet attempt to update to the latest versions of supabase/postgres and supabase/wrappers, and will ultimately submit a future PR to cover that update