Release: version packages

packages/create-eigen-game/CHANGELOG.md

@@ -1,5 +1,18 @@
 # create-eigen-game
 
+## 0.9.2
+
+### Patch Changes
+
+- [#50](https://github.com/eigeninteractive/eigen-server/pull/50) [`96438c4`](https://github.com/eigeninteractive/eigen-server/commit/96438c450d481db74f40fed4e32f9690a7938294) Thanks [@seenu-k](https://github.com/seenu-k)! - A scaffold now fills in the deployment values it already knows, instead of leaving four empty strings for the reader to chase.
+
+  - `app-config.json` ships with `API_BASE_URL` pointing at `http://localhost:8787`, so `pnpm dev` and `flutter run` agree with nothing edited.
+  - `FIREBASE_PROJECT_ID` is written into `server/wrangler.jsonc` from the project FlutterFire recorded, and `GOOGLE_WEB_CLIENT_ID` into `app-config.json` from the OAuth client Firebase created for it. Left empty, as `FIREBASE_PROJECT_ID` was before, every authenticated request answers 500.
+
+  The writing belongs to `eigen_flutter`'s `configure_firebase`, which this now invokes as `--worker ../server`, and which the generated `firebase:configure` script passes too. One implementation, so a project configured by re-running that command ends up exactly where a freshly scaffolded one does. It needs an `eigen_flutter` new enough to accept `--worker`.
+
+  What is left is what genuinely cannot be derived, and the closing summary lists exactly that: the Google sign-in provider when it is off, since the OAuth client does not exist until somebody enables it in the console, and `FIREBASE_VAPID_KEY`, which is a Web Push certificate the Firebase CLI does not serve. `WEB_APP_ORIGIN` was already defaulted to the port the scaffold trusts.
+
 ## 0.9.1
 
 ### Patch Changes

packages/create-eigen-game/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-eigen-game",
-  "version": "0.9.1",
+  "version": "0.9.2",
   "license": "MIT",
   "description": "Scaffold an EigenInteractive game Worker and Flutter app without cloning the engine repositories.",
   "type": "module",