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

Version Packages #5086

Merged
merged 1 commit into from
Mar 21, 2021
Merged

Version Packages #5086

merged 1 commit into from
Mar 21, 2021

Conversation

keystonejs-release-bot
Copy link
Collaborator

@keystonejs-release-bot keystonejs-release-bot commented Mar 10, 2021

What's New

Prisma migrations 🚚

  • We updated keystone-next dev with the Prisma adapter so that it interactively prompts for creating and applying migrations.
  • createKeystone and createSystem also accept a migration mode now instead of a script.
  • keystone-next generate now uses Prisma's programmatic APIs to generate migrations and it accepts the following options as command line arguments or as prompts:
    • --name to set the name of the migration
    • --accept-data-loss to allow resetting the database when it is out of sync with the migrations
    • --allow-empty to create an empty migration when there are no changes to the schema.

Noteworthy bug-squashing 🐛

Now you can include negative values for float, decimal and integer fields. 🎉

Enjoying Keystone?

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


Releases

@keystone-next/admin-ui@12.0.0

Major Changes

Patch Changes

@keystone-next/keystone@13.0.0

Major Changes

  • #5087 56e5fe10b Thanks @mitchellhamilton! - Updated createKeystone and createSystem to accept a migration mode rather than script

  • #5135 cdd889db1 Thanks @mitchellhamilton! - Updated keystone-next dev with the Prisma adapter so that it interactively prompts for creating and applying a migration

  • #5163 b37cbffc8 Thanks @mitchellhamilton! - Added db.useMigrations option to replace using keystone-next dev and keystone-next prototype depending on what kind of migration strategy you want to use. If you were previously using keystone-next dev, you should set db.useMigrations to true in your config and continue using keystone-next dev. If you were previously using keystone-next prototype, you should now use keystone-next dev.

  • #5155 215aed387 Thanks @mitchellhamilton! - Removed createOnly migration mode

  • #5163 b37cbffc8 Thanks @mitchellhamilton! - Replaced MigrationMode type with MigrationAction that createSystem and createKeystone now accept.

Minor Changes

  • #3946 8e9b04ecd Thanks @timleslie! - Added experimental support for Prisma + SQLite as a database adapter.

  • #5102 714bdadce Thanks @mitchellhamilton! - Added none-skip-client-generation migrationMode

  • #5148 e6b16d4e9 Thanks @mitchellhamilton! - Updated keystone-next deploy to use Prisma's programmatic APIs to apply migrations

  • #5155 215aed387 Thanks @mitchellhamilton! - Changed keystone-next generate so that it uses Prisma's programmatic APIs to generate migrations and it accepts the following options as command line arguments or as prompts:

    • --name to set the name of the migration
    • --accept-data-loss to allow resetting the database when it is out of sync with the migrations
    • --allow-empty to create an empty migration when there are no changes to the schema
  • #5084 40d4fff5d Thanks @timleslie! - Updated context.sudo() to provide access to all operations, including those excluded by { access: false } in the public schema.

  • #5152 00f980cad Thanks @mitchellhamilton! - Updated keystone-next reset to use Prisma's programmatic APIs to reset the database.

  • #4912 d31acf61b Thanks @timleslie! - Added a config.graphql.apolloConfig option to allow developers to configure the ApolloServer object provided by Keystone.

Patch Changes

@keystone-next/types@15.0.0

Major Changes

Minor Changes

  • #3946 8e9b04ecd Thanks @timleslie! - Added experimental support for Prisma + SQLite as a database adapter.

  • #5102 714bdadce Thanks @mitchellhamilton! - Added none-skip-client-generation migrationMode

  • #5087 56e5fe10b Thanks @mitchellhamilton! - Added MigrationMode type

  • #5163 b37cbffc8 Thanks @mitchellhamilton! - Added db.useMigrations option to replace using keystone-next dev and keystone-next prototype depending on what kind of migration strategy you want to use. If you were previously using keystone-next dev, you should set db.useMigrations to true in your config and continue using keystone-next dev. If you were previously using keystone-next prototype, you should now use keystone-next dev.

  • #5084 40d4fff5d Thanks @timleslie! - Updated context.sudo() to provide access to all operations, including those excluded by { access: false } in the public schema.

  • #4912 d31acf61b Thanks @timleslie! - Added a config.graphql.apolloConfig option to allow developers to configure the ApolloServer object provided by Keystone.

