Conversation
* fix(vendors): skip assignee validation when assignee hasn't changed The form sends the existing assigneeId on every PATCH even when the user only changed a different field (e.g. website). If the vendor's current assignee is a platform admin, every update fails with "Cannot assign a platform admin as assignee" — even though no one is trying to change the assignee. Only run validateAssigneeNotPlatformAdmin when assigneeId is actually being changed to a different value. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(vendors): don't assign platform admins as vendor assignees during onboarding The vendor mitigation task assigned vendors to whoever triggered onboarding (authorId). When a platform admin onboards a customer, all vendors get assigned to the admin. Since platform admins are filtered from the UI assignee list, vendors appear "Unassigned" but the backend still has the admin's member ID — which then blocks all PATCH updates with "Cannot assign a platform admin". Two fixes: - Service: only validate assignee when it's actually changing - Onboarding: skip assignee if author is a platform admin Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Mariano Fuentes <marfuen98@gmail.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryMedium Risk Overview Updates onboarding’s Written by Cursor Bugbot for commit 9e508c2. This will update automatically on new commits. Configure here. |
|
🎉 This PR is included in version 3.11.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
2 participants
This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.