Skip to content
Latchkey

Validate SDK Compliance workflow (supabase/supabase-py)

The Validate SDK Compliance workflow from supabase/supabase-py, explained and optimized by Latchkey.

C

CI health: C - fair

Run this on Latchkey for self-healing, caching, and up to 58% lower cost.

Grade your own workflow free or run it on Latchkey →
Source: supabase/supabase-py.github/workflows/validate-capabilities.ymlLicense MITView source

What it does

This is the Validate SDK Compliance workflow from the supabase/supabase-py repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)
name: Validate SDK Compliance

on:
  push:
    branches:
      - main
  pull_request:

permissions:
  contents: read

jobs:
  validate:
    uses: supabase/sdk/.github/workflows/validate-sdk-compliance.yml@main
    with:
      language: python
      griffe-packages: >-
        supabase supabase_auth postgrest storage3 realtime supabase_functions
      griffe-search-paths: >-
        src/supabase/src,src/auth/src,src/postgrest/src,src/storage/src,src/realtime/src,src/functions/src

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Validate SDK Compliance
 
on:
  push:
    branches:
      - main
  pull_request:
 
permissions:
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  validate:
    timeout-minutes: 30
    uses: supabase/sdk/.github/workflows/validate-sdk-compliance.yml@main
    with:
      language: python
      griffe-packages: >-
        supabase supabase_auth postgrest storage3 realtime supabase_functions
      griffe-search-paths: >-
        src/supabase/src,src/auth/src,src/postgrest/src,src/storage/src,src/realtime/src,src/functions/src
 

What changed

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.