Patch Changes

@keystone-next/access-control-legacy@9.0.0

Major Changes

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

Major Changes

Minor Changes

  • #3946 8e9b04ecd Thanks @timleslie! - Added experimental support for Prisma + SQLite as a database adapter.

  • #5102 714bdadce Thanks @mitchellhamilton! - Added none-skip-client-generation migrationMode

  • #5148 e6b16d4e9 Thanks @mitchellhamilton! - Updated keystone-next deploy to use Prisma's programmatic APIs to apply migrations

  • #5155 215aed387 Thanks @mitchellhamilton! - Changed keystone-next generate so that it uses Prisma's programmatic APIs to generate migrations and it accepts the following options as command line arguments or as prompts:

    • --name to set the name of the migration
    • --accept-data-loss to allow resetting the database when it is out of sync with the migrations
    • --allow-empty to create an empty migration when there are no changes to the schema
  • #5152 00f980cad Thanks @mitchellhamilton! - Updated keystone-next reset to use Prisma's programmatic APIs to reset the database.

  • #5142 543232c3f Thanks @renovate! - Updated Prisma to 2.19.0

Patch Changes

@keystone-next/keystone-legacy@21.0.0

Major Changes

Minor Changes

Patch Changes

  • #5150 3a9d20ce1 Thanks @timleslie! - Applied eslint import/order rule.

  • #4931 a4002b045 Thanks @timleslie! - Updated schema generation to no longer consider access.auth, as it is no longer used in Keystone Next.

  • Updated dependencies [4ac9148a0]:

    • @keystone-next/access-control-legacy@9.0.0

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

Major Changes

Minor Changes

Patch Changes

@keystone-next/fields@5.3.0

Minor Changes

Patch Changes

@keystone-next/fields-document@3.1.0

Minor Changes

Patch Changes

@keystone-next/fields-legacy@23.1.0

Minor Changes

Patch Changes

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

Minor Changes

Patch Changes

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

Minor Changes

Patch Changes

@keystone-next/fields-color-legacy@1.1.0

Minor Changes

Patch Changes

@keystone-next/fields-markdown-legacy@5.3.0

Minor Changes

Patch Changes

@keystone-next/fields-oembed-legacy@4.1.0

Minor Changes

Patch Changes

@keystone-next/fields-unsplash-legacy@4.1.0

Minor Changes

Patch Changes

@keystone-next/fields-wysiwyg-tinymce-legacy@5.4.0

Minor Changes

Patch Changes

@keystone-ui/core@2.0.2

Patch Changes

@keystone-ui/fields@2.0.2

Patch Changes

@keystone-ui/notice@2.0.2

Patch Changes

@keystone-ui/options@2.0.2

Patch Changes

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

Patch Changes

@keystone-next/auth@18.0.0

Patch Changes

@keystone-next/cloudinary@3.0.4

Patch Changes

@keystone-next/document-renderer@2.0.2

Patch Changes

@keystone-next/session-store-redis@1.0.2

Patch Changes

@keystone-next/adapter-knex-legacy@13.2.2

Patch Changes

@keystone-next/adapter-mongoose-legacy@11.1.2

Patch Changes

@keystone-next/app-admin-ui-legacy@7.4.3

Patch Changes

@keystone-next/app-static-legacy@5.1.5

Patch Changes

@keystone-next/field-views-loader-legacy@6.0.3

Patch Changes

@keystone-next/fields-location-google-legacy@3.3.4

Patch Changes

@keystone-next/fields-mongoid-legacy@9.1.7

Patch Changes

@keystone-next/website@1.2.0

Minor Changes

  • #3946 8e9b04ecd Thanks @timleslie! - Added experimental support for Prisma + SQLite as a database adapter.

  • #4912 d31acf61b Thanks @timleslie! - Added a config.graphql.apolloConfig option to allow developers to configure the ApolloServer object provided by Keystone.

Patch Changes

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

Minor Changes

Patch Changes

@keystone-ui/website@1.0.2

