fix(providers): fix supabase apikey interpolation#5575
Open
hassan254-prog wants to merge 3 commits intomasterfrom
Open
fix(providers): fix supabase apikey interpolation#5575hassan254-prog wants to merge 3 commits intomasterfrom
hassan254-prog wants to merge 3 commits intomasterfrom
Conversation
Contributor
There was a problem hiding this comment.
Found a documentation anchor mismatch that breaks a deep link and needs alignment.
Status: Changes Suggested | Risk: Medium
Issues Identified & Suggestions
- Fix heading anchor to match referenced doc section for deep links:
docs/api-integrations/supabase/connect.mdx
Review Details
📁 14 files reviewed | 💬 1 comments
Instruction Files
├── .claude/
│ ├── agents/
│ │ └── nango-docs-migrator.md
│ └── skills/
│ ├── agent-builder-skill/
│ │ ├── EXAMPLES.md
│ │ └── SKILL.md
│ ├── creating-integration-docs/
│ │ └── SKILL.md
│ └── creating-skills-skill/
│ └── SKILL.md
├── AGENTS.md
└── GEMINI.md
👍 / 👎 individual comments to help improve reviews for you
hassan254-prog
commented
Mar 5, 2026
| proxy: | ||
| base_url: https://${connectionConfig.projectUrl} | ||
| headers: | ||
| authorization: Bearer ${credentials.apiKey} |
Contributor
Author
There was a problem hiding this comment.
Currently the api_key auth mode, interpolations are handled with the ${apiKey}, the ${credenails.key} format is only for TWO_STEP.
hassan254-prog
commented
Mar 5, 2026
| credentials: | ||
| apiKey: | ||
| type: string | ||
| title: API Key |
Contributor
Author
There was a problem hiding this comment.
Supabase is encouraging users to use their newer Keys, anon and service_role keys are legacy.
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.
Fix Supabase API key interpolation and update Supabase docs paths
This PR fixes Supabase proxy header interpolation to use
apiKeydirectly inpackages/providers/providers.yaml, aligning with how credentials are passed at runtime. It also updates Supabase doc links and navigation to the newapi-integrationspaths and replaces legacy Supabase docs underdocs/integrations/allwith updated content indocs/api-integrations.Key Changes
• Updated Supabase proxy headers in
packages/providers/providers.yamlto useauthorization: Bearerandapikey:• Repointed Supabase docs links and navigation entries to
docs/api-integrations/supabase.mdxanddocs/api-integrations/supabase/connect.mdxviapackages/providers/providers.yamlanddocs/docs.json• Replaced legacy Supabase docs in
docs/integrations/allwith new quickstart and connect content underdocs/api-integrationsPossible Issues
• If any templates or consumers still reference
credentials.apiKeyfor proxy headers, the newapiKeyinterpolation could be inconsistent outside Supabase.• Legacy Supabase doc URLs may require redirects if external links target
docs/integrations/all/supabase.This summary was automatically generated by @propel-code-bot