[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.0

Minor Changes

• 782583c: In bearer transport, a request that carries a token no longer follows a redirect to an origin outside apiHost and trustedOrigins. The client asks fetch for redirect: 'manual', follows a redirect to a trusted origin itself (up to five hops, turning a 303, or a 301 or 302 after a POST, into a GET as fetch does), and rejects any other with the new UntrustedRedirectError without sending the token on. Where the platform follows redirects regardless, as React Native's fetch does, a response that ended on another origin is rejected instead. A caller that sets redirect itself keeps that choice, and the final-origin check still applies. Requests without a token, and cookie transport, are unchanged.

Patch Changes

• e3cf1f9: authorizedFetch works again for an app that serves /auth on its own origin (apiHost: "", as <AuthProvider apiHost="">). Since 0.5.0 it refused every path in that setup with UntrustedOriginError, because a path stayed relative and the origin check could not read an origin from it. A path now resolves on the page's own origin, which is trusted. Without a page (server rendering, React Native) an empty apiHost still sends nothing.

@seamless-auth/angular@0.3.1

Patch Changes

• Updated dependencies [782583c]
• Updated dependencies [e3cf1f9]
  • @seamless-auth/client@0.7.0

@seamless-auth/react@0.17.1

Patch Changes

• 782583c: In bearer transport, a request that carries a token no longer follows a redirect to an origin outside apiHost and trustedOrigins. The client asks fetch for redirect: 'manual', follows a redirect to a trusted origin itself (up to five hops, turning a 303, or a 301 or 302 after a POST, into a GET as fetch does), and rejects any other with the new UntrustedRedirectError without sending the token on. Where the platform follows redirects regardless, as React Native's fetch does, a response that ended on another origin is rejected instead. A caller that sets redirect itself keeps that choice, and the final-origin check still applies. Requests without a token, and cookie transport, are unchanged.
• Updated dependencies [782583c]
• Updated dependencies [e3cf1f9]
  • @seamless-auth/client@0.7.0

@seamless-auth/react-native@0.3.2

Patch Changes

• 782583c: In bearer transport, a request that carries a token no longer follows a redirect to an origin outside apiHost and trustedOrigins. The client asks fetch for redirect: 'manual', follows a redirect to a trusted origin itself (up to five hops, turning a 303, or a 301 or 302 after a POST, into a GET as fetch does), and rejects any other with the new UntrustedRedirectError without sending the token on. Where the platform follows redirects regardless, as React Native's fetch does, a response that ended on another origin is rejected instead. A caller that sets redirect itself keeps that choice, and the final-origin check still applies. Requests without a token, and cookie transport, are unchanged.
• Updated dependencies [782583c]
• Updated dependencies [e3cf1f9]
  • @seamless-auth/client@0.7.0

@seamless-auth/svelte@0.2.1

Patch Changes

• Updated dependencies [782583c]
• Updated dependencies [e3cf1f9]
  • @seamless-auth/client@0.7.0

@seamless-auth/vue@0.2.1

Patch Changes

• Updated dependencies [782583c]
• Updated dependencies [e3cf1f9]
  • @seamless-auth/client@0.7.0