chore: version packages - #89
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-templates@0.14.0
Minor Changes
724a6cb: Move the API starters onto the adapters that forward the browser's user agent.
@seamless-auth/expressgoes from 0.14.0 to 0.15.0 and@seamless-auth/fastifyfrom 0.5.0 to0.6.0. Both now send the browser's
User-Agentto the auth API asx-seamless-client-user-agenton every proxied call, beside the client address they alreadyforward.
The auth API records a device class on every audit row from that header and reports sign-in
outcomes by it (
GET /internal/metrics/sign-ins,seamless-auth-api0.13.0). The adapter is theonly client the API sees, so a project on the older adapters has every row recorded as the
adapter's own user agent and the breakdown by device reads
unknownfor every sign-in. Theadapters also pass the new metrics route through, which the admin console's Overview reads.
The starters needed the version and nothing else.
createSeamlessAuthServer,requireAuth,requireRoleandSeamlessAuthUserare unchanged, and nothing here forwards anything a browserdid not already send. The React starters stay on
@seamless-auth/react0.12.0; the token theAPI mints gained a claim the client never reads.