-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Move packages-next to packages #6087
Conversation
🦋 Changeset detectedLatest commit: 0333f13 The changes in this PR will be included in the next version bump. This PR includes changesets to release 15 packages
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 |
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/FR35cQxBUREVrebPLCRjXaebtzHo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requires a changeset
What were you expecting this to include? |
Co-authored-by: Tim Leslie <timl@thinkmill.com.au>
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
* Move packages-next to packages * Add changeset
Been meaning to do this since we got rid of the last legacy packages and removed the original
packages
directory.This moves
packages-next
topackages
and updates all the references.I also found a few things we missed (old config in
package.json
etc) for things that have been removed, and cleaned it up.