All the new Monorepo things

.changeset/README.md

@@ -1,37 +1,8 @@
-
 # Changesets
 
-Hello and welcome! This folder has been automatically generated by `@atlaskit/build-releases`, a build tool that works with `bolt` to help you release components from a mono-repository. You can find the full documentation for it [here](https://www.npmjs.com/package/@atlaskit/build-releases)
-
-To help you get started though, here are some things you should know about this folder:
-
-## Changesets are automatically generated
-
-Changesets are generated by the `build-releases changeset` command, though it may have been given a new name within your repository. As long as you are following a changeset release flow, you shouldn't have any problems.
-
-## Each changeset is its own folder
-
-We use hashes by default for these folder names to avoid collisions when generating them, but there's no harm that will come from renaming them.
-
-## Changesets are automatically removed
-
-When `build-releases version` or equivalent command is run, all the changeset folders are removed. This is so we only ever use a changeset once. This makes this a very bad place to store any other information.
-
-## Changesets come in two parts
-
-You should treat these parts quite differently:
-
-- `changes.md` is a file you should feel free to edit as much as you want. It will be prepended to your changelog when you next run your version command.
-- `changes.json` is a file that includes information about releases, what should be versioned by the version command. We strongly recommend against editing this directly, as you may make a new changeset that puts your bolt repository into an invalid state.
-
-## I want to edit the information in a `changes.json` - how do I do it safely?
-
-The best option is to make a new changeset using the changeset command, copy over the `changes.md`, then delete the old changeset.
-
-## Can I rename the folder for my changeset?
-
-Absolutely! We need unique hashes to make changesets play nicely with git, but changing your folder from our hash to your own name isn't going to cause any problems.
-
-## Can I manually delete changesets?
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
 
-You can, but you should be aware this will remove the intent to release communicated by the changeset, and should be done with caution.
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/master/docs/common-questions.md)

.changeset/config.json

@@ -0,0 +1,7 @@
+{
+  "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
+  "changelog": ["@changesets/changelog-github", { "repo": "keystonejs/keystone-5" }],
+  "commit": false,
+  "linked": [],
+  "access": "public"
+}

.circleci/config.yml

@@ -32,14 +32,13 @@ x-integration-steps: &integration-steps
   steps:
     - checkout
     - restore_cache: *restore-cache
-    - run: sudo yarn global add bolt
     - run:
-        name: Bolt - Install packages
-        command: CYPRESS_CACHE_FOLDER=$CIRCLE_WORKING_DIRECTORY/node_modules/cypress/.cache/ bolt
+        name: Yarn - Install packages
+        command: CYPRESS_CACHE_FOLDER=$CIRCLE_WORKING_DIRECTORY/node_modules/cypress/.cache/ yarn
     - save_cache: *save-cache
     - run:
         name: E2E Cypress tests
-        command: CYPRESS_CACHE_FOLDER=$CIRCLE_WORKING_DIRECTORY/node_modules/cypress/.cache/ bolt ws run cypress:run:ci --only-fs $PROJECT_DIRECTORY
+        command: CYPRESS_CACHE_FOLDER=$CIRCLE_WORKING_DIRECTORY/node_modules/cypress/.cache/ yarn --cwd $PROJECT_DIRECTORY cypress:run:ci
     - run:
         name: Prepare artifacts
         command: |
@@ -71,11 +70,10 @@ jobs:
       - run: psql -d $TEST_DATABASE_URL -c "CREATE SCHEMA keystone;"
       - run: psql -d $TEST_DATABASE_URL -c "CREATE USER keystone5 PASSWORD 'k3yst0n3';"
       - run: psql -d $TEST_DATABASE_URL -c "GRANT ALL ON SCHEMA keystone TO keystone5;"
-      - run: sudo yarn global add bolt
       # Set Cypress cache dir here, in case this job runs/completes first, and
       # hence clobbers the `node_modules` cache with a non-cypress version,
       # causing the other job to fail with a "Missing Cypress" error.
-      - run: CYPRESS_CACHE_FOLDER=$CIRCLE_WORKING_DIRECTORY/node_modules/cypress/.cache/ bolt
+      - run: CYPRESS_CACHE_FOLDER=$CIRCLE_WORKING_DIRECTORY/node_modules/cypress/.cache/ yarn
       - save_cache: *save-cache
       # run tests!
       - run: yarn lint:eslint --format junit -o reports/junit/js-lint-results.xml

.github/workflows/release.yml

@@ -16,14 +16,11 @@ jobs:
       - name: Setup Node.js 10.x
         uses: actions/setup-node@master
         with:
-          version: 10.x
-
-      - name: Install Bolt
-        run: npm install --global bolt
+          node-version: 10.x
 
       - name: Install Dependencies
         # we have a postinstall script that uses is-ci which doesn't yet detect GitHub Actions
-        run: CI=true bolt
+        run: CI=true yarn
 
       - name: Create Release Pull Request
         uses: changesets/action@master