Skip to content

feat: Upgrade authkit-js to v0.20.0#90

Merged
cmatheson merged 1 commit intomainfrom
upgrade-authkit-js
Mar 25, 2026
Merged

feat: Upgrade authkit-js to v0.20.0#90
cmatheson merged 1 commit intomainfrom
upgrade-authkit-js

Conversation

@cmatheson
Copy link
Copy Markdown
Collaborator

@cmatheson cmatheson commented Mar 25, 2026

This version supports multiple applications/environments

@greptile-apps
Copy link
Copy Markdown

greptile-apps bot commented Mar 25, 2026

Greptile Summary

This PR bumps the @workos-inc/authkit-js peer dependency from 0.19.0 to 0.20.0, which adds support for multiple applications/environments. The change is minimal and consistent with the existing exact-pin versioning policy.

Key points to verify:

  • If v0.20.0 introduced new configuration options (e.g., applicationId, environmentId) to enable the multi-app feature, those options would need to be explicitly destructured and forwarded to createClient in provider.tsx, as well as added to the useEffect dependency array. The current provider pattern silently drops any unrecognized props.
  • If the multi-environment support is transparently handled server-side with no new client configuration, the version bump alone is sufficient and the PR is safe to merge as-is.

Confidence Score: 4/5

  • Safe to merge if the new multi-environment feature requires no additional client-side configuration options.
  • This is a one-line version bump with no structural code changes. The main uncertainty is whether v0.20.0 introduced new createClient options that the React provider needs to explicitly forward — if it does, those props would be silently dropped today. Confirming with the authkit-js changelog would resolve that concern.
  • src/provider.tsx — verify that all new options from v0.20.0 are destructured and passed through to createClient.

Important Files Changed

Filename Overview
package.json Bumps @workos-inc/authkit-js from 0.19.0 to 0.20.0 (exact pin, consistent with existing policy). No lock file is maintained in this repo. If the new version introduced new client options to support multiple applications/environments, those options may need to be explicitly wired through provider.tsx.

Sequence Diagram

sequenceDiagram
    participant App as React App
    participant Provider as AuthKitProvider
    participant JS as authkit-js (v0.20.0)
    participant WOS as WorkOS API

    App->>Provider: render with props (clientId, options...)
    Provider->>JS: createClient(clientId, { apiHostname, port, https, redirectUri, devMode, ... })
    JS->>WOS: initialize session / fetch tokens
    WOS-->>JS: access token + user claims
    JS-->>Provider: onRefresh(response)
    Provider->>Provider: setState (user, roles, permissions...)
    Provider-->>App: Context value updated
Loading

Reviews (1): Last reviewed commit: "feat: Upgrade authkit-js to v0.20.0" | Re-trigger Greptile

This version supports multiple applications/environments
@cmatheson cmatheson force-pushed the upgrade-authkit-js branch from 3918faf to 2c84c75 Compare March 25, 2026 14:48
@cmatheson cmatheson merged commit 10f0216 into main Mar 25, 2026
4 checks passed
@cmatheson cmatheson deleted the upgrade-authkit-js branch March 25, 2026 14:49
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