← 变更日志

v0.6.6

Mail learns to receive, and third-party secrets get one home. Openship Mail now captures, filters and reads inbound messages, and an arriving message can raise a notification. Alongside it, a single org-scoped credential store replaces the one-off DNS token table and unlocks private image pulls on any host. The app catalog is installable end to end, the audit log moves out of Settings onto its own page, and uploads stop failing at 1 MB.

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

安全性

  • 作业写入是针对作业自己的目标服务器进行授权的

    Jobs are instance-wide, so the job:write 权限(检查组织成员资格)本身并不是对运行命令作业的服务器的权限。现在,编辑和删除作业会像创建和运行作业时那样执行相同的每目标服务器检查,并且拒绝与不存在的作业没有区别。对外报告;添加了回归测试。具有多个信任级别的自托管实例应升级; OpenShip Cloud 从未受到影响(作业 API localOnly).

凭证

  • 第三方秘密的一间商店

    A provider registry (container registries, Cloudflare, and room for what comes next) behind one table, with every secret sealed in a single enc1: 信封而不是每个字段的一列。凭据的提供者会对其进行验证 之前 它被存储,因此错误的令牌会在您粘贴的位置而不是部署需要它的位置被拒绝。

  • 私有镜像会拉到每台主机上

    Registry auth is resolved per image from that store (#581). On a remote host the config goes to a temporary DOCKER_CONFIG 目录(0700, 文件 0600) removed whether the pull succeeds or fails, so a pull never edits the operator's own ~/.docker/config.json。本地拉取仍然通过守护程序自己的凭据存储,这就是保留 Docker 桌面的原因 credsStore 工作。

  • DNS 凭据折叠到其中

    Existing Cloudflare tokens are re-wrapped at boot. A token that cannot be decrypted (a rotated BETTER_AUTH_SECRET)完全保留在原来的位置,并且仅在新行存在后才会删除旧行 - 移动过程中发生崩溃会留下重复的凭据,而绝不会为零。

  • Git 凭证有自己的选项卡

    Clone credentials were filed under API tokens, which is neither where you look for them nor somewhere a second Git provider could go. "API tokens" now means only that.

入站邮件

  • 邮箱可以读取

    Inbound capture, read and watch, so mail that arrives is stored and retrievable rather than merely delivered.

  • 入站过滤失败关闭

    Loop guards, a spam gate, and scope matching that drops a message it cannot confidently attribute instead of guessing an owner for it.

  • mail.inbound_received 是一个通知

    Inbound mail can drive a channel, in a mail group that appears only on self-hosted instances.

OpenShip 邮件

  • 邮箱创建在引擎中运行,而不是在主机上运行

    doveadm 和 chown 在主机上运行,但它们不存在,因此创建邮箱返回 500 (GH-562)。

  • 数据库引导失败声音很大

    The script had no set -e,因此失败的步骤仍然报告成功,并且使半配置的引擎看起来正常(GH-562)。

  • 邮件屏幕看起来像产品

    The channel picker is now the same component the notification and job screens use, with real brand marks in place of a native checkbox that renders in the browser's colours rather than the theme's, and the admin tabs drop the borders and status dots that matched no pattern here.

应用目录

  • 每个应用程序都会安装

    Each catalog app now ships a UI and a connection, rather than installing into something you couldn't open.

  • verified 表示上游发布

    The badge is reserved for bundles published upstream, so it stops implying a review it never represented. Neon is no longer marked verified (neond is a community control plane), and the experimental badge is off both Neon and PostHog.

  • Neon 在实际安装时间中幸存下来

    Its bootstrap assumed a readiness it never waited for.

迁移

  • 选择是根据身份而不是姓名来解析的

    The wizard sent names and the server matched on them (#584), so two containers sharing a name collapsed into one pick, and a name matching something outside the selection could be adopted. A selection now carries container ids, falling back to names only for a service that has none.

  • OpenShip自己的堆栈被排除,而不是拦截器

    The containers running Openship are skipped with the reason named, instead of the whole migration refusing to start.

  • 对虚拟主机扫描导入内容的两个修复

    Nginx's own default vhost is skipped rather than adopted as a site, and prefix-relative document roots resolve against their prefix.

边缘

  • 上传默认为 50 MB

    Nginx's built-in limit is 1 MB, and a project that never opened the proxy panel inherited it, so any real upload died with a 413 the app never saw. client_max_body_size 50m 现在发货于 http 范围在每个边缘配置中,这使得项目自身的价值在任何设置的地方获胜。在此之前安装的主机将就地修复,并且操作员自行调整的值永远不会被覆盖。

审核日志

  • 它自己的页面

    Nothing on it is a setting: you never change anything there, you read what already happened. It sat three clicks inside Settings, which is how a review surface goes unread.

  • 每个过滤器都在 URL 中

    Filters and pagination are query parameters, so a view can be linked, shared and reloaded.

  • 未编目事件已编目

    Events emitted without a taxonomy entry now have one.

修复

  • openship reset-admin-password 适用于 Compose 安装

    It authenticated with ~/.openship/internal-token,Compose 路径永远不会写入的文件:api 容器使用 INTERNAL_TOKEN 来自 ~/.openship/compose/.env。所以在撰写框中输入命令 铸造的 一个全新的随机令牌,发送并报告 Unauthorized — 锁定恢复命令在需要它的安装上无法使用。该盒子运行的令牌现在在一个地方解析,读者永远不会铸造,并且根拥有 .env this user can't open 这么说(使用 sudo 重新运行),而不是报告授权失败。同样的修复到达控制面板的“重置管理员密码”, openship doctor (其健康状况读数在每个 Compose 堆栈上都为空),以及一个裸盒的 :80/:443 takeover,它会查找 Compose 令牌,并在停止运营商的代理后跳过导入迁移的站点。

  • 密码重置使用 6 位代码

    Rather than an emailed link.

  • 取消的部署保留其原因

    The failure message was gated on failed 单独的,这会清除每个取消行的原因。但取消并不总是您的停止:引导扫描会因“服务器重新启动而中断”而取消,并且被取代的部分故障会记录原因。放弃原因后,安装向导只剩下通用的“安装失败”来打印一行,上面写着 cancelled.

  • 安装的结论及其原因一致

    The wizard decided "was this a cancel?" and "what do I show?" independently, so a stopped install could print "Install failed" underneath the heading "Install cancelled".

  • 仅当域行存在时才会出现验证

    The optimistic row fell back to the bare hostname as its id, and every guard downstream reads that id as proof the server row exists. So a hostname with no row yet rendered a live Verify button that 404'd, along with a DNS-records panel that couldn't load.

  • 缩写提交不是新提交

    POST /deployments 需要 commitSha 无论调用者发送什么(openship deploy --commit 1eeaf76、MCP 部署工具、CI 脚本),git 愉快地检查了一个缩写:正确的代码已发布,而该行记录了一个无法比较的名称。漂移检查将其与 40 个字符的分支 HEAD 进行了比较,由于双方都渲染了 7 个字符,因此项目页面宣传“新提交可用 1eeaf76 ……您已部署在 1eeaf76 上”——永久地,并且重新部署永远无法清除它。现在,当一个 sha 是另一个在 git 自己的缩写层的前缀时,两个 sha 会命名相同的提交,一个 ref 根本不是 sha(标签, HEAD)读起来是“无法分辨”而不是漂移,并且调用者的引用在任何存储或比较之前都会解析为完整的 sha - 这也打破了每服务提交检查 GitHub 拒绝短 sha 的情况,并且 webhook 已经部署了重复数据删除。