Repository navigation
fix(manifest): sync the bundled manifest with the auth API routes for permissions - #276
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.
Syncs the bundled adapter manifest with the auth API's
main, which gained the permission and organization role routes in fells-code/seamless-auth-api#576 and #577. Themanifestcheck onmainhas been failing since those merged.This is the fallback copy for when fetching the live manifest fails at startup. It is also what a standalone console behind this adapter saw, which showed "needs API v0.23" on a v0.23 API.
scripts/check-adapter-manifest.mjs, the core build and the core tests pass locally. Not in this PR: the Next.js conformance opt-in, which waits for the next CLI release.