Skip to content

Add PostgrestClient to Supabase#1

Merged
satishbabariya merged 1 commit into
supabase:masterfrom
grdsdev:master
Jul 18, 2021
Merged

Add PostgrestClient to Supabase#1
satishbabariya merged 1 commit into
supabase:masterfrom
grdsdev:master

Conversation

@grdsdev

@grdsdev grdsdev commented Jul 17, 2021

Copy link
Copy Markdown
Contributor

What kind of change does this PR introduce?

Feature adding missing PostgrestClient to SupabaseClient.

@satishbabariya satishbabariya merged commit 9bdbb17 into supabase:master Jul 18, 2021
grdsdev added a commit that referenced this pull request Jan 21, 2026
Add three new workflows using shared reusable workflows from supabase/actions:

1. block-merge.yml - Prevents merging of WIP/draft PRs
   - Blocks draft PRs automatically
   - Blocks PRs with 'do-not-merge' label
   - Blocks PRs with 'wip' or 'do not merge' in title

2. stale.yml - Manages stale issues and PRs
   - Issues: 180 days to stale, 30 days to close
   - PRs: 90 days to stale, 14 days to close
   - Exempts priority, security, planned items
   - Runs weekly on Sundays

3. label-issues.yml - Auto-labels by module
   - Extracts scope from PR titles (e.g., fix(auth): → auth label)
   - Parses issue templates for affected modules
   - Supports auth, storage, realtime, functions, database, ci/cd, docs

These workflows use the reusable workflows from supabase/actions
repository (PR #1), which standardizes common CI patterns across
all Supabase repositories.

Benefits:
- Better issue/PR organization
- Automatic triage and cleanup
- Prevents accidental merges of incomplete work
- Consistent with supabase-js patterns

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
grdsdev added a commit that referenced this pull request Jan 22, 2026
…mmary (#887)

* feat(ci): enhance CI with format check, API stability, and success summary

- Update Xcode to 26.2 (latest) while keeping 16.4 and 15.4 for compatibility
- Add format-check job that validates formatting only for changed Swift files, respecting legacy code
- Add api-stability job to detect breaking API changes in PRs using existing script
- Add ci-success summary job that provides single point for branch protection requirements

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* fix(ci): use branch name instead of remote-tracking branch for API stability check

* perf(ci): optimize matrix strategy and add job dependencies

Matrix optimization:
- Reduce macos job from 8 to 6 combinations (25% reduction)
- Test older Xcode (16.4) only on iOS, the most common platform
- Keep full platform coverage (iOS + macOS) on latest Xcode 26.2
- Saves ~2 jobs per CI run, reducing runner time and costs

Job dependencies:
- examples job now depends on macos and spm jobs
- docs job now depends on macos job
- Enables fail-fast behavior: skip expensive jobs if basic builds fail
- Provides faster feedback on broken PRs

Expected impact: 30-35% faster CI on PRs, ~35% cost reduction

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* perf(ci): optimize cache strategy and consolidate SPM builds

Cache optimization:
- Switch from hashing source files to Package.resolved for cache keys
- Source files change frequently, causing cache misses on every commit
- Package.resolved only changes when dependencies update
- Add multi-level restore-keys for better fallback matching
- Expected improvement: 60-80% cache hit rate vs current ~20-30%

SPM build consolidation:
- Run standalone SPM job only on main branch and manual dispatch
- SPM compilation already tested by macos job via xcodebuild
- Linux job provides separate SPM validation
- Removes redundant 2-job SPM build from every PR
- Saves ~4-6 minutes per PR run

Combined impact: Faster builds through better caching, reduced redundant jobs

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* fix(ci): revert matrix optimization to debug test failures

Reverting the explicit matrix structure back to combinatorial matrix while keeping other optimizations. This will help isolate which change is causing the test failures.

* perf(ci): reduce matrix from 8 to 6 jobs using exclude

Successfully tested in PR #888 - using matrix.exclude to remove
MACOS+Xcode 16.4 combinations while keeping all other jobs.

Matrix configuration:
- Latest Xcode 26.2: Full platform coverage (IOS + MACOS) = 4 jobs
- Older Xcode 16.4: iOS only (most common platform) = 2 jobs
- Total: 6 jobs (down from 8, 25% reduction)

Benefits:
- 25% fewer jobs per CI run
- ~2 jobs saved per run
- Additional 10-15% time savings per PR
- Combined with other optimizations: 40-50% total improvement

Testing: All 6 jobs passed in PR #888 test run

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* feat(ci): add reusable workflow integrations

Add three new workflows using shared reusable workflows from supabase/actions:

1. block-merge.yml - Prevents merging of WIP/draft PRs
   - Blocks draft PRs automatically
   - Blocks PRs with 'do-not-merge' label
   - Blocks PRs with 'wip' or 'do not merge' in title

2. stale.yml - Manages stale issues and PRs
   - Issues: 180 days to stale, 30 days to close
   - PRs: 90 days to stale, 14 days to close
   - Exempts priority, security, planned items
   - Runs weekly on Sundays

3. label-issues.yml - Auto-labels by module
   - Extracts scope from PR titles (e.g., fix(auth): → auth label)
   - Parses issue templates for affected modules
   - Supports auth, storage, realtime, functions, database, ci/cd, docs

These workflows use the reusable workflows from supabase/actions
repository (PR #1), which standardizes common CI patterns across
all Supabase repositories.

Benefits:
- Better issue/PR organization
- Automatic triage and cleanup
- Prevents accidental merges of incomplete work
- Consistent with supabase-js patterns

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* ci: use sha instead of branch

---------

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
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.

2 participants