Repository navigation
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018s7p4uu8gLGvgvJAHujagc
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Deploy →
|
|
Generated by Claude Code |
There was a problem hiding this comment.
🟡 Changes recommended
Stale follower state, delayed synchronization, future migration dating, and missing integration coverage must be addressed.
3 open findings
What changed in this PR
Adds SoundCloud follower persistence to the Link Wizard and grants authorized admins database write access.
Changes:
- Stages and saves candidate follower counts.
- Adds secure SoundCloud insert/update policies.
- Adds candidate-selection unit tests.
| File | Description |
|---|---|
supabase/migrations/20261013060000_soundcloud_admin_write_policies.sql |
Adds admin write policies. |
src/pages/admin/festivals/LinkWizard/LinkWizardStep.tsx |
Stages follower counts for saving. |
src/api/artistSearch/mergeCandidateSelection.ts |
Extracts SoundCloud candidate followers. |
src/api/artistSearch/mergeCandidateSelection.test.ts |
Tests follower-selection behavior. |
src/api/artists/useUpdateArtist.ts |
Upserts followers into SoundCloud data. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| if (data.soundcloud_followers !== undefined) { | ||
| updates.soundcloud_followers = data.soundcloud_followers; | ||
| } |
There was a problem hiding this comment.
Not adding this here: the existing Link Wizard integration suite stubs Spotify-only search results and I have no local Supabase to verify a new SoundCloud/RLS case. Unit tests cover the selection logic; the integration + non-admin RLS case is left for a follow-up.
Generated by Claude Code
There was a problem hiding this comment.
you should have access to staging supabase
There was a problem hiding this comment.
The session only has the staging anon key (VITE_SUPABASE_URL + publishable key). The integration fixtures (signInAsTestUser, grantAdminRole) need the service-role admin API, and the harness is built for a local stack, so I can't run the test, and I'd rather not push one unverified. If you can expose a staging service-role key to the routine environment (or run pnpm run test:integration locally), I'll add the SoundCloud follower + non-admin RLS cases. Otherwise it's a follow-up.
Generated by Claude Code
…syncable Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018s7p4uu8gLGvgvJAHujagc
Playwright test resultsDetails
|
|
Generated by Claude Code |
|
Generated by Claude Code |
|
CI is red on Generated by Claude Code |
|
CI Generated by Claude Code |


UPL-39: selecting a SoundCloud candidate in the Link Wizard now saves its follower count to
soundcloud.followers_countalongside the URL (Spotify unchanged; the nextsync-artist-datarun may overwrite it). Adds admin insert/update RLS policies onsoundcloud, since only the service role could write it before.Verification
soundcloud_followers.soundcloudrow is written.soundcloudis still rejected by RLS.Note: the migration needs the
staginglabel to pass the migration gate; no integration test added (no local Supabase available to verify one).🤖 Generated with Claude Code
https://claude.ai/code/session_018s7p4uu8gLGvgvJAHujagc
Generated by Claude Code