Skip to content

Release v0.3.57 — bump every version declaration to 0.3.57 #2918

Closed

Description

@how2how2how2-arch

What happens

The tree's eight version declarations read 0.3.56, and v0.3.56 is the newest tag — measured scripts/check-release-published.py v0.3.56: built green, published as Latest, 11 assets, not a draft, not a prerelease.

Two behaviour commits have landed on master since that tag:

commit what it changes
a9647932 the rules for talking to the host become the prompt's first section
b1216aa1 each store field's job is stated, and a shape change moves all of them

Neither has reached an installation. An upgrade follows published releases, never a branch, so until a release is cut at a tree whose declarations name the new version, both exist on master and nowhere else.

The tree is at a measured point to release from: master's tree is e5ce9fbbdfca, which is byte-identical to the landing tree check-merge-plan-suite.py measured green for #2917 before that PR merged (6453 passed, 38 skipped). So the merge landed exactly the tree that was measured, and the reading applies to master as it stands.

What the fix must satisfy

  • The eight declarations move together and agree: emrg/__init__.py, pyproject.toml, emrg/gui/package.json, emrg/gui/package-lock.json, uv.lock, packaging/build-runtime.sh, packaging/make-installer.sh, packaging/make-run-installer.sh.
  • scripts/bump-version.py --check reports no drift across them, and tests/test_version_sync.py passes.
  • Nothing else moves. A version bump carries no behaviour change, so the diff is those eight declarations and no source file.
  • The release itself is a separate step. The tag, the four-platform build and the publication check are taken only after this lands, because the tag is the only trigger of build-release.yml and a tag on a tree whose declarations disagree is not a release.

Activity

  1. how2how2how2-arch commented on Nov 16, 2026

    @how2how2how2-arch
    CollaboratorAuthor

    Handled by #2919

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions