Skip to content

chore: version packages - #379

Closed
github-actions[bot] wants to merge 1 commit into
masterfrom
changeset-release/master
Closed

chore: version packages#379
github-actions[bot] wants to merge 1 commit into
masterfrom
changeset-release/master

Conversation

@github-actions

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 master, this PR will be updated.

Releases

aicodeman@1.25.0

Minor Changes

  • 66eb01b: Restore in-app self-update for the Docker Compose deployment.

    App Settings → Updates now works in the container, using the same updater,
    status file and progress UI as a bare-host install. The Compose file mounts the
    checkout it builds from at /opt/codeman, so an update's git checkout and
    rebuild land on the host and survive container recreation, and the restart is
    the server exiting — restart: unless-stopped relaunches it on the new build.

    An in-place container update applies application code only, since a restarted
    container reuses its existing image and configuration. The updater therefore
    refuses a release that changes docker/server.Dockerfile or
    docker/docker-compose.yaml, or that adds keys to docker/.env.example the
    user's .env has no value for, naming what changed and pointing at
    docker/Start-Codeman.sh on the host. It also refuses when the container's
    restart policy would not bring it back. The missing-key check matters most:
    Compose resolves an unset ${VAR} to the empty string and starts anyway, so a
    new required setting would otherwise arrive as a silently blank variable.

    Supporting changes:

    • The runtime image keeps devDependencies and gains python3/make/g++, so
      npm install and npm run build can run inside the container. This makes the
      image larger; that is the cost of updating in place.
    • Build artefacts live in codeman-node-modules and codeman-dist named
      volumes so container-compiled native modules never land in the host checkout.
    • The four global agent CLIs are pinned, so a release needing newer CLI
      behaviour becomes a Dockerfile change the environment gate can detect.
    • docker/Start-Codeman.sh records the Dockerfile and compose fingerprints the
      container was created from, which is the baseline the gate compares against.
    • New CI guard: test/docker-compose-env-parity.test.ts fails when a compose
      variable has no .env.example entry, or the reverse.

    Documented in docs/docker-self-update.md.

@github-actions
github-actionsBotforce-pushed the changeset-release/master branch from 0328b86 to 9dc3dcfCompareSeptember 4, 2026 12:37
@github-actions
github-actionsBotforce-pushed the changeset-release/master branch from 9dc3dcf to 206bde0CompareSeptember 4, 2026 13:22
@Ark0N

Ark0N commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Closing: 1.24.7 was released manually from master (commit 6f7add7), which already consumed this changeset. Master is a strict superset of this PR: package.json is at 1.24.7, .changeset/docker-self-update.md is gone, and CHANGELOG.md carries the #373 entry folded into one patch-level note together with #371 and the web-tab proxy hardening. Merging this would re-apply a stale, narrower changelog.

@Ark0NArk0N closed this Sep 4, 2026
Sign up for freeto 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

@Ark0N