Linking to project using CLI in CI environment not working.

[CalvinWilkinson]

Describe the bug
I am trying to link to my project in the GitHub CI environment by using the supabase link --project-ref --password command.
When doing this, I get the following output:

WARN: no SMS provider is enabled. Disabling phone login
Connecting to remote database...
failed to connect to postgres: failed to connect to `host=aws-0-us-west-1.pooler.supabase.com user=postgres.hypsasklbmkqagnwhkca database=postgres`: failed SASL auth (invalid SCRAM server-final-message received from server)
Try rerunning the command with --debug to troubleshoot the error.
Error: Process completed with exit code 1.

I don't know if this is related to the issue below, but I have been having issues related to this for months. This time, the issue has changed from what was described in the issue below to the output described above.

• Failed to retrieve project status #2956

I tried 2 different attempts this morning. The first attempt was with supabase CLI version v2.22.4 with the command supabase link --project-ref with the GitHub output below:

 $projRefId = "hypsasklbmkqagnwhkca";
  supabase link --project-ref "$projRefId";
  shell: /usr/bin/pwsh -command ". '{0}'"
  env:
    OWNER_NAME: EngagedAgility
    REPO_NAME: EAClassManager
    SUPABASE_INTERNAL_IMAGE_REGISTRY: ghcr.io
    SUPABASE_ACCESS_TOKEN: ***
    SUPABASE_DB_PASSWORD: ***
WARN: no SMS provider is enabled. Disabling phone login
Connecting to remote database...
failed to connect to postgres: failed to connect to `host=aws-0-us-west-1.pooler.supabase.com user=postgres.hypsasklbmkqagnwhkca database=postgres`: failed SASL auth (invalid SCRAM server-final-message received from server)
Try rerunning the command with --debug to troubleshoot the error.
Error: Process completed with exit code 1.

My second attempt was after I updated the supabase CLI version to the latest version as of this issue to version v2.22.6. I also tried to use the command with the --password flag, but got the GitHub output above.

I know you mentioned project inactivity in issue #2956, but my project is not inactive. We are 1 to 2 weeks away from paying and going to production, so the project has been active due to me doing testing before we go live, but I just checked again, and we are indeed not inactive.

Note

When running this command locally on my Windows machine, it works with no issue.

To Reproduce
Steps to reproduce the behavior:

1. Create a supabase project
2. Verify the supabase CLI is v2.22.6
3. Create a workflow with a job and a step to link to a supabase project
4. In the step, use the supabase link --project-ref --password command.
5. Observe the result. (If it exists)

Note

My workflow is running on the latest version of Ubuntu, which is v24.04.2

Expected behavior
I expect the CLI to connect to my supabase project with no issues.

System information
NONE. The'- create-ticket' command did not get any information.

Additional context
If applicable, add any other context about the problem here.

• Browser [e.g. chrome, safari]
• Version of supabase-js [e.g. v2.22.0]
• Version of Node.js [e.g. v16.20.0]

I reran the command in my CI environment using the --create-ticket command, but the output did not show
any additional information as shown in the System Information section. Below is the output I got with the additional flag.

  $projRefId = "hypsasklbmkqagnwhkca";
  $dbPassword = "***";
  supabase link --project-ref "$projRefId" --password "$dbPassword --create-ticket";
  shell: /usr/bin/pwsh -command ". '{0}'"
  env:
    OWNER_NAME: EngagedAgility
    REPO_NAME: EAClassManager
    SUPABASE_INTERNAL_IMAGE_REGISTRY: ghcr.io
    SUPABASE_ACCESS_TOKEN: ***
    SUPABASE_DB_PASSWORD: ***
WARN: no SMS provider is enabled. Disabling phone login
Connecting to remote database...
failed to connect to postgres: failed to connect to `host=aws-0-us-west-1.pooler.supabase.com user=postgres.hypsasklbmkqagnwhkca database=postgres`: failed SASL auth (invalid SCRAM server-final-message received from server)
Try rerunning the command with --debug to troubleshoot the error.
Error: Process completed with exit code 1.