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 #6943

Merged
merged 1 commit into from
Nov 23, 2021
Merged

Version Packages #6943

merged 1 commit into from
Nov 23, 2021

Conversation

keystonejs-release-bot
Copy link
Collaborator

@keystonejs-release-bot keystonejs-release-bot commented Nov 15, 2021

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@keystone-ui/button@6.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

  • Updated dependencies [de8cf44e7, 748538649]:
    • @keystone-ui/core@4.0.0
    • @keystone-ui/icons@5.0.0
    • @keystone-ui/loading@5.0.0

@keystone-ui/core@4.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-ui/fields@6.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-ui/icons@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-ui/loading@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-ui/modals@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

  • Updated dependencies [de8cf44e7, 748538649]:
    • @keystone-ui/button@6.0.0
    • @keystone-ui/core@4.0.0

@keystone-ui/notice@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

  • Updated dependencies [de8cf44e7, 748538649]:
    • @keystone-ui/button@6.0.0
    • @keystone-ui/core@4.0.0
    • @keystone-ui/icons@5.0.0

@keystone-ui/options@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-ui/pill@6.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

  • Updated dependencies [de8cf44e7, 748538649]:
    • @keystone-ui/core@4.0.0
    • @keystone-ui/icons@5.0.0

@keystone-ui/popover@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-ui/segmented-control@6.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-ui/toast@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

  • Updated dependencies [de8cf44e7, 748538649]:
    • @keystone-ui/core@4.0.0
    • @keystone-ui/icons@5.0.0

@keystone-ui/tooltip@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

  • Updated dependencies [de8cf44e7, 748538649]:
    • @keystone-ui/core@4.0.0
    • @keystone-ui/popover@5.0.0

@keystone-next/auth@37.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/cloudinary@12.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/document-renderer@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/fields-document@14.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/keystone@29.0.0

Major Changes

  • #6920 82539faa5 Thanks @mitchellhamilton! - Keystone now uses Prisma's Node-API Query Engine instead of the Binary Query Engine. This should improve the performance of operations using Prisma. See https://www.prisma.io/docs/concepts/components/prisma-engines/query-engine for more details.

  • #6917 04c54a4eb Thanks @mitchellhamilton! - The names of one-sided and two-sided, many-many relationships has been shortened. Two-sided many-many relationship names contain only the left-hand side names now; and the _many suffix has been dropped from one-sided many-many relationships.

    This reduces the probability that you will exceed PostgreSQL's 63 character limit for identifiers with typical usage.

    This is a breaking change.

    There are two ways to update:

    Set db.relationName on many to many relation

    Rather than doing a migration, you can set the new field property db.relationName, for either side of a many-to-many relationship field.
    If set to the existing relation name, your database will remain unchanged.

    For example, given a schema like this:

    Post: list({
      fields: {
        tags: relationship({ ref: 'Tag.posts', many: true }),
      },
    }),
    Tag: list({
      fields: {
        posts: relationship({ ref: 'Post.tags', many: true }),
      },
    }),

    Before this release, the generated Prisma schema looked like this:

    // This file is automatically generated by Keystone, do not modify it manually.
    // Modify your Keystone config when you want to change this.
    
    datasource postgresql {
      url      = env("DATABASE_URL")
      provider = "postgresql"
    }
    
    generator client {
      provider   = "prisma-client-js"
      output     = "node_modules/.prisma/client"
      engineType = "binary"
    }
    
    model Post {
      id   String @id @default(cuid())
      tags Tag[]  @relation("Post_tags_Tag_posts")
    }
    
    model Tag {
      id    String @id @default(cuid())
      posts Post[] @relation("Post_tags_Tag_posts")
    }

    By adding db: { relationName: 'Post_tags_Tag_posts' } to one side of the many-to-many relationship; you can preclude yourself from a migration.

    Note: It doesn't matter which side of the relationship you put this property, but it should be only on one side; otherwise you will receive an error.

    Post: list({
      fields: {
        tags: relationship({ ref: 'Tag.posts', many: true, db: { relationName: 'Post_tags_Tag_posts' } }),
      },
    }),
    Tag: list({
      fields: {
        posts: relationship({ ref: 'Post.tags', many: true }),
      },
    }),

    Rename your many relation tables using a migration

    For example, given a schema like this:

    Post: list({
      fields: {
        tags: relationship({ ref: 'Tag.posts', many: true }),
      },
    }),
    Tag: list({
      fields: {
        posts: relationship({ ref: 'Post.tags', many: true }),
      },
    }),

    When updating to this change, and running yarn dev, Keystone will prompt you to update your schema.

    • If you are using useMigrations: true, Keystone will follow the typical migration flow offer to apply an automatically generated migration. DO NOT APPLY THE AUTOMATICALLY GENERATED MIGRATION - unless you want to DROP your data.

    • If you are using useMigrations: false, Keystone will follow the typical flow and offer to automatically migrate your schema. Again, DO NOT RUN THE AUTOMATIC MIGRATION - unless you want to DROP your data.

    On PostgreSQL, Prisma will generate a migration that looks something like this:

    /*
      Warnings:
    
      - You are about to drop the `_Post_tags_Tag_posts` table. If the table is not empty, all the data it contains will be lost.
    
    */
    -- DropForeignKey
    ALTER TABLE "_Post_tags_Tag_posts" DROP CONSTRAINT "_Post_tags_Tag_posts_A_fkey";
    
    -- DropForeignKey
    ALTER TABLE "_Post_tags_Tag_posts" DROP CONSTRAINT "_Post_tags_Tag_posts_B_fkey";
    
    -- DropTable
    DROP TABLE "_Post_tags_Tag_posts";
    
    -- CreateTable
    CREATE TABLE "_Post_tags" (
        "A" TEXT NOT NULL,
        "B" TEXT NOT NULL
    );
    
    -- CreateIndex
    CREATE UNIQUE INDEX "_Post_tags_AB_unique" ON "_Post_tags"("A", "B");
    
    -- CreateIndex
    CREATE INDEX "_Post_tags_B_index" ON "_Post_tags"("B");
    
    -- AddForeignKey
    ALTER TABLE "_Post_tags" ADD FOREIGN KEY ("A") REFERENCES "Post"("id") ON DELETE CASCADE ON UPDATE CASCADE;
    
    -- AddForeignKey
    ALTER TABLE "_Post_tags" ADD FOREIGN KEY ("B") REFERENCES "Tag"("id") ON DELETE CASCADE ON UPDATE CASCADE;

    You need to modify it so that it looks like this with the old and new table names for your schema substituted:

    ALTER TABLE "_Post_tags_Tag_posts" RENAME TO "_Post_tags";
    ALTER INDEX "_Post_tags_Tag_posts_AB_unique" RENAME TO "_Post_tags_AB_unique";
    ALTER INDEX "_Post_tags_Tag_posts_B_index" RENAME TO "_Post_tags_B_index";
    ALTER TABLE "_Post_tags" RENAME CONSTRAINT "_Post_tags_Tag_posts_A_fkey" TO "_Post_tags_A_fkey";
    ALTER TABLE "_Post_tags" RENAME CONSTRAINT "_Post_tags_Tag_posts_B_fkey" TO "_Post_tags_B_fkey";

    On SQLite, Prisma will generate a migration that looks something like this:

    /*
      Warnings:
    
      - You are about to drop the `_Post_tags_Tag_posts` table. If the table is not empty, all the data it contains will be lost.
    
    */
    -- DropTable
    PRAGMA foreign_keys=off;
    DROP TABLE "_Post_tags_Tag_posts";
    PRAGMA foreign_keys=on;
    
    -- CreateTable
    CREATE TABLE "_Post_tags" (
        "A" TEXT NOT NULL,
        "B" TEXT NOT NULL,
        FOREIGN KEY ("A") REFERENCES "Post" ("id") ON DELETE CASCADE ON UPDATE CASCADE,
        FOREIGN KEY ("B") REFERENCES "Tag" ("id") ON DELETE CASCADE ON UPDATE CASCADE
    );
    
    -- CreateIndex
    CREATE UNIQUE INDEX "_Post_tags_AB_unique" ON "_Post_tags"("A", "B");
    
    -- CreateIndex
    CREATE INDEX "_Post_tags_B_index" ON "_Post_tags"("B");

    You need to modify it so that it looks like this with the old and new table names for your schema substituted:

    ALTER TABLE "_Post_tags_Tag_posts" RENAME TO "_Post_tags";
    DROP INDEX "_Post_tags_Tag_posts_AB_unique";
    DROP INDEX "_Post_tags_Tag_posts_B_index";
    CREATE UNIQUE INDEX "_Post_tags_AB_unique" ON "_Post_tags"("A", "B");
    CREATE INDEX "_Post_tags_B_index" ON "_Post_tags"("B");
  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Minor Changes

  • #6968 f2b41df9f Thanks @JedWatson! - Added db.foreignKey option to the relationship field that allows you to explicitly pick which side of a one to one relationship the foreign key should be on and for one to one or one to many relationships add @map to the foreign key to change the column name in the database.

  • #6917 04c54a4eb Thanks @mitchellhamilton! - Added db.relationName option to many to many relationship fields to allow explicitly setting the relation name.

