← 变更日志

v0.4.0

A security fix for the edge, migrations that behave like a native repo project, and a batch of routing/reliability fixes.

1 发布
7月27日2026v0.4.0特点修复安全性8 更新

安全性

  • 未路由的 HTTPS 主机会被拒绝,不会交叉服务

    The edge now owns a 443 default server that refuses any hostname it doesn't route (one you removed, never added, or merely pointed at the box's IP). Before this, such a request fell through to the first-loaded vhost and was served 另一个应用程序的证书和后端。在下一次部署时自动应用,无论是裸露边缘还是容器化边缘。重要 - 请参阅应用内建议。

迁移

  • 迁移的项目现在是本机回购项目

    A migrated compose stack redeploys like any repo project: it reclones and rebuilds build: 服务 并拉 image: 的,而不是在冻结的构建标签上失败(404 no such image)。仅重用运行图像 一次,在切换时。

  • 整个组合就是部署计划

    The migrate screen lists every repo compose service, not just running containers, so a service with no container (e.g. redis或未启动的应用程序)像其他应用程序一样构建/拉取和路由,其环境和路由可在卡上编辑。

  • 重用的数据库保持可达性

    A reused container is joined to the new project's network under its service-name alias, so a freshly-built app resolves postgres:5432 从名称上看,与本机部署完全相同。

  • 迁移的服务报告其实际运行的容器

    Service state is read live from the host and matched by identity (label → openship-<slug>-<svc> 名称 → 跟踪 id → 组成标签),因此采用了容器 OpenShip 到位 (它的 docker 标签仍然命名以前的项目)在提供流量时不再显示“已停止”。现在,每次运行的日志都以每个服务的容器、状态和匹配结束。

修复

  • 永远不会从数据库猜测服务状态

    Start/Stop/Restart, logs, terminal, backup/restore and volume sizes resolve the container against the host first, so a redeploy that replaced it no longer leaves them failing with no such container — 或者,在开始时启动 重复的 正在运行的容器旁边。崩溃循环容器现在读取 正在重启 instead of a green "Running", and an unreachable host reads 未知 而不是回显上次部署状态。

  • 删除路线绝不会错误地要求 OpenShip Cloud

    The free-domain gate classifies by hostname, so removing a custom-domain route (or any route) is no longer blocked by an unrelated free subdomain still in the set.

  • 删除服务无法挂起

    Runtime teardown is time-bounded, so a slow or unreachable server no longer strands the delete before the record is removed.