-
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
Remove unused keystone-5 packages from this repo #5025
Comments
This was referenced Mar 7, 2021
Merged
This was referenced Mar 8, 2021
Merged
Merged
This was referenced Mar 8, 2021
Merged
This was referenced Mar 16, 2021
This was referenced Mar 24, 2021
Merged
With all the PRs above merged, I think we're good to close this issue. The remaining |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As outlined in #4962 (what's next for KeystoneJS)
Now that we have the keystone-5 repo ready to go, we can start cleaning up this codebase to prepare for our next round of changes in keystone-next.
The first step is to remove packages and code paths that aren't being used by the
@keystone-next
packages, for example:If you're watching this repo, it'll mean that you'll see us deleting a lot of the code that has been moved over to the new repo for maintenance and is now unreferenced by the new Keystone Next packages and website.
In this first pass we'll leave in place the packages and code paths that are currently referenced in the new packages.
Once that's complete, we'll start refactoring the remaining Keystone 5 code into the new packages, so we have a clean codebase to build on again.
The text was updated successfully, but these errors were encountered: