Making the move to Keystone 6

By The Keystone Team, Published on Thu Jan 06 2022

In 2021 Thinkmill’s Keystone team focused on achieving a General Availability release for Keystone 6. The new Keystone is faster and more flexible than ever, and now is a great time to look at making the move from 5 to 6.

Setting a new foundation

There’s so many great changes in the new Keystone. With a TypeScript native DX, Prisma under the hood, and Next.js powering the Admin UI, we’re really excited by the foundations we’ve put in place.

Read the full announcement, and check out our roadmap to understand where we’re taking Keystone in 2022.

Making the change to Keystone 6

With Keystone 5 in maintenance mode, migrating your project to Keystone 6 is a great way to take advantage of the new DX.

V6 offers a lot of features and DX improvements that weren’t possible in V5. However, better DX does come with a few limitations that V5 was not inhibited by.

Given how much has changed between the two versions, and the diversity of use cases that are in use in V5, there’s no single upgrade guide we can provide that will solve your needs.

Help us help you

We’ve set up a new discussion category in the Keystone 5 repo and will be seeding it with:

• Info on some of the key differences between 5 and 6
• Answers to some questions we think many of you will have

We also want to help in a way that’s most useful for you. After you've taken a look at the new Keystone docs, and read the existing answers, let us know:

• Where are you getting stuck in migrating from your use case?
• What other differences between V5 and V6 are hardest to grok?

To get help: just create a new discussion topic with info about your K5 version, and any other relevant details from your use case (deployment, DB lang, schema, etc) that we’ll need to know in order to help you.

Thanks for being part of the Keystone 5 journey, and we’re looking forward to having you on Keystone 6.