Skip to content

Ship the supabase provider microsite: live smoke run, featured image, docs corrections - #4

Merged
jeffreyaven merged 8 commits into
mainfrom
feature/provider-dev
Oct 12, 2026
Merged

jeffreyaven merged 8 commits into
mainfrom
feature/provider-dev

Conversation

@jeffreyaven

@jeffreyaven jeffreyaven commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Ships the provider microsite and records the first live smoke run.

  • Live smoke run against the standing dev project: 52 passed, 0 failed, 2 skipped. Harness fixes (API key naming and per-endpoint pacing, token-scope and empty-config SKIPs) - NOTES.md findings 18 and 19.
  • Website: Back to StackQL Docs sidebar link, source project link, Supabase featured image, projectName/editUrl, docs header corrections (158 operations / 14 services / 65 resources), docs regenerated.
  • provider-utils 0.7.12.

Merging deploys the microsite to GitHub Pages (prod-web-deploy.yml); served at supabase-provider.stackql.io once the Pages custom domain and the DNS CNAME -> stackql.github.io are in place.

jeffreyaven and others added 3 commits October 6, 2026 16:38
…epo link

Bumps @stackql/provider-utils to 0.7.11, passes --source-project to the
doc generation target and regenerates the markdown docs, so the provider
summary links to the source repository.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Opens the docs sidebar with a link to /stackqldocs, the redirect to the
main stackql.io docs, matching the query library site and the provider
template. Styled by the new .sidebar-back-link rules in the site
stylesheet. No generated docs or dependencies change.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Keeps the doc generation dependency on the current release. 0.7.12 only
changes the generate-docs-v2 index page (Markdown hard breaks in the
Provider Summary); this provider uses the v1 generator, whose output is
unchanged, so the regenerated docs are identical.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@jeffreyaven jeffreyaven self-assigned this Oct 6, 2026
jeffreyaven and others added 2 commits October 12, 2026 12:04
Harness fixes from the run, all classification and pacing, no provider
defects: API key names use the vendor-validated stackql_smoke_<stamp>
form (sweep matches both prefixes); API key writes pause 6 s for the
stricter per-endpoint limit; profile.profiles SKIPs under an
organization-scoped token (probed once, since pystackql returns an empty
list for a failed SELECT); config.postgres_configs SKIPs when the project
has no overrides (the API returns {} and the engine cannot bind an empty
flat object - reproduced on v0.12.778). NOTES.md findings 18 and 19 and
the live-run record; tests/live_probe.sh for one-off live checks.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Featured image composed in the house style (STACKQL>> wordmark plus the
Supabase mark, 1200x627) replacing the generic placeholder; projectName
and editUrl set as on the snowflake site; the index copy corrected to
158 operations / 14 services / 65 resources, with notes on token scope
and the empty postgres_configs case. Docs regenerated with make docs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jeffreyaven jeffreyaven changed the title website: add the Back to StackQL Docs link and the source repo link Ship the supabase provider microsite: live smoke run, featured image, docs corrections Oct 12, 2026
jeffreyaven and others added 3 commits October 12, 2026 13:12
An in-path parameter must have a matching {name} placeholder in its
path key. The ref rebase strips ref from the mapped verbs only, so the
skip-coded HEAD action-run count on /actions kept a ref path parameter
the path no longer carries (stackql/stackql-provider-registry#476
review). New rule 8 checks every path-item and operation parameter list
against its path key on all OpenAPI operation verbs and drops orphans -
no names, verbs or paths special-cased. One parameter dropped
(branches.yaml HEAD /actions); idempotent; make test green.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
make smoke-live against supabase v26.10.00477 in the public registry:
52 passed, 0 failed, 2 skipped, matching the local-registry run. The
binary does not auto-pull a provider under pystackql, so the first
--live attempt read no rows everywhere; --live now runs REGISTRY PULL
supabase and fails fast if SHOW SERVICES is empty.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jeffreyaven
jeffreyaven merged commit 1dc1c38 into main Oct 12, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant