From 28ad6b3c71a4f008eb2798c124b81e10e86ef12a Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Wed, 12 Aug 2026 18:26:53 +0000
Subject: [PATCH] Version packages

---
 .changeset/scaffold-flutter-0-6.md      | 19 -------------------
 packages/create-eigen-game/CHANGELOG.md | 20 ++++++++++++++++++++
 packages/create-eigen-game/package.json |  2 +-
 3 files changed, 21 insertions(+), 20 deletions(-)
 delete mode 100644 .changeset/scaffold-flutter-0-6.md

diff --git a/.changeset/scaffold-flutter-0-6.md b/.changeset/scaffold-flutter-0-6.md
deleted file mode 100644
index fb53d1c..0000000
--- a/.changeset/scaffold-flutter-0-6.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-"create-eigen-game": minor
----
-
-Install `eigen_flutter@^0.6.0` into the app half, matching the engine's 0.4.x line.
-
-This is a required pairing rather than an improvement. The 0.4.x engine takes
-`cursor` as an opaque string and returns `nextCursor` on every paged response,
-and `eigen_flutter` 0.6.0 is the first shell that pins `eigen_api: ^0.4.0` and
-can read it. Everything below pins `eigen_api: ^0.3.0` or older, so a scaffold
-left on `^0.4.1` installed the engine's current line beside a shell that could
-not read a single paged list from it: it resolved, it compiled, and then the
-lobby and the history screen were empty. 0.5.0 is skipped for the same reason,
-being a web-design release that still speaks the 0.3.x wire.
-
-Closes the window opened by the engine's own 0.4.0 release: because
-`updateInternalDependencies` republishes this package whenever the engine
-version moves, the scaffolder had already gone out pairing a 0.4.x worker with a
-0.4.1 shell.
diff --git a/packages/create-eigen-game/CHANGELOG.md b/packages/create-eigen-game/CHANGELOG.md
index f66445c..a22db99 100644
--- a/packages/create-eigen-game/CHANGELOG.md
+++ b/packages/create-eigen-game/CHANGELOG.md
@@ -1,5 +1,25 @@
 # create-eigen-game
 
+## 0.11.0
+
+### Minor Changes
+
+- [#62](https://github.com/eigeninteractive/eigen-server/pull/62) [`e8c537f`](https://github.com/eigeninteractive/eigen-server/commit/e8c537fd29bc0d8a6d0d252c41bd411692dab298) Thanks [@seenu-k](https://github.com/seenu-k)! - Install `eigen_flutter@^0.6.0` into the app half, matching the engine's 0.4.x line.
+  
+  This is a required pairing rather than an improvement. The 0.4.x engine takes
+  `cursor` as an opaque string and returns `nextCursor` on every paged response,
+  and `eigen_flutter` 0.6.0 is the first shell that pins `eigen_api: ^0.4.0` and
+  can read it. Everything below pins `eigen_api: ^0.3.0` or older, so a scaffold
+  left on `^0.4.1` installed the engine's current line beside a shell that could
+  not read a single paged list from it: it resolved, it compiled, and then the
+  lobby and the history screen were empty. 0.5.0 is skipped for the same reason,
+  being a web-design release that still speaks the 0.3.x wire.
+  
+  Closes the window opened by the engine's own 0.4.0 release: because
+  `updateInternalDependencies` republishes this package whenever the engine
+  version moves, the scaffolder had already gone out pairing a 0.4.x worker with a
+  0.4.1 shell.
+
 ## 0.10.2
 
 ### Patch Changes
diff --git a/packages/create-eigen-game/package.json b/packages/create-eigen-game/package.json
index 013c077..beb52ab 100644
--- a/packages/create-eigen-game/package.json
+++ b/packages/create-eigen-game/package.json
@@ -1,6 +1,6 @@
 {
   "name": "create-eigen-game",
-  "version": "0.10.2",
+  "version": "0.11.0",
   "license": "MIT",
   "description": "Scaffold an EigenInteractive game Worker and Flutter app without cloning the engine repositories.",
   "type": "module",