Repository navigation
Conversation
… logo upload fails
🦋 Changeset detectedLatest commit: 5e77a17 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-biometrics
@clerk/expo-google-signin
@clerk/expo-native-components
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/mosaic
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
|

Description
In Mosaic's
TaskChooseOrganization, if the logo upload failed after the organization was created, the new organization was never set active. The user was left with an organization they couldn't use, and the task didn't complete. The legacy component ignores the logo failure and carries on, so this does the same: create, try the logo, then always set active and finish the task.CreateOrganizationkeeps its current behavior (the error is shown and the org isn't activated), which also matches legacy.Follow-up, not in this PR: Mosaic doesn't pre-fill the default logo from organization creation defaults the way legacy does.
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change