Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove BaseKeystone dependency from auth schema extension #5827

Merged
merged 1 commit into from
May 31, 2021

Conversation

timleslie
Copy link
Contributor

This sets us up for the breaking change of removing keystone from the ExtendGraphqlSchema type.

@vercel
Copy link

vercel bot commented May 31, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/BYsSVUeVpqGGpRAq4ZfPFrs1sMDf
✅ Preview: https://keystone-next-docs-git-no-keystone-init-first-item-keystonejs.vercel.app

@changeset-bot
Copy link

changeset-bot bot commented May 31, 2021

🦋 Changeset detected

Latest commit: 81d178a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@keystone-next/auth Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@codesandbox-ci
Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@timleslie timleslie requested a review from a team May 31, 2021 00:44
@timleslie timleslie enabled auto-merge (squash) May 31, 2021 00:51
@timleslie timleslie merged commit a0ef39c into master May 31, 2021
@timleslie timleslie deleted the no-keystone-init-first-item branch May 31, 2021 01:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants