diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index c2ba01ff..134fd305 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -20,7 +20,7 @@ jobs:
     - uses: actions/checkout@v2.3.4
     - uses: actions/setup-node@v2.4.1
       with:
-        node-version: 12.x
+        node-version: 16.x
     - name: install dependencies
       run: yarn install
     - name: linting
@@ -32,7 +32,7 @@ jobs:
 
     strategy:
       matrix:
-        node: ['10', '12', '14', '15']
+        node: ['12', '14', '16', '17']
         os: [ubuntu, windows]
 
     steps:
@@ -53,7 +53,7 @@ jobs:
     - uses: actions/checkout@v2.3.4
     - uses: actions/setup-node@v2.4.1
       with:
-        node-version: '14.x'
+        node-version: '16.x'
     - run: yarn install --no-lockfile
     - run: yarn build
     - name: test
diff --git a/README.md b/README.md
index aad588f2..2a91d04c 100644
--- a/README.md
+++ b/README.md
@@ -162,7 +162,7 @@ unique SemVer commitments. A high level summary is:
 
 The following are scenarios that would cause a major version (aka breaking change) release:
 
-* Dropping support for Node versions (e.g. dropping Node 10 support)
+* Dropping support for Node versions (e.g. dropping Node 12 support)
 * Non-additive changes to the underlying AST (which we bundle from `@glimmer/syntax`)
 * Breaking changes to the `@glimmer/syntax` builder APIs
 
diff --git a/package.json b/package.json
index f84a77a2..4c5b225a 100644
--- a/package.json
+++ b/package.json
@@ -66,7 +66,7 @@
     "typescript": "~4.2.4"
   },
   "engines": {
-    "node": "10.* || 12.* || >= 14.*"
+    "node": "12.* || 14.* || >= 16.*"
   },
   "publishConfig": {
     "registry": "https://registry.npmjs.org"