Patch Changes

  • #5150 3a9d20ce1 Thanks @timleslie! - Applied eslint import/order rule.

  • Updated dependencies [17c86e0c3, 3a9d20ce1]:

    • @keystone-ui/fields@2.0.2
    • @keystone-ui/options@2.0.2
    • @keystone-ui/core@2.0.2
    • @keystone-ui/notice@2.0.2

@keystone-next/example-auth@1.0.3

Patch Changes

@keystone-next/app-basic@1.0.3

Patch Changes

@keystone-next/example-ecommerce@1.0.3

Patch Changes

keystone-next-app@0.0.3

Patch Changes

@keystone-next/example-roles@1.0.3

Patch Changes

@keystone-next/example-sandbox@1.0.3

Patch Changes

@keystone-next/example-todo@1.0.3

Patch Changes

@keystone-next/benchmarks-legacy@5.2.2

Patch Changes

@keystonejs/examples-smoke-tests@0.0.1

Patch Changes

@keystone-next/cypress-project-access-control-legacy@6.0.5

Patch Changes

@keystone-next/cypress-project-basic-legacy@7.0.6

Patch Changes

@keystone-next/cypress-project-client-validation-legacy@7.0.5

Patch Changes

@keystone-next/cypress-project-login-legacy@6.0.5

Patch Changes

@vercel
Copy link

vercel bot commented Mar 10, 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/bgTwvDsmKU1EnojeSviVo1ACGPQt
✅ Preview: https://keystone-next-docs-git-changeset-release-master-keystonejs.vercel.app

@vercel vercel bot temporarily deployed to Preview March 10, 2021 04:15 Inactive
@vercel vercel bot temporarily deployed to Preview March 10, 2021 04:52 Inactive
@vercel vercel bot temporarily deployed to Preview March 10, 2021 21:45 Inactive
@vercel vercel bot temporarily deployed to Preview March 10, 2021 21:53 Inactive
@vercel vercel bot temporarily deployed to Preview March 11, 2021 02:05 Inactive
@vercel vercel bot temporarily deployed to Preview March 11, 2021 02:15 Inactive
@vercel vercel bot temporarily deployed to Preview March 11, 2021 04:35 Inactive
@vercel vercel bot temporarily deployed to Preview March 11, 2021 04:48 Inactive
@vercel vercel bot temporarily deployed to Preview March 11, 2021 04:57 Inactive
@vercel vercel bot temporarily deployed to Preview March 11, 2021 23:28 Inactive
@vercel vercel bot temporarily deployed to Preview March 11, 2021 23:53 Inactive
@vercel vercel bot temporarily deployed to Preview March 12, 2021 00:42 Inactive
@vercel vercel bot temporarily deployed to Preview March 12, 2021 02:37 Inactive
@vercel vercel bot temporarily deployed to Preview March 12, 2021 03:02 Inactive
@vercel vercel bot temporarily deployed to Preview March 12, 2021 03:11 Inactive
@vercel vercel bot temporarily deployed to Preview March 17, 2021 05:17 Inactive
@vercel vercel bot temporarily deployed to Preview March 17, 2021 05:35 Inactive
@vercel vercel bot temporarily deployed to Preview March 17, 2021 21:26 Inactive
@vercel vercel bot temporarily deployed to Preview March 18, 2021 00:44 Inactive
@vercel vercel bot temporarily deployed to Preview March 18, 2021 05:55 Inactive
@vercel vercel bot temporarily deployed to Preview March 18, 2021 06:11 Inactive
@vercel vercel bot temporarily deployed to Preview March 18, 2021 22:21 Inactive
@vercel vercel bot temporarily deployed to Preview March 19, 2021 00:10 Inactive
@vercel vercel bot temporarily deployed to Preview March 19, 2021 00:45 Inactive
@vercel vercel bot temporarily deployed to Preview March 21, 2021 21:32 Inactive
@vercel vercel bot temporarily deployed to Preview March 21, 2021 22:18 Inactive
Copy link
Contributor

@timleslie timleslie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

@timleslie timleslie merged commit 7fb3d36 into master Mar 21, 2021
@timleslie timleslie deleted the changeset-release/master branch March 21, 2021 22:30
@bladey bladey changed the title Version Packages ✨ Release - 22nd March 2021 May 7, 2021
@bladey bladey changed the title ✨ Release - 22nd March 2021 Version Packages May 12, 2021
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.

3 participants