This repository was archived by the owner on Sep 10, 2026. It is now read-only.
Repository navigation
Release: version packages - #49
Merged
Merged
Conversation
eigen-release
Bot
force-pushed
the
changeset-release/main
branch
from
August 9, 2026 18:32
7c34cd7 to
ecd5e80
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm 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
create-eigen-game@0.9.2
Patch Changes
#50
96438c4Thanks @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.jsonships withAPI_BASE_URLpointing athttp://localhost:8787, sopnpm devandflutter runagree with nothing edited.FIREBASE_PROJECT_IDis written intoserver/wrangler.jsoncfrom the project FlutterFire recorded, andGOOGLE_WEB_CLIENT_IDintoapp-config.jsonfrom the OAuth client Firebase created for it. Left empty, asFIREBASE_PROJECT_IDwas before, every authenticated request answers 500.The writing belongs to
eigen_flutter'sconfigure_firebase, which this now invokes as--worker ../server, and which the generatedfirebase:configurescript passes too. One implementation, so a project configured by re-running that command ends up exactly where a freshly scaffolded one does. It needs aneigen_flutternew 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_ORIGINwas already defaulted to the port the scaffold trusts.