user-feedback: verify migration deployment order and authenticated integrations
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- supabase
- Domain
- authentication, databases, documentation
Research direction
Open skills/supabase/SKILL.md and read Core Principles > 2. Verify your work and Making and Committing Schema Changes. Update the documented verification checklist for migration rollout compatibility, authenticated application paths, external-provider calls, and blocked local database checks. Done means the workflow explicitly covers each requested gate and incomplete verification is not treated as complete.
Written by the indexing model from the issue text.
Description
What happened
Task: Add a Supabase-backed multi-currency feature that introduced a household column, enriched snapshot RPCs, and authenticated historical exchange-rate lookups.
Skill said: Verify the work and follow the migration workflow, but it did not make deployment-order compatibility or an authenticated end-to-end request a required completion gate.
Expected: When application parsing depends on a new migration, verification should confirm that old-schema/new-app and new-schema/old-app rollout states remain safe. A new authenticated API or Server Action path that also calls an external provider should be exercised end to end before the feature is reported complete. If the local database cannot run because Docker is unavailable, that limitation should prevent treating the database integration as fully verified unless an equivalent remote or branch verification succeeds.
Source
File: skills/supabase/SKILL.md
Section: Core Principles > 2. Verify your work and Making and Committing Schema Changes
Fix suggestion
Add a rollout and integration checklist:
- Verify migration history and schema state before deploying code that requires new RPC fields.
- Require backward-compatible parsing during rolling deployments.
- Exercise new authenticated routes or Server Actions with a real session.
- Exercise external-provider calls from the actual application runtime, not only a mocked unit test.
- If local Supabase verification is blocked, require a branch/remote test or explicitly mark the database integration incomplete.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/agent-skills
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
supabase/agent-skills#586 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#585 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
supabase/agent-skills#583 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
supabase/agent-skills#582 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#581 ·
All issues in supabase/agent-skills
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100