You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Using a GitHub action to push migrations to the hosted instance fails with the current CLI, because it is now fatal to not have an smtp host defined. The local CLI development defaults to in bucket, so this is not set in my config file.
pulls the latest version of the cli, which is v1.223.10 currently. My project locally is still using CLI v1.219.2 where everything works. When running the link command, it fails with this error:
Missing required field in config: auth.email.smtp.host
Try rerunning the command with --debug to troubleshoot the error.
Then it exits.
There's no reason to have the local CLI development configuration set this variable, as it uses inbucket.
Expected behavior
A clear and concise description of what you expected to happen.
The deploy should succeed like it always has with my config file, or the version should be bumped for the breaking change.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Rerun the failing command with --create-ticket flag.
Now it is demanding I set all the other fields, but there's no guidance as to what those should be to work with inbucket in the sample config.toml in a new project. I set the following, but the auth service cannot still send any email, it returns 500 error status.
It would be helpful to add those notes in the config.toml in a new project, and to have a "migrate" function of the CLI to bring my config file up to current, keeping existing settings I changed.
Describe the bug
A clear and concise description of what the bug is.
Using a GitHub action to push migrations to the hosted instance fails with the current CLI, because it is now fatal to not have an smtp host defined. The local CLI development defaults to in bucket, so this is not set in my config file.
To Reproduce
Steps to reproduce the behavior:
Using the following GitHub actions:
pulls the latest version of the cli, which is v1.223.10 currently. My project locally is still using CLI v1.219.2 where everything works. When running the link command, it fails with this error:
Then it exits.
There's no reason to have the local CLI development configuration set this variable, as it uses inbucket.
Expected behavior
A clear and concise description of what you expected to happen.
The deploy should succeed like it always has with my config file, or the version should be bumped for the breaking change.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Rerun the failing command with
--create-ticket
flag.latest
.supabase services
command] nothing is running in my action but the CLI.Additional context
If applicable, add any other context about the problem here.
The text was updated successfully, but these errors were encountered: