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/node@2.5.0
Minor Changes
957a1c9: Add organizationId to getContext function.
This will allow the users to get access token with "organization_id" claim, which supports organization API resources.
Patch Changes
Updated dependencies [bc3e8da]
@logto/client@2.6.7
@logto/browser@2.2.11
Patch Changes
Updated dependencies [bc3e8da]
@logto/client@2.6.7
@logto/capacitor@1.1.10
Patch Changes
@logto/browser@2.2.11
@logto/chrome-extension@0.1.5
Patch Changes
@logto/browser@2.2.11
@logto/client@2.6.7
Patch Changes
bc3e8da: Fix the bug of granting mutiple organization tokens concurrently.
This is a bug fix for the issue that the client is not able to grant multiple organization tokens concurrently. The issue is caused by the memoize function that caches the organization token request, which leads to the token request being memoized by incorrect key and not being able to be granted concurrently. This fix updates the memoize function to cache by the correct key.
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/node@2.5.0
Minor Changes
957a1c9: Add
organizationIdtogetContextfunction.This will allow the users to get access token with "organization_id" claim, which supports organization API resources.
Patch Changes
@logto/browser@2.2.11
Patch Changes
@logto/capacitor@1.1.10
Patch Changes
@logto/chrome-extension@0.1.5
Patch Changes
@logto/client@2.6.7
Patch Changes
bc3e8da: Fix the bug of granting mutiple organization tokens concurrently.
This is a bug fix for the issue that the client is not able to grant multiple organization tokens concurrently. The issue is caused by the memoize function that caches the organization token request, which leads to the token request being memoized by incorrect key and not being able to be granted concurrently. This fix updates the memoize function to cache by the correct key.
@logto/express@2.3.9
Patch Changes
@logto/next@3.2.6
Patch Changes
@logto/nuxt@0.1.11
Patch Changes
@logto/react@3.0.9
Patch Changes
@logto/remix@2.1.9
Patch Changes
@logto/sveltekit@0.2.9
Patch Changes
@logto/vue@2.2.10
Patch Changes
@logto/browser-sample@2.0.11
Patch Changes
@logto/express-sample@2.0.9
Patch Changes
@logto/next-app-dir-sample@2.1.10
Patch Changes
@logto/next-sample@2.1.10
Patch Changes
@logto/next-server-actions-sample@2.1.15
Patch Changes
@logto/react-sample@2.1.10
Patch Changes
@logto/vue-sample@2.1.9
Patch Changes