This repository was archived by the owner on Sep 10, 2026. It is now read-only.
Repository navigation
Scaffold eigen_flutter ^0.6.0 alongside the 0.4.x engine - #62
Merged
Merged
Conversation
The engine's 0.4.x line takes `cursor` as an opaque string and returns `nextCursor` on every paged response. `eigen_flutter` 0.6.0 is the first shell pinning `eigen_api: ^0.4.0` that can read it; everything below pins ^0.3.0 or older. A scaffold left on ^0.4.1 therefore installed the current worker beside a shell that cannot read a single paged list from it, which resolves, compiles, and then shows an empty lobby and an empty history. This closes a window the engine's own 0.4.0 release opened: `updateInternalDependencies` republishes this package whenever the engine version moves, so a scaffolder pairing a 0.4.x worker with a 0.4.1 shell has already been published. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
1 participant
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.
Closes the scaffolder window opened by the 0.4.0 engine release.
Draft: blocked until
eigen_flutter0.6.0 publishes. The release run forv0.6.0is currently gated, and theScaffolded project buildscheck runsflutter pub add eigen_flutter@^0.6.0, which cannot resolve until then. Mark ready once it lands.Why this is required, not an improvement
The 0.4.x engine takes
cursoras an opaque string and returnsnextCursoron every paged response.eigen_flutter0.6.0 is the first shell pinningeigen_api: ^0.4.0that can read it; everything below pins^0.3.0or older.So a scaffold left on
^0.4.1installs the engine's current line beside a shell that cannot read a single paged list from it. It resolves, it compiles, and then the lobby and the history screen are empty — the same "worst of the three" failure the 0.4.0 note in that doc block already describes.0.5.0 is skipped for the same reason: a web-design release that still speaks the 0.3.x wire.
The window this closes
updateInternalDependencies: "patch"plus@eigeninteractive/server: workspace:*means changesets republishescreate-eigen-gameautomatically whenever the engine version moves. So the moment the engine went to 0.4.0, a scaffolder pairing a 0.4.x worker with a 0.4.1 shell was already published. That pairing is live right now.Nothing in this repository can detect that on its own — the pin is a stated version precisely because
eigen_flutterlives elsewhere and only compiling a scaffolded app establishes which release the templates work against. TheScaffolded project buildsjob is what proves it, and on this PR it will be proving it against 0.6.0 for the first time.Changes
flutterClientVersion→"^0.6.0", with a doc-block note in the form of the existing 0.4.0 and 0.4.1 onesscaffold.spec.tsminorchangeset80 scaffolder tests pass; lint clean.
🤖 Generated with Claude Code