[github-actions]

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.

Releases

@seamless-auth/client@0.7.1

Patch Changes

• f21867d: OAuth sign-in now carries the state binding the auth server returns from POST /oauth/:providerId/start back to the callback. The session actions startOAuthLogin and finishOAuthLogin (and so useAuth() in React and React Native, and the Angular, Vue and Svelte bindings) store the binding with its state, attach it to the matching callback, and clear it afterwards, so apps that call these actions directly need no code change. The binding is kept in sessionStorage under seamless:oauth:binding in a browser and in memory elsewhere, and is never sent to the provider or put in a URL. startOAuthSignIn passes it explicitly when an in-app browser hands the callback back, and now refuses a callback whose state is not the one it started.

  StartOAuthLoginResult gains an optional binding and FinishOAuthLoginInput an optional binding. Older auth servers return no binding and are unaffected. Auth API 0.19.x with fix(oauth): bind the OAuth state to the client that started sign-in seamless-auth-api#463 refuses a callback without the binding, so upgrade this SDK before or with that API release.

@seamless-auth/react@0.18.1

Patch Changes

• 15ed347: The SMS terms modal now lists support@fellscode.com as the opt-out and support contact.

• f21867d: OAuth sign-in now carries the state binding the auth server returns from POST /oauth/:providerId/start back to the callback. The session actions startOAuthLogin and finishOAuthLogin (and so useAuth() in React and React Native, and the Angular, Vue and Svelte bindings) store the binding with its state, attach it to the matching callback, and clear it afterwards, so apps that call these actions directly need no code change. The binding is kept in sessionStorage under seamless:oauth:binding in a browser and in memory elsewhere, and is never sent to the provider or put in a URL. startOAuthSignIn passes it explicitly when an in-app browser hands the callback back, and now refuses a callback whose state is not the one it started.

  StartOAuthLoginResult gains an optional binding and FinishOAuthLoginInput an optional binding. Older auth servers return no binding and are unaffected. Auth API 0.19.x with fix(oauth): bind the OAuth state to the client that started sign-in seamless-auth-api#463 refuses a callback without the binding, so upgrade this SDK before or with that API release.

• Updated dependencies [f21867d]

  • @seamless-auth/client@0.7.1

@seamless-auth/react-native@0.3.3

Patch Changes

• f21867d: OAuth sign-in now carries the state binding the auth server returns from POST /oauth/:providerId/start back to the callback. The session actions startOAuthLogin and finishOAuthLogin (and so useAuth() in React and React Native, and the Angular, Vue and Svelte bindings) store the binding with its state, attach it to the matching callback, and clear it afterwards, so apps that call these actions directly need no code change. The binding is kept in sessionStorage under seamless:oauth:binding in a browser and in memory elsewhere, and is never sent to the provider or put in a URL. startOAuthSignIn passes it explicitly when an in-app browser hands the callback back, and now refuses a callback whose state is not the one it started.

  StartOAuthLoginResult gains an optional binding and FinishOAuthLoginInput an optional binding. Older auth servers return no binding and are unaffected. Auth API 0.19.x with fix(oauth): bind the OAuth state to the client that started sign-in seamless-auth-api#463 refuses a callback without the binding, so upgrade this SDK before or with that API release.

• Updated dependencies [f21867d]

  • @seamless-auth/client@0.7.1