← Journal des modifications

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 version
30 août2026v0.6.9Caractéristiques7 mises à jour

Déploiements et routage

  • Les piles Compose existantes ne sont jamais adoptées implicitement

    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 et indique à l'opérateur de l'importer/l'adopter, de le supprimer ou de le renommer. Les conteneurs explicitement adoptés et les conteneurs déjà suivis par OpenShip continuent normalement.

  • Les ports hôtes du même serveur restent verrouillés lors des redéploiements

    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.

  • Les avertissements concernant les conteneurs en double nécessitent une preuve de propriété

    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.

Rédiger un rapprochement

  • Les métadonnées de l'analyseur existant ne créent pas de fausse dérive du référentiel

    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.

Surveillance

  • Les problèmes sont désormais l'espace de travail Surveillance.

    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.

  • Les lectures de santé réutilisent l'observateur existant

    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.

  • Les mises à jour et les nouvelles analyses de la flotte se poursuivent en arrière-plan

    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.