Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Version Packages (alpha-v5) #2554

Merged
merged 1 commit into from
Jan 11, 2024
Merged

Version Packages (alpha-v5) #2554

merged 1 commit into from
Jan 11, 2024

Conversation

clerk-cookie
Copy link
Collaborator

@clerk-cookie clerk-cookie commented Jan 11, 2024 •
edited

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/backend@1.0.0-alpha-v5.15

Major Changes

  • Change SessionApi.getToken() to return consistent { data, errors } return value (#2539) by @dimkl

    and fix the getToken() from requestState to have the same return behavior as v4
    (return Promise or throw error).
    This change fixes issues with getToken() in @clerk/nextjs / @clerk/remix / @clerk/fastify / @clerk/sdk-node / gatsby-plugin-clerk:

    Example:

    import { getAuth } from '@clerk/nextjs/server';

const { getToken } = await getAuth(...);
const jwtString = await getToken(...);

    The change in SessionApi.getToken() return value is a breaking change, to keep the existing behavior use the following:

    import { ClerkAPIResponseError } from '@clerk/shared/error';

const response = await clerkClient.sessions.getToken(...);

if (response.errors) {
    const { status, statusText, clerkTraceId } = response;
    const error = new ClerkAPIResponseError(statusText || '', {
        data: [],
        status: Number(status || ''),
        clerkTraceId,
    });
    error.errors = response.errors;

    throw error;
}

// the value of the v4 `clerkClient.sessions.getToken(...)`
const jwtString = response.data.jwt;

Minor Changes

  • Replace the Clerk-Backend-SDK header with User-Agent in BAPI requests and update it's value to contain both the package name and the package version of the clerk package (#2558) by @dimkl

    executing the request. Eg request from @clerk/nextjs to BAPI with append User-Agent: @clerk/nextjs@5.0.0-alpha-v5.16 using the latest version.

    Miscellaneous changes: The backend test build changed to use tsup.

Patch Changes

  • Updated dependencies [8cc45d2af]:
    • @clerk/shared@2.0.0-alpha-v5.10

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

Minor Changes

  • Replace the Clerk-Backend-SDK header with User-Agent in BAPI requests and update it's value to contain both the package name and the package version of the clerk package (#2558) by @dimkl

    executing the request. Eg request from @clerk/nextjs to BAPI with append User-Agent: @clerk/nextjs@5.0.0-alpha-v5.16 using the latest version.

    Miscellaneous changes: The backend test build changed to use tsup.

Patch Changes

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

Minor Changes

  • Replace the Clerk-Backend-SDK header with User-Agent in BAPI requests and update it's value to contain both the package name and the package version of the clerk package (#2558) by @dimkl

    executing the request. Eg request from @clerk/nextjs to BAPI with append User-Agent: @clerk/nextjs@5.0.0-alpha-v5.16 using the latest version.

    Miscellaneous changes: The backend test build changed to use tsup.

Patch Changes

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

Minor Changes

  • Replace the Clerk-Backend-SDK header with User-Agent in BAPI requests and update it's value to contain both the package name and the package version of the clerk package (#2558) by @dimkl

    executing the request. Eg request from @clerk/nextjs to BAPI with append User-Agent: @clerk/nextjs@5.0.0-alpha-v5.16 using the latest version.

    Miscellaneous changes: The backend test build changed to use tsup.

Patch Changes

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

Minor Changes

  • Apply the following changes to components with routing props: (#2543) by @dimkl

    • default is routing="path" and path prop is required to be set via env or context
    • when routing="hash" or routing="virtual" is set the implicit (via env or context) path option is ignored
    • when routing="hash" or routing="virtual" then path prop is not allowed to be set

    Examples of components with routing props:

    • <CreateOrganization />
    • <OrganizationProfile />
    • <SignIn />
    • <SignUp />
    • <UserProfile />

Patch Changes

  • Allow dynamic values components props, even if these values change after the components are rendered. For example, a SignIn component with a redirectUrl prop passed in will always respect the latest value of redirectUrl. (#2515) by @nikosdouvlis

  • Updated dependencies [8cc45d2af]:

    • @clerk/shared@2.0.0-alpha-v5.10

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

Minor Changes

  • Replace the Clerk-Backend-SDK header with User-Agent in BAPI requests and update it's value to contain both the package name and the package version of the clerk package (#2558) by @dimkl

    executing the request. Eg request from @clerk/nextjs to BAPI with append User-Agent: @clerk/nextjs@5.0.0-alpha-v5.16 using the latest version.

    Miscellaneous changes: The backend test build changed to use tsup.

Patch Changes

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

Minor Changes

  • Replace the Clerk-Backend-SDK header with User-Agent in BAPI requests and update it's value to contain both the package name and the package version of the clerk package (#2558) by @dimkl

    executing the request. Eg request from @clerk/nextjs to BAPI with append User-Agent: @clerk/nextjs@5.0.0-alpha-v5.16 using the latest version.

    Miscellaneous changes: The backend test build changed to use tsup.

Patch Changes

@clerk/shared@2.0.0-alpha-v5.10

Minor Changes

  • Allow dynamic values components props, even if these values change after the components are rendered. For example, a SignIn component with a redirectUrl prop passed in will always respect the latest value of redirectUrl. (#2515) by @nikosdouvlis

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

Patch Changes

  • Updated dependencies [8cc45d2af, db2d82901]:
    • @clerk/clerk-js@5.0.0-alpha-v5.16
    • @clerk/clerk-react@5.0.0-alpha-v5.16
    • @clerk/shared@2.0.0-alpha-v5.10

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

Patch Changes

  • Allow dynamic values components props, even if these values change after the components are rendered. For example, a SignIn component with a redirectUrl prop passed in will always respect the latest value of redirectUrl. (#2515) by @nikosdouvlis

  • Updated dependencies [8cc45d2af]:

    • @clerk/shared@2.0.0-alpha-v5.10

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

Patch Changes

  • Updated dependencies [8cc45d2af, db2d82901]:
    • @clerk/clerk-js@5.0.0-alpha-v5.16
    • @clerk/clerk-react@5.0.0-alpha-v5.16
    • @clerk/shared@2.0.0-alpha-v5.10

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

Patch Changes

@github-actions github-actions bot force-pushed the changeset-release/main branch 8 times, most recently from a1fb9b9 to 1654179 Compare January 11, 2024 16:10
@dimkl dimkl closed this Jan 11, 2024
@dimkl dimkl reopened this Jan 11, 2024
@dimkl dimkl enabled auto-merge January 11, 2024 17:00
@dimkl dimkl added this pull request to the merge queue Jan 11, 2024
Merged via the queue into main with commit cdc4f51 Jan 11, 2024
7 checks passed
@dimkl dimkl deleted the changeset-release/main branch January 11, 2024 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dimkl dimkl dimkl approved these changes

Assignees
No one assigned
Labels
backend chrome-extension clerk-js elements expo fastify gatsby nextjs react remix sdk-node
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@clerk-cookie @dimkl