← 变更日志

v0.6.8

Compose projects now deploy as the services they declare, with their build arguments and dynamic environment intact from import through rollback. Instance moves can go directly from one self-hosted installation to another without copying an encryption key, and the file workflow shows and filters what it will carry. This release also hardens custom-domain ownership, host-port allocation, Git credential boundaries, and edge recovery across Linux and macOS.

1 发布
8月25日2026v0.6.8特点安全性20 更新

实例转移

  • 直接移动实例,包括凭据

    The destination creates a single-use, ten-minute receive code for Replace or Merge mode; the source encrypts the selected database rows and plaintext credential bundle directly to that destination, and the destination immediately re-encrypts every transferred secret under its own instance key. Server SSH passwords and keys, environment variables, tokens, registry and DNS credentials, and backup credentials move without sharing either instance's BETTER_AUTH_SECRET 或管理传输密码(#656)。

  • 下载前查看并过滤导出内容

    Settings now shows the durable row count and a count beside each optional history group. Analytics, audit/notification activity, backup history, incident history, and migration history can be included independently; configuration, projects, services, servers, users, and credential records always stay in the portable core. Leaving the selection absent preserves the legacy full export (#656).

  • 无法导入半解锁的包含凭据的文件

    The offline export/import path remains available, but a file containing a sealed credential bundle now requires its passphrase before any database write. Invalid bundles are rejected before restore rather than importing rows whose secrets were silently scrubbed.

组成和环境

  • 撰写服务驱动自己的构建

    A project with composePath 被具体化到服务管道中,而不是落入一个通用 Docker 文件构建。地图和列表形式 build.args,纯粹的论点,和 ${...} 表达式按服务存储,并在 CLI 同步、协调、迁移采用、重新部署快照和回滚后继续存在。 Docker 套接字、SSH、批处理和云构建都使用相同的参数解析器,并且 OpenShip 的构建命令日志记录不打印参数值 (#689)。

  • 删除 Compose 构建参数会删除存储的参数

    An empty args 地图或已删除 args key 清除过时的值和插值来源,而在构建参数存在之前创建的快照在回滚期间保持非破坏性(#689)。

  • 不受支持的 Compose 构建在部署前失败

    Malformed arguments, repository-escaping or remote contexts, and build features Openship cannot reproduce no longer leave the old service shape running silently. A declared Compose project with no materialized rows is scanned once to bootstrap its topology, while an explicit single-app choice remains single-app.

  • 动态撰写环境在部署时解析

    Raw expressions such as postgresql://user:${POSTGRES_PASSWORD:?set it}@postgres:5432/app 根据最终项目、冻结发布、内联和服务范围层进行评估。嵌入式需求、直通键、默认值、嵌套表达式和转义美元保留了 Compose 语义;未解析的必需变量导致该服务因缺少名为 (#673) 的密钥而失败。

  • 手动服务变量是持久覆盖的

    The service Environment tab now owns service-scoped environment rows rather than rewriting the Compose-owned service.environment 对象。因此,UI 中添加的值在 Compose 重新解析和项目重新部署后仍然存在。保存未公开的秘密(包括重命名其密钥)会保留其现有的密文,而不是存储掩码或删除值。

部署和路由

  • 预构建的容器镜像可以作为版本进行跟踪

    A single-app project can resolve versions from GitHub Releases or an HTTPS version feed, optionally pin a version, and render that tag into a registry image template. Deploy and Update pull the application image directly on Docker or Cloud — no Git clone, Dockerfile build, or release archive — while drift detection compares deployed and upstream semver. Successful Docker releases freeze the immutable registry digest so rollback can reacquire the exact image after local retention expires; source changes apply atomically across environments and are available in both the dashboard Source tab and openship project release-image (#694).

  • 应用实际上意味着重新启动而不重建单个应用程序

    Docker and host-mode projects reuse the active deployment's retained artifact even though they have no service rows. Apply never fetches Git or silently turns into a rebuild; if the artifact is gone, it says to Redeploy instead (#674).

  • DNS 检查点涵盖 Docker 和每个 Compose 路由

    Pressing Deploy now shows records for single-app custom domains, service scalar routes, and multi-route Compose endpoints. Multiple hostnames appear together, www 与其顶点分组,远程部署预览使用所选服务器的公共地址而不是该实例的地址 (#663)。

  • 重新部署无法分离自定义域

    Deployment reconciliation preserves both pending and verified custom-domain rows and their live targets when a release omits them. A failed deployment rolls back only generated managed routes, never user-owned custom configuration, and concurrent hostname claims use database-authoritative ownership instead of letting the losing project route another project's domain (#675).

  • 停止的容器无法将旧主机名转换为另一个应用程序

    Loopback ports now have database-enforced, physical-target-wide ownership across organizations. Allocation reserves the port before Docker binds it, treats local and “This Server” as one namespace, and persists every routed Compose port through stopped and reconciling states. A stale vhost/TLS certificate can therefore never be repointed accidentally when a later deployment starts listening on the same number (#682, GHSA-284v-9jw3-jfhx).

  • 重试路由首先修复边缘

    When openship-edge 如果停止或丢失,重试路由会在接触虚拟主机之前对其进行协调和运行状况检查。不可恢复的边缘立即返回可操作的警告,而不是挂起直到路由请求超时(#693)。

  • 项目删除不再在裸露的 OpenResty 监听器上出现死锁

    Route cleanup validates the installed configuration and signals only the verified running master instead of starting a second nginx process on ports 80/443. Listener checks account for every socket owner, including mixed SO_REUSEPORT 侦听器,并且当无法证明所有权时会失败关闭。删除标志现在在查询字符串和 JSON 正文中一致工作; forceOrphan 在删除项目之前持久记录未完成的主机清理,以便垃圾收集器可以安全地重试(#700)。

主机和边缘

  • Docker 源获取遵循实际传输

    Preflight and the build pipeline now share one source-location plan. Local socket and TCP daemon builds prepare source on the API host, remote SSH Docker builds may clone on the target, and bare or cloud builds retain their own boundaries. A local server row therefore no longer asks a nonexistent remote clone path to use ambient Git credentials (#654).

  • macOS 边缘安装使用物理主机路径

    Bind sources are canonicalized on the machine that owns the Docker daemon, so /var 和 /etc 决心他们的 /private/... 在 Docker Desktop 或 OrbStack 发现目标之前。具有陈旧逻辑挂载的看起来健康的边缘被重新创建到相同的虚拟主机、证书、ACME 和静态数据目录上 (#692)。

安全性

  • 显式 GitHub CLI 配置目录是隔离边界

    Fallback token discovery reads exactly the hosts.yml 按 Linux、macOS 和 Windows 上的 GitHub CLI 优先级选择。如果 GH_CONFIG_DIR 或 XDG_CONFIG_HOME 设置但丢失或无令牌后,OpenShip 不再落入另一个用户的主目录并借用该凭据 (#687)。

OpenShip 邮件

  • 入站 SMTP 在 Postfix 的 chroot 内具有 DNS

    Every mail-engine boot now refreshes resolv.conf 以及在 Supervisor 启动之前持久 Postfix 假脱机内的支持 NSS 文件。如果无法安装解析器,引擎将无法关闭,而不是启动 SMTP 服务来拒绝每个合法发件人 450 Helo Host not found (#686).

仪表板

  • 项目环境无需刷新即可更新

    Creating an environment commits it to shared state immediately and reconciles the canonical list; deleting one removes it from every affected cache and navigates to the best surviving sibling. A failed follow-up read no longer makes a successful create look like it failed (#657).