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.

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

release: version packages #775

Merged
merged 1 commit into from
Jul 24, 2024
Merged

release: version packages #775

merged 1 commit into from
Jul 24, 2024

Conversation

silverhand-bot
Copy link
Collaborator

@silverhand-bot silverhand-bot commented Jul 24, 2024

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 master, this PR will be updated.

Releases

@logto/next@3.4.0

Minor Changes

  • a40b28f: add getAccessToken to the server actions package

    Previously, in order to get access tokens (and organization tokens) in App Router, you'll use getLogtoContext with config { getAccessToken: true }, this won't cache the token and will make a network request every time you call it. That is because Next.js does not allow to write cookies in the server side: HTTP does not allow setting cookies after streaming starts, so you must use .set() in a Server Action or Route Handler.

    This change adds a new function getAccessToken for you to get the access token in a server action or a route handler. It will cache the token and only make a network request when the token is expired.

    And also, this change adds a new function getOrganizationToken for you to get the organization token.

    The original method is deprecated and will be removed in the future.

  • ff8bcbb: support custom error handler for all methods in pages router

@logto/nuxt@0.3.3

Patch Changes

  • ea4555f: use warning to replace the error of empty configuration

@logto/next-server-actions-sample@2.2.0

Minor Changes

  • a40b28f: add getAccessToken to the server actions package

    Previously, in order to get access tokens (and organization tokens) in App Router, you'll use getLogtoContext with config { getAccessToken: true }, this won't cache the token and will make a network request every time you call it. That is because Next.js does not allow to write cookies in the server side: HTTP does not allow setting cookies after streaming starts, so you must use .set() in a Server Action or Route Handler.

    This change adds a new function getAccessToken for you to get the access token in a server action or a route handler. It will cache the token and only make a network request when the token is expired.

    And also, this change adds a new function getOrganizationToken for you to get the organization token.

    The original method is deprecated and will be removed in the future.

Patch Changes

  • Updated dependencies [a40b28f]
  • Updated dependencies [ff8bcbb]
    • @logto/next@3.4.0

@logto/next-app-dir-sample@2.1.17

Patch Changes

  • Updated dependencies [a40b28f]
  • Updated dependencies [ff8bcbb]
    • @logto/next@3.4.0

@logto/next-sample@2.1.17

Patch Changes

  • Updated dependencies [a40b28f]
  • Updated dependencies [ff8bcbb]
    • @logto/next@3.4.0

@wangsijie wangsijie merged commit 7c65c7b into master Jul 24, 2024
20 checks passed
@wangsijie wangsijie deleted the changeset-release/master branch July 24, 2024 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants