Skip to content

release: version packages - #1180

Open
silverhand-bot wants to merge 1 commit into
masterfrom
changeset-release/master
Open

release: version packages#1180
silverhand-bot wants to merge 1 commit into
masterfrom
changeset-release/master

Conversation

@silverhand-bot

@silverhand-bot silverhand-bot commented Sep 9, 2026 •
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 master, this PR will be updated.

Releases

@logto/express@4.0.0

Major Changes

  • db78ef4: require Node.js 22 or later for server-side SDKs

Minor Changes

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a078735]
  • Updated dependencies [db78ef4]
  • Updated dependencies [3b32030]
  • Updated dependencies [a9dca71]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/node@4.0.0

@logto/next@5.0.0

Major Changes

  • db78ef4: require Node.js 22 or later for server-side SDKs

Minor Changes

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

  • a9dca71: expose token claim APIs across platform SDKs

    Make getIdTokenClaims, getAccessTokenClaims, and getOrganizationTokenClaims available through
    Next.js and React Router. Forward the optional organizationId through platform access-token
    wrappers.

  • 1cfbfd2: expose token clearing APIs in Next.js and React Router

    Add clearAccessToken and clearAllTokens to Next.js server APIs and the React Router request
    context. Persist the resulting session changes through each framework's cookie response mechanism.

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a078735]
  • Updated dependencies [db78ef4]
  • Updated dependencies [3b32030]
  • Updated dependencies [a9dca71]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/node@4.0.0

@logto/node@4.0.0

Major Changes

  • db78ef4: require Node.js 22 or later for server-side SDKs

Minor Changes

  • b694c0e: support configurable request timeouts in Node.js and edge runtimes

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

  • a9dca71: expose token claim APIs across platform SDKs

    Make getIdTokenClaims, getAccessTokenClaims, and getOrganizationTokenClaims available through
    Next.js and React Router. Forward the optional organizationId through platform access-token
    wrappers.

  • 1b9abbd: stabilize cache configuration across JavaScript SDKs

    Use the stable cache client adapter property. The deprecated unstable_cache alias remains
    supported, with the stable property taking precedence. Node and edge clients continue to use an
    endpoint-scoped process-local cache by default.

    Browser, React, Angular, Vue, Capacitor, and Chrome Extension clients can opt in through the stable
    enableCache option. Browser caches are isolated by endpoint and application, and cache storage
    failures no longer discard successful discovery responses.

Patch Changes

  • a078735: remove stale node-fetch documentation and declarations

  • 3b32030: export FirstScreen and update the React Router type surface

    React Router users should replace InteractionMode imports with FirstScreen. The client and Node
    SDKs retain InteractionMode for compatibility.

  • 9f877b2: clear local authentication state when remote sign-out cannot start

  • Updated dependencies [a078735]

  • Updated dependencies [3b32030]

  • Updated dependencies [a9dca71]

  • Updated dependencies [1b9abbd]

  • Updated dependencies [b694c0e]

  • Updated dependencies [9f877b2]

    • @logto/client@3.2.0

@logto/nuxt@2.0.0

Major Changes

  • db78ef4: require Node.js 22 or later for server-side SDKs

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a078735]
  • Updated dependencies [db78ef4]
  • Updated dependencies [3b32030]
  • Updated dependencies [a9dca71]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/node@4.0.0

@logto/react-router@2.0.0

Major Changes

  • db78ef4: require Node.js 22 or later for server-side SDKs

  • 3b32030: export FirstScreen and update the React Router type surface

    React Router users should replace InteractionMode imports with FirstScreen. The client and Node
    SDKs retain InteractionMode for compatibility.

  • 6a98d63: replace legacy React Router handlers with a Framework Mode middleware API

    Create the integration with createLogtoReactRouter(), register logto.middleware, and mount
    authentication routes with logto.authRoutes(). Export its callback loader and mutation action;
    sign-in, sign-up, and sign-out now require POST. Read authentication from logto.context; explicit
    token methods now persist refreshed sessions safely.

    The new API supports React Router 7.15 and React Router 8.

Minor Changes

  • f335935: support request-specific post-callback redirects

    Pass a resolver as postCallbackRedirectUri to derive a same-origin path from the sign-in or
    sign-up request. The resolved path is stored in the sign-in session and used after callback
    exchange. Callbacks without a stored destination fall back to the application root.

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

  • a9dca71: expose token claim APIs across platform SDKs

    Make getIdTokenClaims, getAccessTokenClaims, and getOrganizationTokenClaims available through
    Next.js and React Router. Forward the optional organizationId through platform access-token
    wrappers.

  • 1cfbfd2: expose token clearing APIs in Next.js and React Router

    Add clearAccessToken and clearAllTokens to Next.js server APIs and the React Router request
    context. Persist the resulting session changes through each framework's cookie response mechanism.

Patch Changes

  • e5f3817: keep coordination request-local until a new persistent session reaches the browser
  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a078735]
  • Updated dependencies [db78ef4]
  • Updated dependencies [3b32030]
  • Updated dependencies [a9dca71]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/node@4.0.0

@logto/remix@4.0.0

Major Changes

  • db78ef4: require Node.js 22 or later for server-side SDKs

Minor Changes

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a078735]
  • Updated dependencies [db78ef4]
  • Updated dependencies [3b32030]
  • Updated dependencies [a9dca71]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/node@4.0.0

@logto/sveltekit@1.0.0

Major Changes

  • db78ef4: require Node.js 22 or later for server-side SDKs

Minor Changes

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a078735]
  • Updated dependencies [db78ef4]
  • Updated dependencies [3b32030]
  • Updated dependencies [a9dca71]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/node@4.0.0

@logto/angular@2.1.0

Minor Changes

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

  • a9dca71: expose token claim APIs across platform SDKs

    Make getIdTokenClaims, getAccessTokenClaims, and getOrganizationTokenClaims available through
    Next.js and React Router. Forward the optional organizationId through platform access-token
    wrappers.

  • 1b9abbd: stabilize cache configuration across JavaScript SDKs

    Use the stable cache client adapter property. The deprecated unstable_cache alias remains
    supported, with the stable property taking precedence. Node and edge clients continue to use an
    endpoint-scoped process-local cache by default.

    Browser, React, Angular, Vue, Capacitor, and Chrome Extension clients can opt in through the stable
    enableCache option. Browser caches are isolated by endpoint and application, and cache storage
    failures no longer discard successful discovery responses.

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/browser@3.1.0

@logto/browser@3.1.0

Minor Changes

  • b694c0e: support configurable request timeouts through native fetch

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

  • 1b9abbd: stabilize cache configuration across JavaScript SDKs

    Use the stable cache client adapter property. The deprecated unstable_cache alias remains
    supported, with the stable property taking precedence. Node and edge clients continue to use an
    endpoint-scoped process-local cache by default.

    Browser, React, Angular, Vue, Capacitor, and Chrome Extension clients can opt in through the stable
    enableCache option. Browser caches are isolated by endpoint and application, and cache storage
    failures no longer discard successful discovery responses.

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [a078735]
  • Updated dependencies [3b32030]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [b694c0e]
  • Updated dependencies [9f877b2]
    • @logto/client@3.2.0

@logto/capacitor@4.1.0

Minor Changes

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

  • 1b9abbd: stabilize cache configuration across JavaScript SDKs

    Use the stable cache client adapter property. The deprecated unstable_cache alias remains
    supported, with the stable property taking precedence. Node and edge clients continue to use an
    endpoint-scoped process-local cache by default.

    Browser, React, Angular, Vue, Capacitor, and Chrome Extension clients can opt in through the stable
    enableCache option. Browser caches are isolated by endpoint and application, and cache storage
    failures no longer discard successful discovery responses.

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/browser@3.1.0

@logto/chrome-extension@0.2.0

Minor Changes

  • b694c0e: support configurable request timeouts through native fetch

  • 1b9abbd: stabilize cache configuration across JavaScript SDKs

    Use the stable cache client adapter property. The deprecated unstable_cache alias remains
    supported, with the stable property taking precedence. Node and edge clients continue to use an
    endpoint-scoped process-local cache by default.

    Browser, React, Angular, Vue, Capacitor, and Chrome Extension clients can opt in through the stable
    enableCache option. Browser caches are isolated by endpoint and application, and cache storage
    failures no longer discard successful discovery responses.

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/browser@3.1.0

@logto/client@3.2.0

Minor Changes

  • a9dca71: expose token claim APIs across platform SDKs

    Make getIdTokenClaims, getAccessTokenClaims, and getOrganizationTokenClaims available through
    Next.js and React Router. Forward the optional organizationId through platform access-token
    wrappers.

  • 1b9abbd: stabilize cache configuration across JavaScript SDKs

    Use the stable cache client adapter property. The deprecated unstable_cache alias remains
    supported, with the stable property taking precedence. Node and edge clients continue to use an
    endpoint-scoped process-local cache by default.

    Browser, React, Angular, Vue, Capacitor, and Chrome Extension clients can opt in through the stable
    enableCache option. Browser caches are isolated by endpoint and application, and cache storage
    failures no longer discard successful discovery responses.

  • b694c0e: support configurable request timeouts and optional fetch adapters

    Set requestTimeoutMs in LogtoConfig to apply a timeout to Logto discovery, token, revocation,
    user-info, and remote JSON Web Key Set requests. Existing request abort signals are preserved.

    ClientAdapter uses native fetch by default and accepts an optional custom fetch transport so
    the client can consistently apply shared request policies. Existing requester adapters remain
    supported but are deprecated. When both are provided, fetch takes precedence.

Patch Changes

  • a078735: simplify error response parsing while preserving the original response for callers

  • 3b32030: export FirstScreen and update the React Router type surface

    React Router users should replace InteractionMode imports with FirstScreen. The client and Node
    SDKs retain InteractionMode for compatibility.

  • 9f877b2: clear local authentication state when remote sign-out cannot start

@logto/react@4.1.0

Minor Changes

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

  • 1b9abbd: stabilize cache configuration across JavaScript SDKs

    Use the stable cache client adapter property. The deprecated unstable_cache alias remains
    supported, with the stable property taking precedence. Node and edge clients continue to use an
    endpoint-scoped process-local cache by default.

    Browser, React, Angular, Vue, Capacitor, and Chrome Extension clients can opt in through the stable
    enableCache option. Browser caches are isolated by endpoint and application, and cache storage
    failures no longer discard successful discovery responses.

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/browser@3.1.0

@logto/vue@3.1.0

Minor Changes

  • a9dca71: export decodeAccessToken, ReservedResource, and CacheKey from applicable platform SDK package
    roots

  • 1b9abbd: stabilize cache configuration across JavaScript SDKs

    Use the stable cache client adapter property. The deprecated unstable_cache alias remains
    supported, with the stable property taking precedence. Node and edge clients continue to use an
    endpoint-scoped process-local cache by default.

    Browser, React, Angular, Vue, Capacitor, and Chrome Extension clients can opt in through the stable
    enableCache option. Browser caches are isolated by endpoint and application, and cache storage
    failures no longer discard successful discovery responses.

Patch Changes

  • 9f877b2: clear local authentication state when remote sign-out cannot start
  • Updated dependencies [b694c0e]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/browser@3.1.0

@logto/browser-sample@2.0.35

Patch Changes

  • Updated dependencies [b694c0e]
  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/browser@3.1.0

@logto/capacitor-sample@0.1.6

Patch Changes

  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/capacitor@4.1.0

@logto/express-sample@2.0.36

Patch Changes

  • Updated dependencies [db78ef4]
  • Updated dependencies [a9dca71]
  • Updated dependencies [9f877b2]
    • @logto/express@4.0.0

@logto/react-router-sample@1.0.7

Patch Changes

@logto/react-sample@2.1.35

Patch Changes

  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/react@4.1.0

@logto/vue-sample@2.1.33

Patch Changes

  • Updated dependencies [a9dca71]
  • Updated dependencies [1b9abbd]
  • Updated dependencies [9f877b2]
    • @logto/vue@3.1.0

@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch 7 times, most recently from f988b0a to 1037ff5 Compare September 11, 2026 06:34
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 1037ff5 to 9302724 Compare September 11, 2026 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@charIeszhao charIeszhao Awaiting requested review from charIeszhao charIeszhao is a code owner
@wangsijie wangsijie Awaiting requested review from wangsijie wangsijie is a code owner
@gao-sun gao-sun Awaiting requested review from gao-sun gao-sun is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@silverhand-bot