Patch Changes

  • #6911 748538649 Thanks @dcousens! - Explicitly declare return type on createExpressServer

  • #6967 4e96c23bb Thanks @mitchellhamilton! - Fixed relationship field not respecting ui.displayMode: 'cards' in the create view.

  • #6949 76ec35c97 Thanks @bladey! - Fixed React key error in relationship field with ui.displayMode: 'cards'

  • #6955 760ae82ac Thanks @mitchellhamilton! - Fixed ui.isAccessAllowed not being respected in the admin meta query when no session strategy was defined

  • #6932 0a7b75838 Thanks @mitchellhamilton! - Field-level hooks and field-level create and update access control functions are now awaited in parallel. Note this means all field-level hooks and access control are now awaited in parallel because field-level read access control was already awaited in parallel.

  • 622e57689 Thanks @JedWatson! - Pinned @apollo/client to 3.4.17, fixes an incompatibility between @apollo/client >= 3.5.0 and apollo-upload-client that breaks the Admin UI.

    We can revert this when jaydenseric/apollo-upload-client#273 has been resolved (may also be resolved by apollographql/apollo-client#9103)

  • #6972 bbedee845 Thanks @mitchellhamilton! - The item page in the Admin UI no longer crashes when failing to fetch an item.

  • #6955 760ae82ac Thanks @mitchellhamilton! - The admin meta query now bypasses ui.isAccessAllowed for sudo contexts.

  • #6974 96fd2e220 Thanks @JedWatson! - Removed unnecessary @types/ dependencies

  • #6920 82539faa5 Thanks @mitchellhamilton! - Fixed doing multiple writes at the same time on SQLite causing an timeout immediately.

  • #6948 7a7450009 Thanks @mitchellhamilton! - The Set as Authenticated Item/Add Authenticated Item button is now hidden if the relationship field already has the authenticated item.

  • Updated dependencies [96fd2e220, de8cf44e7, 748538649]:

    • @keystone-ui/fields@6.0.0
    • @keystone-ui/options@5.0.0
    • @keystone-ui/button@6.0.0
    • @keystone-ui/core@4.0.0
    • @keystone-ui/icons@5.0.0
    • @keystone-ui/loading@5.0.0
    • @keystone-ui/modals@5.0.0
    • @keystone-ui/notice@5.0.0
    • @keystone-ui/pill@6.0.0
    • @keystone-ui/popover@5.0.0
    • @keystone-ui/segmented-control@6.0.0
    • @keystone-ui/toast@5.0.0
    • @keystone-ui/tooltip@5.0.0

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

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-ui/website@4.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

  • Updated dependencies [96fd2e220, de8cf44e7, 748538649]:
    • @keystone-ui/fields@6.0.0
    • @keystone-ui/options@5.0.0
    • @keystone-ui/button@6.0.0
    • @keystone-ui/core@4.0.0
    • @keystone-ui/loading@5.0.0
    • @keystone-ui/modals@5.0.0
    • @keystone-ui/notice@5.0.0
    • @keystone-ui/pill@6.0.0
    • @keystone-ui/popover@5.0.0
    • @keystone-ui/segmented-control@6.0.0
    • @keystone-ui/toast@5.0.0
    • @keystone-ui/tooltip@5.0.0

@keystone-next/website@4.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-assets-cloud@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-assets-local@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-auth@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/examples-app-basic@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-ecommerce@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-embedded-nextjs@4.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

keystone-next-app@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-roles@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-sandbox@4.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-blog@3.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-custom-admin-ui-logo@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-custom-admin-ui-navigation@6.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-custom-admin-ui-pages@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-custom-field@1.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-custom-field-view@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-default-values@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-document-field@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-extend-graphql-schema@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-extend-graphql-schema-graphql-ts@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-extend-graphql-schema-nexus@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-json-field@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-rest-api@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-task-manager@5.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-testing@1.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-virtual-field@1.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/example-with-auth@3.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/prisma-utils@2.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

@keystone-next/admin-ui-tests@1.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

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

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

@keystone-next/benchmarks-legacy@8.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystonejs/examples-smoke-tests@3.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

@keystone-next/test-projects-basic@1.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/test-projects-crud-notifications@1.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@keystone-next/test-projects-live-reloading@1.0.0

Major Changes

  • #6957 de8cf44e7 Thanks @bladey! - Update Node engines to support current Node LTS versions, currently versions 14 and 16.

Patch Changes

@vercel
Copy link

vercel bot commented Nov 15, 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/D5BwbKTopJAj6JToXJuBZZ3SSRvm
✅ Preview: https://keystone-next-docs-git-changeset-release-main-keystonejs.vercel.app

@vercel vercel bot temporarily deployed to Preview November 15, 2021 23:06 Inactive
@codesandbox-ci
Copy link

codesandbox-ci bot commented Nov 15, 2021

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.

@vercel vercel bot temporarily deployed to Preview November 16, 2021 02:50 Inactive
@vercel vercel bot temporarily deployed to Preview November 16, 2021 05:03 Inactive
@vercel vercel bot temporarily deployed to Preview November 16, 2021 06:00 Inactive
@vercel vercel bot temporarily deployed to Preview November 16, 2021 22:57 Inactive
@vercel vercel bot temporarily deployed to Preview November 17, 2021 00:49 Inactive
@vercel vercel bot temporarily deployed to Preview November 17, 2021 01:14 Inactive
@vercel vercel bot temporarily deployed to Preview November 17, 2021 02:06 Inactive
@vercel vercel bot temporarily deployed to Preview November 17, 2021 02:25 Inactive
@vercel vercel bot temporarily deployed to Preview November 17, 2021 02:43 Inactive
@vercel vercel bot temporarily deployed to Preview November 17, 2021 03:18 Inactive
@vercel vercel bot temporarily deployed to Preview November 17, 2021 03:43 Inactive
@vercel vercel bot temporarily deployed to Preview November 17, 2021 05:36 Inactive
@vercel vercel bot temporarily deployed to Preview November 18, 2021 00:50 Inactive
@vercel vercel bot temporarily deployed to Preview November 18, 2021 03:20 Inactive
@vercel vercel bot temporarily deployed to Preview November 18, 2021 10:05 Inactive
@vercel vercel bot temporarily deployed to Preview November 19, 2021 03:11 Inactive
@vercel vercel bot temporarily deployed to Preview November 21, 2021 23:11 Inactive
@vercel vercel bot temporarily deployed to Preview November 22, 2021 05:08 Inactive
@vercel vercel bot temporarily deployed to Preview November 22, 2021 06:03 Inactive
@vercel vercel bot temporarily deployed to Preview November 22, 2021 23:11 Inactive
@vercel vercel bot temporarily deployed to Preview November 22, 2021 23:25 Inactive
@bladey bladey requested a review from dcousens November 23, 2021 01:08
@vercel vercel bot temporarily deployed to Preview November 23, 2021 22:52 Inactive
Copy link
Member

@dcousens dcousens left a comment

Choose a reason for hiding this comment

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

LGTM

@bladey bladey merged commit e9221e7 into main Nov 23, 2021
@bladey bladey deleted the changeset-release/main branch November 23, 2021 23:44
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