chore: version packages - #379
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
github-actionsBotforce-pushed
the
changeset-release/master
branch
from
September 4, 2026 12:37
0328b86 to
9dc3dcfComparegithub-actionsBotforce-pushed
the
changeset-release/master
branch
from
September 4, 2026 13:22
9dc3dcf to
206bde0CompareArk0N
commented
Sep 4, 2026
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. |
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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'sgit checkoutandrebuild land on the host and survive container recreation, and the restart is
the server exiting —
restart: unless-stoppedrelaunches 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.Dockerfileordocker/docker-compose.yaml, or that adds keys todocker/.env.exampletheuser's
.envhas no value for, naming what changed and pointing atdocker/Start-Codeman.shon the host. It also refuses when the container'srestart 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 anew required setting would otherwise arrive as a silently blank variable.
Supporting changes:
python3/make/g++, sonpm installandnpm run buildcan run inside the container. This makes theimage larger; that is the cost of updating in place.
codeman-node-modulesandcodeman-distnamedvolumes so container-compiled native modules never land in the host checkout.
behaviour becomes a Dockerfile change the environment gate can detect.
docker/Start-Codeman.shrecords the Dockerfile and compose fingerprints thecontainer was created from, which is the baseline the gate compares against.
test/docker-compose-env-parity.test.tsfails when a composevariable has no
.env.exampleentry, or the reverse.Documented in
docs/docker-self-update.md.