7月31日2026v0.5.0特点修复25 更新复制链接
回滚
回滚每个项目的任何版本
The Rollback action used to be greyed out on projects using the default settings, because nothing marked their releases as restorable. It's now available on every successful release, and it is a single action: Openship reuses the release's retained image when it's still on the server (seconds, no rebuild) and rebuilds that release's commit when it isn't. It can no longer dead-end — the "Redeploy this commit" fallback button is gone because the one action already covers it, and the confirmation tells you which of the two you're about to get.
恢复后的版本已完成
A rollback now runs the same deploy pipeline a normal deploy does, replaying that release's own frozen configuration and environment variables. Previously it hand-assembled a bare container, which meant a "successful" rollback could come back with no environment variables, no published port (a 502 behind your domain) and its volumes detached. Restores now get the health check, the crash-loop watch, routing, logs and a build log of their own, exactly like any other deploy.
每个服务的 Compose 堆栈回滚
Only services whose image is missing are rebuilt; a service the deploy never touched keeps running on the image it already has, so rolling back your app code doesn't bounce your database.
静态站点回滚其文件
A static release's artifact is its built files on disk, not an image, so restoring one copies that version's files back into place (hard-linked, so it costs almost no extra disk) and re-points the edge at them. No image, no rebuild. A static rollback previously tried — and failed — to restart a directory as if it were a process.
恢复永远不会破坏您所在的版本
A restore reuses its source release's image, so two releases can share one. Retention now knows that and will not delete an image another retained release still needs.
回滚历史记录将自身大小调整到磁盘
How many releases stay restorable is now measured from free space on the deploy host and your project's real image size (a quarter of what's free, between 2 and 20 releases), instead of a fixed 5. You can still pin an exact number; clearing the field returns it to automatic.
设置移至备份旁边
Rollback retention now lives in the project's Backup tab, and in the deploy wizard's target panel where you pick the server, with the measured snapshot size and free disk shown inline. Pinning a release to keep it restorable indefinitely is unchanged.
在您仍在选择服务器时设置保留
The wizard's rollback controls are editable on a first deploy too, and the choice is applied when the project is created. They used to render read-only until the project existed, which was the one moment you were actually looking at them. The card also names what a retained version 是 在您的项目中 - 为静态站点构建文件,否则为图像 - 而不是以任何方式谈论图像。
向导的高级面板显示其中的内容
It listed only the build location while hiding the rollback window and clone location; it now names each section it contains. The summary chips next to the target (Static, Sandboxed, tier) lost their coloured pill backgrounds and read as plain text, with the one that matters — an unsandboxed "direct on host" runtime — still called out in colour.
翻转保留设置适用于现有版本
It used to be frozen onto each deployment as it was created, so turning on instant rollback did nothing for anything already deployed.
重建回滚时发现的修复
旧版本根本无法部署或恢复
A release whose configuration snapshot predated the "production paths" setting crashed the deploy pipeline outright. This affected plain redeploys too, not just rollback.
不再因缺少构建设置而拒绝恢复
A release that reuses an existing image needs no install or start command, but pre-deploy checks demanded them. Adding a required setting would otherwise have made every older release un-restorable.
仅包含注册表映像的项目可以再次部署
A stack adopted from a Docker migration has no git repository and needs none, but deploys were refused for not having one.
Compose 部署记录哪个服务运行哪个镜像
Six of the nine places that write per-service deployment records left the service name blank, so a later rollback couldn't tell services apart and rebuilt the whole stack.
清除的回滚历史字段不再意味着“不保留任何内容”
An empty value now falls back to the default instead of purging every restorable release.
可以访问 Docker 桌面之外的 Docker
Local deploys honor
DOCKER_HOST(和显式套接字路径)而不是假设/var/run/docker.sock,因此 Colima、Rancher Desktop、Podman 和 rootless Docker 可以工作。
升级说明:此版本删除了未使用的 artifact_retained_at 每个服务部署表中的列。没有人读或写它。
MCP
引导部署流程
The MCP server now ships a prompt catalog (
deploy-from-git,deploy-a-folder,install-catalog-app,以及方向概述),因此 AI 客户端遵循正确的工具序列,而不是从平面列表对其进行逆向工程。它的编写工具现在端到端地携带类型化的请求主体(项目、部署、域、网络钩子、通知、连接、应用程序),并且每个提示都指向github.com/oblien/openship/issues当客户遇到平台错误时。范围令牌列出了正确的工具
A token granted a single GitHub repo (or the "create your own projects" scope) now correctly advertises the tools it can actually call. Previously the per-repo GitHub tools and the project create/list tools were filtered out of
tools/list,因此作用域令牌没有任何作用。
自定义域
www是它自己的域,而不是您的域的附件"Include www" always created a second hostname, but the pieces around it still treated the pair as one thing. Renewing SSL for a domain issued the
www同一操作中的证书,不受保护:awww尚未指向服务器但失败 之后 顶点已经成功,但据报告顶点已损坏。在打开开关的情况下添加域也只会显示顶点的 DNS 记录,因此www从未解决,其证书永远无法颁发,并且每次部署都会重试已设置为失败的主机名。现在,两个主机名都有自己的 DNS 记录、自己的验证按钮、自己的证书以及自己的失败。将一个域重定向到另一个域
Any domain can now answer a 301 (or 302) to another domain of the same project, set on the domain's card.
www默认使用它(www.example.com→example.com),方向由您决定翻转或关闭。旧域到新域的移动工作方式相同。路径和查询字符串被保留,重定向主机仍然获得自己的证书,并且项目外部的目标(或将循环的重定向)被拒绝。验证失败时保留日志
The verify modal streamed certbot's output and then, on any failure, replaced the whole console with one line: "the connection closed before the operation reported a result — check the domain's status." The actual reason was discarded. The log now stays on screen in every outcome, with Copy log and Try again next to it. And if the connection really does drop, Openship reads the domain's state back and tells you what happened instead of asking you to go and look.
完成的运行停止报告自身失败
A keep-alive ping could race the final event of any live-log stream (verify, edge setup, deploys) and win, so the browser never received the result of an operation the server had already completed. Stream writes are serialized now, and a result that has arrived can no longer be overwritten by the connection closing behind it.
Two domains on one server no longer fight over certificates
Certificate issuance is serialized per server, not just per hostname.
www使两个待处理域成为正常情况,并且手动验证可能会与同级域上的后台重试发生冲突:两者都运行 certbot,都需要相同的质询端口,其中一个因看起来像 DNS 问题的错误而死亡。A记录显示你的服务器IP
On a self-hosted install the pre-deploy DNS panel now fills the A record's value with the server's public address (detected once when the server is registered) instead of leaving it blank.
正确的自托管 DNS 指导
The panel no longer tells you to add a TXT record on a self-hosted box; there isn't one — HTTPS is issued automatically on the first deploy. The DNS modal is also lighter and on-theme, and the "Include www" switch now sits below the domain field so it no longer shifts the input as you type.