github keystonejs/keystone 2021-04-06
✨ 6th April 2021
on GitHub

latest releases: create-keystone-app@10.0.2, create-keystone-app@10.0.1, @keystone-6/core@6.3.0...
3 years ago

What's New

Controlled code demolition 🏗️ 👷‍♀️

We pruned a lot of code from the Keystone garden – cutting out the dead wood to make way for a more efficient and productive core in Keystone 6. Notable changes include:

  • Removed Keystone‘s DB adapters and the db.adapter config option (now that Keystone 6 uses Prisma under the hood).
  • Said goodbye to a bunch of redundant methods and arguments for the same reasons as above.
  • Exchanged deploy, reset and generate commands for keystone-next prisma e.g:
    • keystone-next deploy -> keystone-next prisma migrate deploy

Better pagination in Admin UI ⏭️ ✨

Pagination in the Admin UI has fresh styles and is easier to use.

Enjoying Keystone?

Star this repo 🌟 ☝️ or connect to Keystone on Twitter and in Slack.

View verbose release notes

Releases

@keystone-next/admin-ui@13.0.0

Major Changes

  • #5266 c28e765d1 Thanks @mitchellhamilton! - Updated Next API route template to use createSystem without the dotKeystonePath argument and import from the new Prisma Client location.

Minor Changes

Patch Changes

@keystone-next/fields@6.0.0

Major Changes

Patch Changes

@keystone-next/fields-document@4.0.0

Major Changes

Patch Changes

@keystone-next/keystone@15.0.0

Major Changes

  • #5266 c28e765d1 Thanks @mitchellhamilton! - Replaced deploy, reset and generate commands with keystone-next prisma. You can use these commands as replacements for the old commands:

    • keystone-next deploy -> keystone-next prisma migrate deploy
    • keystone-next reset -> keystone-next prisma migrate reset
    • keystone-next generate -> keystone-next prisma migrate dev

  • #5266 c28e765d1 Thanks @mitchellhamilton! - Removed migrationAction argument to createSystem and require that the PrismaClient is passed to createSystem to be able to connect to the database.

  • #5266 c28e765d1 Thanks @mitchellhamilton! - Updated keystone-next build command to validate that the GraphQL and Prisma schemas are up to date.

  • #5287 95fefaf81 Thanks @mitchellhamilton! - Removed getDbSchemaName and getPrismaPath database adapter options. To change the database schema that Keystone uses, you can add ?schema=whatever to the database url.

  • #5266 c28e765d1 Thanks @mitchellhamilton! - Moved generated schema.prisma to the root of the project directory. Note that this also moves the location of migrations from .keystone/prisma/migrations to migrations at the root of the project.

  • #5266 c28e765d1 Thanks @mitchellhamilton! - Removed dotKeystonePath argument from createSystem

  • #5256 399e6db39 Thanks @timleslie! - Removed support for the knex and mongoose database adapters. We now only support prisma_postgresql and prisma_sqlite.

  • #5285 5cd94b2a3 Thanks @mitchellhamilton! - Removed dropDatabase method and config option

  • #5266 c28e765d1 Thanks @mitchellhamilton! - Moved generated GraphQL schema to schema.graphql to the root of the project. We recommend that you commit this file to your repo.

Minor Changes

Patch Changes

@keystone-next/types@16.0.0

Major Changes

  • #5266 c28e765d1 Thanks @mitchellhamilton! - Removed migrationAction argument to createSystem and require that the PrismaClient is passed to createSystem to be able to connect to the database.

  • #5256 399e6db39 Thanks @timleslie! - Removed support for the knex and mongoose database adapters. We now only support prisma_postgresql and prisma_sqlite.

Minor Changes

  • #5368 b40016301 Thanks @timleslie! - The config option db.adapter is now deprecated. It has been repaced with db.provider which can take the values postgresql or sqlite.

  • #5283 192393d0d Thanks @timleslie! - The flag { experimental: { prismaSqlite: true } } is no longer required to use the SQLite adapter.

  • #5341 1886b4323 Thanks @mitchellhamilton! - Added generateNextGraphqlAPI and generateNodeAPI experimental options

@keystone-next/adapter-prisma-legacy@5.0.0

Major Changes

  • #5319 1261c398b Thanks @timleslie! - Removed legacy PrismaAdapter.listAdapterClass, PrismaAdapter.postConnect(), and PrismaAdapter.checkDatabaseVersion().

  • #5302 1e6d12f47 Thanks @mitchellhamilton! - Removed CLIOptionsForCreateMigration and createMigration exports

  • #5324 e702fea44 Thanks @timleslie! - Removed legacy .find(), .findAll(), .findOne(), .findById(), .itemsQueryMeta(), .getFieldAdapterByPath(), and .getPrimaryKeyAdapter() methods from PrismaListAdapter.

  • #5287 95fefaf81 Thanks @mitchellhamilton! - Removed getDbSchemaName and getPrismaPath database adapter options. To change the database schema that Keystone uses, you can add ?schema=whatever to the database url.

  • #5302 1e6d12f47 Thanks @mitchellhamilton! - Removed formatting of Prisma schema returned from _generatePrismaSchema method and made it return synchronously

  • #5320 fda82869c Thanks @timleslie! - Removed legacy default ID field support.

  • #5285 5cd94b2a3 Thanks @mitchellhamilton! - Removed dropDatabase method and config option

  • #5287 95fefaf81 Thanks @mitchellhamilton! - Removed migrationMode and all migration related methods on the adapter and instead require that a prisma client is passed to the adapter to be able to connect to the database

Patch Changes

@keystone-next/fields-legacy@25.0.0

Major Changes

Patch Changes

@keystone-next/fields-auto-increment-legacy@10.0.0

Major Changes

Patch Changes

@keystone-next/fields-cloudinary-image-legacy@5.0.0

Major Changes

Patch Changes

@keystone-next/keystone-legacy@23.0.0

Major Changes

Patch Changes

  • #5324 e702fea44 Thanks @timleslie! - Removed legacy .find(), .findAll(), .findOne(), .findById(), .itemsQueryMeta(), .getFieldAdapterByPath(), and .getPrimaryKeyAdapter() methods from PrismaListAdapter.

@keystone-next/test-utils-legacy@16.0.0

Major Changes

  • #5276 1a4db6c87 Thanks @mitchellhamilton! - Removed usage of getDbSchemaName, getPrismaPath, migrationMode and dropDatabase adapter options. Note this means that dropping the database and running migrations will now only happen when creating a keystone instance from setupFromConfig rather than on every keystone.connect

  • #5256 399e6db39 Thanks @timleslie! - Removed support for the knex and mongoose database adapters. We now only support prisma_postgresql and prisma_sqlite.

Patch Changes

@keystone-ui/fields@2.1.0

Minor Changes

  • #5322 d93bab17b Thanks @gwyneplaine! - Added styles prop to @keystone-ui/fields select components to enable style customisations to propagate to the underlying reaect-select implementation.

@keystone-next/admin-ui-utils@3.0.3

Patch Changes

@keystone-next/auth@20.0.0

Patch Changes

@keystone-next/cloudinary@3.0.6

Patch Changes

@keystone-next/server-side-graphql-client-legacy@3.0.1

Patch Changes

@keystone-next/website@1.3.0

Minor Changes

  • #5368 b40016301 Thanks @timleslie! - The config option db.adapter is now deprecated. It has been repaced with db.provider which can take the values postgresql or sqlite.

Patch Changes

@keystone-next/example-auth@2.0.1

Patch Changes

@keystone-next/app-basic@2.0.1

Patch Changes

@keystone-next/example-ecommerce@2.0.1

Patch Changes

keystone-next-app@0.0.5

Patch Changes

@keystone-next/example-next-lite@1.0.4

Patch Changes

@keystone-next/example-roles@2.0.1

Patch Changes

@keystone-next/example-sandbox@1.0.5

Patch Changes

@keystone-next/example-todo@1.0.5

Patch Changes

@keystone-next/api-tests-legacy@9.2.2

Patch Changes

@keystone-next/benchmarks-legacy@5.2.5

Patch Changes

Check out latest releases or
releases around keystonejs/keystone 2021-04-06

Don't miss a new keystone release

NewReleases is sending notifications on new releases.

Get notifications