Skip to content
This repository was archived by the owner on Sep 10, 2026. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 0 additions & 30 deletions .changeset/append-never-insert.md

This file was deleted.

31 changes: 31 additions & 0 deletions packages/create-eigen-game/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,36 @@
# create-eigen-game

## 0.10.2

### Patch Changes

- [#58](https://github.com/eigeninteractive/eigen-server/pull/58) [`d9916de`](https://github.com/eigeninteractive/eigen-server/commit/d9916de6adb0a882bb40bac2d34b6ea6f9807a35) Thanks [@seenu-k](https://github.com/seenu-k)! - Give the three edits into files the scaffolder does not own one shared whitespace
rule, and write down the doctrine they follow.

`enableAndroidCoreLibraryDesugaring`, `enableAndroidReleaseSigning` and
`configureLauncherIconsAndSplash` each append a block to a file `flutter create`
produced. All three normalised newlines themselves, with two different answers,
so the desugaring block got a blank line before it and the other two did not: in
a generated project the two Gradle blocks ended up flush against each other.
`appendBlock` now owns that and nothing else, one blank line before and one
newline after, with the block constants carrying neither, and the scaffold test
pins the separation rather than only the contents.

No behavioural change beyond the whitespace of generated `build.gradle.kts` and
`pubspec.yaml`. A comment claiming the release-signing block still prepends a
Kotlin `import` was also stale, describing an edit removed when it broke under
AGP 9, and said the opposite of the rule it sat next to.

MAINTAINERS.md gains **Editing files the scaffolder does not own**: append never
insert, why every block is recognised by a content probe on its own payload, and
why FlutterFire's `// START:`/`// END:` marker comments are deliberately not
copied. Those markers are attribution rather than machinery, never read back by
`flutterfire_cli` itself, and an append needs no anchor; the one condition that
would earn a marker pair is a block whose content must be found and replaced on a
later run, which is an upgrade command's problem and not one that exists yet. It
also records that configuration values are assigned into declared slots instead,
and the JSON-versus-JSONC rule that governs how.

## 0.10.1

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion packages/create-eigen-game/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "create-eigen-game",
"version": "0.10.1",
"version": "0.10.2",
"license": "MIT",
"description": "Scaffold an EigenInteractive game Worker and Flutter app without cloning the engine repositories.",
"type": "module",
Expand Down