In my CI I have a line which regenrates the types from the database and fails if it finds any differences. This makes sense.
However, if there is a mismatch between the supabase CLI version used by GitHub actions and the one you used locally to build the types, an error might be raised if the format is different.
This is fixable by upgrading the local supabase version.
>>> supabase --version
1.187.3
A new version of Supabase CLI is available: v1.187.8 (currently installed v1.187.3)
We recommend updating regularly for new features and bug fixes: https://supabase.com/docs/guides/cli/getting-started#updating-the-supabase-cli
Sure, but if I try to update with 'brew upgrade supabase`, it says that 'supabase is already to the latest version 1.187.3'.
Basically brew does not register the update, which means I am unable to push any commits to master because they all fail the CI.
The immediate fix is ensure that brew upgrade sees the latest version. Longer term it would be nice to avoid this type of breakages by making sure all the versions are updated at the same time
Note It's weird that a minor version update 1.187.3 -> 1.187.8 changes the generated types formatting, which in turns break CI (which is a check which is suggested by the supabase documentation)
⚠️ We receive a lot of bug reports which have already been solved or discussed. If you are looking for help, please try these first:
Bug report
Hi,
In my CI I have a line which regenrates the types from the database and fails if it finds any differences. This makes sense. However, if there is a mismatch between the supabase CLI version used by GitHub actions and the one you used locally to build the types, an error might be raised if the format is different.
This is fixable by upgrading the local supabase version.
Sure, but if I try to update with 'brew upgrade supabase`, it says that 'supabase is already to the latest version 1.187.3'. Basically brew does not register the update, which means I am unable to push any commits to master because they all fail the CI.
The immediate fix is ensure that brew upgrade sees the latest version. Longer term it would be nice to avoid this type of breakages by making sure all the versions are updated at the same time
Note It's weird that a minor version update 1.187.3 -> 1.187.8 changes the generated types formatting, which in turns break CI (which is a check which is suggested by the supabase documentation)
⚠️ We receive a lot of bug reports which have already been solved or discussed. If you are looking for help, please try these first:
Before opening a bug report, please verify the following:
-->
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Additional context
Add any other context about the problem here.