Repository navigation
chore: version packages - #153
Merged
Merged
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.22.0
Minor Changes
566d7b2: Show permission guards in the starters. Every API starter, and the Next.js starter, serves
GET /reports(/api/reportsin Next.js) behind its adapter's permission guard forreports:read, beside the existingbetaUserrole route. The React starters show the reports on the Session page withusePermissions().hasPermission, and the Angular, Vue, SvelteKit and Expo starters gate their reports UI withhasPermission; the server guard is what enforces. Each README and AGENTS.md has the steps to add a dedicatedreportViewerrole, create the permission and grant it to that role.Permissions need Seamless Auth API v0.23 or later. On v0.22 access tokens carry no permissions, so the guarded route answers 403 to everyone and the UI stays hidden.
The starters move to the adapters and SDKs that carry the guard:
@seamless-auth/express0.25,@seamless-auth/fastify0.16,@seamless-auth/nextjs0.9,@seamless-auth/react0.20,@seamless-auth/angular0.5,@seamless-auth/vue0.4,@seamless-auth/svelte0.4,@seamless-auth/react-native0.5, andseamless-auth0.6 for Go, Rust and Python. With the Python 0.6 adapter, FastAPI guard refusals answer{"error": "<code>"}instead of{"detail": "<code>"}.