Skip to content

Version Packages (alpha-v5) - #2397

Merged
dimkl merged 1 commit into
mainfrom
changeset-release/main
Dec 21, 2023
Merged

Version Packages (alpha-v5)#2397
dimkl merged 1 commit into
mainfrom
changeset-release/main

Conversation

@clerk-cookie

@clerk-cookieclerk-cookie commented Dec 19, 2023•
edited
Loading

Copy link
Copy Markdown
Collaborator

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@clerk/clerk-js@5.0.0-alpha-v5.12

Major Changes

  • Path-based routing is now the default routing strategy if the path prop is filled. Additionally, if the path and routing props are not filled, an error will be thrown. (#2338) by @octoper

    // Without path or routing props, an error with be thrown<UserProfile/><CreateOrganization/><OrganizationProfile/><SignIn/><SignUp/>// Alternative #1<UserProfilepath="/whatever"/><CreateOrganizationpath="/whatever"/><OrganizationProfilepath="/whatever"/><SignInpath="/whatever"/><SignUppath="/whatever"/>// Alternative #2<UserProfilerouting="hash_or_virtual"/><CreateOrganizationrouting="hash_or_virtual"/><OrganizationProfilerouting="hash_or_virtual"/><SignInrouting="hash_or_virtual"/><SignUprouting="hash_or_virtual"/>

  • Make the user name on clickable, i.e. part of the button's trigger. (#2411) by @marcelscruz

    This change inverts the positions of cl-userButtonTrigger and cl-userButtonBox, the latter now being a child of the former.

  • Consolidate afterSignOutOneUrl & afterSignOutAllUrl to afterSignOutUrl and drop usage of Dashboard settings in ClerkJS components. The Dashboard settings should only apply to the Account Portal application. (#2414) by @dimkl

Minor Changes

  • Remove MemberRole TypeMemberRole would always include the old role keys admin, member, guest_member. (#2388) by @panteliselef

    If developers still depend on them after the introduction of custom roles, the can provide them as their custom types for authorization.

    // clerk.d.tsexport{};interfaceClerkAuthorization{permission: '';role: 'admin'|'basic_member'|'guest_member';}

  • Update @clerk/clerk-js and @clerk/clerk-react to support the following examples: (#2412) by @dimkl

    Clerk.signOut({redirectUrl: '/'})<SignOutButtonredirectUrl='/'/>// uses Clerk.signOut({ redirectUrl: '/' })<UserButtonafterSignOutUrl='/after'/>// uses Clerk.signOut({ redirectUrl: '/after' })<ClerkProviderafterSignOutUrl='/after'/>// uses Clerk.signOut({ redirectUrl: '/after' })

Patch Changes

  • Prevent submitting on enter in Organization Profile form when submit button is disabled. (#2400) by @panteliselef

  • Bug fix: Clear feedback of input field if setError is called with undefined. (#2399) by @panteliselef

  • Updated dependencies [fe2607b6f, 2e4a43017]:

    • @clerk/types@4.0.0-alpha-v5.12

@clerk/nextjs@5.0.0-alpha-v5.13

Major Changes

  • Path-based routing is now the default routing strategy if the path prop is filled. Additionally, if the path and routing props are not filled, an error will be thrown. (#2338) by @octoper

    // Without path or routing props, an error with be thrown<UserProfile/><CreateOrganization/><OrganizationProfile/><SignIn/><SignUp/>// Alternative #1<UserProfilepath="/whatever"/><CreateOrganizationpath="/whatever"/><OrganizationProfilepath="/whatever"/><SignInpath="/whatever"/><SignUppath="/whatever"/>// Alternative #2<UserProfilerouting="hash_or_virtual"/><CreateOrganizationrouting="hash_or_virtual"/><OrganizationProfilerouting="hash_or_virtual"/><SignInrouting="hash_or_virtual"/><SignUprouting="hash_or_virtual"/>

Patch Changes

@clerk/clerk-react@5.0.0-alpha-v5.12

Major Changes

  • Path-based routing is now the default routing strategy if the path prop is filled. Additionally, if the path and routing props are not filled, an error will be thrown. (#2338) by @octoper

    // Without path or routing props, an error with be thrown<UserProfile/><CreateOrganization/><OrganizationProfile/><SignIn/><SignUp/>// Alternative #1<UserProfilepath="/whatever"/><CreateOrganizationpath="/whatever"/><OrganizationProfilepath="/whatever"/><SignInpath="/whatever"/><SignUppath="/whatever"/>// Alternative #2<UserProfilerouting="hash_or_virtual"/><CreateOrganizationrouting="hash_or_virtual"/><OrganizationProfilerouting="hash_or_virtual"/><SignInrouting="hash_or_virtual"/><SignUprouting="hash_or_virtual"/>

  • Consolidate afterSignOutOneUrl & afterSignOutAllUrl to afterSignOutUrl and drop usage of Dashboard settings in ClerkJS components. The Dashboard settings should only apply to the Account Portal application. (#2414) by @dimkl

Minor Changes

  • Remove MemberRole TypeMemberRole would always include the old role keys admin, member, guest_member. (#2388) by @panteliselef

    If developers still depend on them after the introduction of custom roles, the can provide them as their custom types for authorization.

    // clerk.d.tsexport{};interfaceClerkAuthorization{permission: '';role: 'admin'|'basic_member'|'guest_member';}

  • Update @clerk/clerk-js and @clerk/clerk-react to support the following examples: (#2412) by @dimkl

    Clerk.signOut({redirectUrl: '/'})<SignOutButtonredirectUrl='/'/>// uses Clerk.signOut({ redirectUrl: '/' })<UserButtonafterSignOutUrl='/after'/>// uses Clerk.signOut({ redirectUrl: '/after' })<ClerkProviderafterSignOutUrl='/after'/>// uses Clerk.signOut({ redirectUrl: '/after' })

Patch Changes

@clerk/remix@4.0.0-alpha-v5.13

Major Changes

  • Path-based routing is now the default routing strategy if the path prop is filled. Additionally, if the path and routing props are not filled, an error will be thrown. (#2338) by @octoper

    // Without path or routing props, an error with be thrown<UserProfile/><CreateOrganization/><OrganizationProfile/><SignIn/><SignUp/>// Alternative #1<UserProfilepath="/whatever"/><CreateOrganizationpath="/whatever"/><OrganizationProfilepath="/whatever"/><SignInpath="/whatever"/><SignUppath="/whatever"/>// Alternative #2<UserProfilerouting="hash_or_virtual"/><CreateOrganizationrouting="hash_or_virtual"/><OrganizationProfilerouting="hash_or_virtual"/><SignInrouting="hash_or_virtual"/><SignUprouting="hash_or_virtual"/>

Patch Changes

@clerk/backend@1.0.0-alpha-v5.11

Minor Changes

  • Add createOrganizationEnabled param in @clerk/backend method User.updateUser() (#2415) by @dimkl

    Example:

    import{createClerkClient}from'@clerk/backend';constclerkClient=createClerkClient({...});awaitclerkClient.users.updateUser('user_...',{createOrganizationEnabled: true})

Patch Changes

  • OrganizationMembershipRole should respect authorization types provided by the developer if those exist. (#2408) by @panteliselef

  • Fixed an issue where errors returned from backend api requests are not converted to camelCase. (#2423) by @Nikpolik

@clerk/types@4.0.0-alpha-v5.12

Minor Changes

  • Remove MemberRole TypeMemberRole would always include the old role keys admin, member, guest_member. (#2388) by @panteliselef

    If developers still depend on them after the introduction of custom roles, the can provide them as their custom types for authorization.

    // clerk.d.tsexport{};interfaceClerkAuthorization{permission: '';role: 'admin'|'basic_member'|'guest_member';}

  • Update @clerk/clerk-js and @clerk/clerk-react to support the following examples: (#2412) by @dimkl

    Clerk.signOut({redirectUrl: '/'})<SignOutButtonredirectUrl='/'/>// uses Clerk.signOut({ redirectUrl: '/' })<UserButtonafterSignOutUrl='/after'/>// uses Clerk.signOut({ redirectUrl: '/after' })<ClerkProviderafterSignOutUrl='/after'/>// uses Clerk.signOut({ redirectUrl: '/after' })

@clerk/chrome-extension@1.0.0-alpha-v5.12

Patch Changes

@clerk/clerk-expo@1.0.0-alpha-v5.12

Patch Changes

@clerk/fastify@1.0.0-alpha-v5.13

Patch Changes

gatsby-plugin-clerk@5.0.0-alpha-v5.13

Patch Changes

@clerk/clerk-sdk-node@5.0.0-alpha-v5.11

Patch Changes

@clerk/elements@0.0.2-alpha-v5.1

Patch Changes

@github-actions
github-actionsBotforce-pushed the changeset-release/main branch 16 times, most recently from fe93774 to 1fc1308CompareDecember 20, 2023 12:52
@github-actions
github-actionsBotforce-pushed the changeset-release/main branch 9 times, most recently from a7d4a6f to 84d5951CompareDecember 21, 2023 09:09
@github-actions
github-actionsBotforce-pushed the changeset-release/main branch from 84d5951 to 84a01e4CompareDecember 21, 2023 09:27
@dimkldimkl closed this Dec 21, 2023
@dimkldimkl reopened this Dec 21, 2023
@dimkl
dimkl added this pull request to the merge queue Dec 21, 2023
Merged via the queue into main with commit 4070cfeDec 21, 2023
@dimkl
dimkl deleted the changeset-release/main branch December 21, 2023 10:01
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer
@dimkldimkldimkl approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

backendchrome-extensionclerk-jselementsexpofastifylocalizationsnextjsreactremixsdk-nodethemestypes

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@clerk-cookie@dimkl