-
Notifications
You must be signed in to change notification settings - Fork 4
Upgrade supabase. Also remove jwt, as it blocks a postgres upgrade. #221
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
@maparent have you tested the build after upgrading? |
c6450ee to
691826e
Compare
|
I often use the new version locally because it gets installed by homebrew. It's actually why I'm so keen to update, I get mismatch issues. |
|
In PR's like this, could you run the |
|
Example: #196 |
mdroidian
left a comment
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.
👍
691826e to
ba2ab1c
Compare
|
@mdroidian And you were right to ask to check. supabase is fine, but the drop extension migration failed. I did try locally, but in the window; made a correction in the window, and iirc in the file, but somehow must have forgotten to save it, so the correction did not make it in the commit. With idempotent migrations, I sometimes reapply the migration after my local tests to be sure, but that one was not idempotent so I did not. Sigh. There will be another minor commit. More important, this means we really need to have either a dev branch or supabase branches, it would have caught this (and have saved us both this and the above conversation.) |
How would a dev branch be better than running |
No description provided.