Skip to content

Release: version packages - #20

Merged
seenu-k merged 1 commit into
mainfrom
changeset-release/main
Aug 6, 2026
Merged

Release: version packages#20
seenu-k merged 1 commit into
mainfrom
changeset-release/main

Conversation

@eigen-release

@eigen-release eigen-release Bot commented Aug 6, 2026

Copy link
Copy Markdown

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.5.0

Minor Changes

  • #19 993883f Thanks @seenu-k! - Initialise a git repository and commit the scaffold, and ask for the Android
    organization when it is not given.

    The scaffold runs flutter_launcher_icons and flutter_native_splash, which
    write generated-but-committed files across android/, web/ and assets/.
    Without a first commit there is no baseline, so the first branding change is
    indistinguishable from the files the scaffolder happened to produce. --no-git
    opts out, and a scaffold created inside an existing checkout is left alone
    rather than given a nested repository.

    --org is now asked for interactively when omitted and there is a terminal,
    because it becomes the Android applicationId — which Google Play makes
    permanent at first upload. Both the flag and the answer are validated as
    reverse domain notation, so com.example-games fails at scaffold time rather
    than at the first Gradle build. An empty value still falls back to
    com.example, and non-interactive use is unchanged.

Patch Changes

  • #19 993883f Thanks @seenu-k! - Use EigenInteractive as the product name throughout, matching the domain,
    the npm scope and the GitHub organization. Package descriptions, READMEs and
    the OpenAPI document title change; every identifier — @eigeninteractive/*,
    eigen_flutter, create-eigen-game, the Eigen-Signature header — is
    untouched.

@eigeninteractive/kernel@0.2.1

Patch Changes

  • #19 993883f Thanks @seenu-k! - Use EigenInteractive as the product name throughout, matching the domain,
    the npm scope and the GitHub organization. Package descriptions, READMEs and
    the OpenAPI document title change; every identifier — @eigeninteractive/*,
    eigen_flutter, create-eigen-game, the Eigen-Signature header — is
    untouched.
  • Updated dependencies [993883f]:
    • @eigeninteractive/rules@0.2.1

@eigeninteractive/rules@0.2.1

Patch Changes

  • #19 993883f Thanks @seenu-k! - Use EigenInteractive as the product name throughout, matching the domain,
    the npm scope and the GitHub organization. Package descriptions, READMEs and
    the OpenAPI document title change; every identifier — @eigeninteractive/*,
    eigen_flutter, create-eigen-game, the Eigen-Signature header — is
    untouched.

@eigeninteractive/server@0.2.1

Patch Changes

  • #19 993883f Thanks @seenu-k! - Use EigenInteractive as the product name throughout, matching the domain,
    the npm scope and the GitHub organization. Package descriptions, READMEs and
    the OpenAPI document title change; every identifier — @eigeninteractive/*,
    eigen_flutter, create-eigen-game, the Eigen-Signature header — is
    untouched.
  • Updated dependencies [993883f]:
    • @eigeninteractive/kernel@0.2.1
    • @eigeninteractive/rules@0.2.1

@eigeninteractive/testkit@0.2.1

Patch Changes

  • #19 993883f Thanks @seenu-k! - Use EigenInteractive as the product name throughout, matching the domain,
    the npm scope and the GitHub organization. Package descriptions, READMEs and
    the OpenAPI document title change; every identifier — @eigeninteractive/*,
    eigen_flutter, create-eigen-game, the Eigen-Signature header — is
    untouched.
  • Updated dependencies [993883f]:
    • @eigeninteractive/kernel@0.2.1
    • @eigeninteractive/rules@0.2.1

@seenu-k
seenu-k merged commit 428ecf5 into main Aug 6, 2026
3 checks passed
@seenu-k
seenu-k deleted the changeset-release/main branch August 6, 2026 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant