Repository navigation
Conversation
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit b1f7406)
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit 970487f)
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit 5357203)
(cherry picked from commit 6570638)
(cherry picked from commit 6a0b01b)
Co-authored-by: Tushar Pagar <240662211+tushardev-365@users.noreply.github.com> (cherry picked from commit 3c98900)
(cherry picked from commit b5a38f1)
(cherry picked from commit 2a795a7)
(cherry picked from commit 80fcba7)
(cherry picked from commit 3c1b4a1)
(cherry picked from commit 9611cb7)
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit 5e55db5)
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit ed93913)
(cherry picked from commit ce24abf)
(cherry picked from commit a662a51)
This was referenced Oct 20, 2026
Contributor
|
The following capabilities are marked
The following capabilities are marked
These may have been renamed, removed, or never registered. Please update the capability matrix. |
This was referenced Oct 20, 2026
spydon
added this pull request to stack #1799
October 20, 2026 15:08
grdsdev
approved these changes
Oct 20, 2026
The postgrest and supabase build-sync recipes edit _sync source files that v3 no longer has, and the supabase one would regenerate its hand-written sync client. They are removed with their unasync scripts and the GNU sed check that only they used. AGENTS.md now describes how v3 lays out its async and sync code and lists utils among the packages whose import name differs.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-picks main's repository-level commits onto v3: CI and action pin bumps, dependency bumps, the SDK compliance workflow and
sdk-compliance.yaml, CODEOWNERS, CONTRIBUTING,gnu-sed.mkand AGENTS.md.uv.lockbumps were regenerated against v3's lock at the same versions main picked.build-sync(postgrest, supabase).sdk-compliance.yamlstill lists v2 symbol names here. chore: sync sdk-compliance.yaml with the v3 public API #1790 at the top of the stack rewrites it for v3.Review fixes
build-synctargets are removed, with their unasync scripts and the GNU sed check. They edited_syncsource files that v3 no longer has, and the supabase one would have regenerated its hand-written sync client.utils→supabase_utils.Commits
Stack
This replaces #1789: main's changes since 6f522d3 are cherry-picked onto v3 one package at a time, so each part can be reviewed on its own. Merge from the bottom up.