Error when generating signing keys.

[Marley-Mulvin-Broome]

Describe the bug Cannot generate signing keys with supabase gen signing-key --algorithm ES256 when signing_key.json file is not already present. When you try, you get failed to read signing keys: open supabase/signing_key.json: no such file or directory.

To Reproduce Steps to reproduce the behavior:

1. Have version 2.58.5 of the Supabase CLI.
2. Do not have the file supabase/signing_key.json present in your project.
3. Uncomment / set auth.signing_keys_path to supabase/signing_key.json
4. Run supabase gen signing-key --algorithm ES256.

Expected behavior Should create the file even if it is not present rather than failing to stat it.

System information Rerun the failing command with --create-ticket flag.

• Ticket ID: Create ticket flag didnt work ☹️
• Version of OS: Ubuntu 24.04.3 LTS x86_64
• Version of CLI: 2.58.5
• Version of Docker: 28.5.2
• Versions of services:

   SERVICE IMAGE          | LOCAL                  | LINKED     
  ------------------------|------------------------|------------
   supabase/postgres      | 17.6.1.008             | 17.6.1.008 
   supabase/gotrue        | v2.179.0               | -          
   postgrest/postgrest    | v13.0.5                | -          
   supabase/realtime      | v2.63.0                | -          
   supabase/storage-api   | v1.29.0                | -          
   supabase/edge-runtime  | v1.69.23               | -          
   supabase/studio        | 2025.11.10-sha-5291fe3 | -          
   supabase/postgres-meta | v0.93.1                | -          
   supabase/logflare      | 1.25.3                 | -          
   supabase/supavisor     | 2.7.4                  | -  

Additional context When you create the json file with the following contents it seems to work as per usual (empty array): [].

This bug is not present when I was using version v2.39.2.

[Marley-Mulvin-Broome]

Ah okay I realised the issue is that in my config.toml the auth.signing_keys_path was set. (On init I believe it would be commented out and you wouldn't get this error).

I do think that it'd be nice if there was some hint when this happens :^) This is because I am not committing my signing keys as the docs say, so when I am on a fresh environment I get an error.