buildmymcpserver/apps/web/app/(dashboard)/servers
Marco Sadjadi 2a12ea18cd
All checks were successful
Deploy to Production / deploy (push) Successful in 1m24s
fix(wizard): editable slug on confirm step so slug_taken (409) is fixable in place
POST /v1/servers returns 409 slug_taken when the org already has that slug. The error told users to change the slug field above, but the normal (non-fork) flow had no slug field on the confirm step - only Step 1 did - leaving them stuck. Now Name+Slug are editable on the confirm step for the normal flow too, mirroring the fork flow, so a slug conflict is resolved without going back.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-31 19:56:45 +02:00
..
[id] feat(dashboard): delete button on server detail page 2026-05-28 21:44:52 +02:00
new fix(wizard): editable slug on confirm step so slug_taken (409) is fixable in place 2026-05-31 19:56:45 +02:00
page.tsx feat(web): dashboard, wizard, server detail, WS build stream, install snippets 2026-05-19 00:32:53 +02:00