← Журнал изменений

v0.6.9

This critical deployment-safety hotfix makes legacy Docker Compose ownership and routing fail closed. Existing unmanaged stacks can no longer be mistaken for an Openship deployment or silently duplicated, and an ordinary same-server redeploy cannot move a routed service onto a different host port.

1 выпуск
30 авг.2026v0.6.9Особенности7 обновлений

Развертывания и маршрутизация

  • Существующие стеки Compose никогда не принимаются неявно.

    Before changing containers or routes, a normal deployment checks the target for an untracked Docker Compose stack with the same project slug and service names. A collision now stops with FOREIGN_COMPOSE_STACK и сообщает оператору, что нужно импортировать/принять, удалить или переименовать его. Явно принятые контейнеры и контейнеры, уже отслеживаемые OpenShip, продолжают работать нормально.

  • Хост-порты одного и того же сервера остаются заблокированными при повторном развертывании.

    A routed service keeps its active host port on its current physical server. If that port cannot be reclaimed safely, deployment stops before routing changes instead of allocating a new port and leaving the public hostname pointed at the wrong workload. A real server migration may still allocate a new host port.

  • Предупреждения о дублирующихся контейнерах требуют подтверждения права собственности

    Normal projects no longer claim same-slug containers through Docker Compose labels alone. Native Openship labels, the canonical managed name, or the tracked container id establish ownership; Compose-label recovery remains available only for an explicit adoption.

Составьте сверку

  • Метаданные устаревшего парсера не создают ложного смещения репозитория.

    Adding environment/build-argument template provenance to an older service baseline is treated as a one-time metadata upgrade, not as a Compose edit. Real changes arriving with that metadata are still reported, and operator-edited live values remain intact while the baseline advances.

Мониторинг

  • «Проблемы» теперь являются рабочей областью «Мониторинг».

    The dashboard adds a Health view for every tracked project service, with fleet counts and state charts for healthy, unhealthy, crash-looping, down, and unknown workloads. Rows show the serving server and last observation, and link back to the service that owns the container.

  • Чтения работоспособности повторно используют существующий наблюдатель

    The page reads an in-memory snapshot produced by the grouped health sweep and Docker-event accelerator; it does not create a poller per container or perform Docker I/O on page refresh. Per-service monitoring can be disabled before the workload enters the watch, inspection, event, or notification path.

  • Обновления и повторные сканирования парка продолжаются в фоновом режиме

    Bulk component updates start together without holding a modal open, retain their durable sessions across navigation and refresh, and allow an operator to reattach to a specific log. The checker batch similarly exposes one shared progress session so multiple tabs cannot multiply Git, DNS, Docker, or version scans.

Upgrade priority: critical for legacy or externally created Compose > workloads. Fully tracked Openship deployments are not expected to hit the > collision path, but installations that previously deployed a same-slug stack > outside the current control-plane records should upgrade before redeploying it.