* fix(deploy): let webhooks and CLI accept reviewed Compose changes
Webhook and CLI deploys hit COMPOSE_REVIEW_REQUIRED with no way through the gate, and the refusal hid what changed. Accept the current Compose source explicitly per deploy (--accept-compose-changes, or acceptComposeChanges on the hook), and surface the added/changed/removed services in the CLI error and the webhook delivery record.
* test(contracts): include acceptComposeChanges in deployment schema flags
The Compose review gate added acceptComposeChanges to
CreateDeploymentSchema without updating the contract test that
enumerates the schema's public flags, so the contracts suite failed
on CI. Add the flag to the expected list.
* docs(cli): list --accept-compose-changes in the deploy reference
The new deploy flag was missing from the generated CLI reference,
so docs:check failed with a stale reference. Add the row in
declaration order.
* Retain explicit Compose approval through shared deployment admission
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* fix(build): scale the managed build-cache budget with the disk
The managed project-cache budget was min(5 GiB, 10% of the Docker
filesystem). A project whose BuildKit cache outgrew 5 GiB was evicted by
the post-build prune after every build, so every deploy started cold.
- buildCacheKeepBytes is now 20% of the Docker filesystem, so the budget
follows the disk in both directions: disks under 50 GiB also move from
10% to 20%. This also applies to managed Cloud workers, which share
the collector.
- Below the 20% free-space GC target the idle budget shrinks to what
still fits above it (never below the old min(5 GiB, 10%)), so idle
caches give space back before rollback artifacts and running apps.
BuildKit's own 20% minFreeSpace still bounds a running worker.
- pruneManagedBuildCaches defaults to that budget instead of 5 GiB.
- The daily sweep marks its call as automaticRetention, so managed caches
use the same budget; keepStorageBytes still bounds native Docker cache.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(servers): configurable build-cache budget per server
Adds an optional managed build-cache budget for remote deployment
servers, edited from a Build cache card on the server Overview tab and
through the existing server update API, CLI and MCP tool. Empty keeps the
automatic share of the Docker filesystem.
- servers.build_cache_budget_bytes (migration 0224), bounded 1 GiB to
64 TiB in the database and the API contract.
- Only remote deployment servers expose and accept it: the local row
builds through the host daemon's native cache and migration sources
never build, so updates there are refused; managed Cloud servers keep
rejecting every field except name. Changing it requires server admin,
since a large budget lets caches hold most of the disk.
- SSH Docker runtimes read the value through a new buildCacheBudgetBytes
connection option on every collection, so a change applies to the next
build without reconnecting. It sets the post-build prune budget,
BuildKit's maxUsedSpace and the daily sweep's managed budget, capped at
the filesystem minus the admission reserve and still reduced under
storage pressure; a failed read falls back to automatic.
- Updates are audited like gpuOverride and do not drop retained SSH
sessions.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: regenerate the MCP and CLI references for the build-cache budget
The server update tool description and the `server configure` help now
mention the build-cache budget, so the generated references changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(migration): frame streamed rsync progress updates
* fix(migration): preserve exact progress with rsync byte units
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
`openship api /api/projects/<id>` requested /api/api/... because the
client always prefixes /api; a leading /api segment is now stripped.
`project env set <id> KEY=VALUE` failed with "too many arguments"; the
pairs are now accepted next to --set. A 401 from a project command now
adds "Run `openship login` first.", as server and service commands do.
Fixes#1023