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
{{ message }}
Repository navigation
Commit eb5ae65
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ops): flag unreadable deploy dates and name the CLI's target
A function whose deploy date is missing or unreadable was compared as
current, so a stale function could pass unnoticed. It is now listed as
changed with "deploy date unknown".
The report label read the linked ref file, but the Supabase CLI prefers
SUPABASE_PROJECT_ID over it, so the label could name a different project
than the one inspected. The label now follows the CLI's order.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/operations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ Do not enable the staging repository variable before every prerequisite is prese
65
65
66
66
## Backend drift check
67
67
68
-
`npm run backend:status` shows what the current commit has that a Supabase project lacks. It inspects the linked project; `npm run backend:status -- --project-ref <ref>` inspects another one. It runs `supabase migration list` and `supabase functions list` and changes no schema, data, functions, or secrets. To connect to the database, the CLI creates its usual short-lived login role.
68
+
`npm run backend:status` shows what the current commit has that a Supabase project lacks. It inspects the project the Supabase CLI resolves, which is `SUPABASE_PROJECT_ID` when that is set and the linked project otherwise; `npm run backend:status -- --project-ref <ref>` inspects another one. It runs `supabase migration list` and `supabase functions list` and changes no schema, data, functions, or secrets. To connect to the database, the CLI creates its usual short-lived login role.
69
69
70
70
The comparison uses the committed tree at `HEAD`, so commit or stash local edits first. It reports:
if(dirty)notes.push("uncommitted changes under supabase/ are not part of this comparison.");
261
272
notes.push("function change dates come from git. A function deployed from a branch before its merge shows as changed; one deployed from an out-of-date checkout looks current.");
262
273
274
+
// Same order the Supabase CLI uses: the flag, then SUPABASE_PROJECT_ID, then the linked ref.
0 commit comments