9月4日2026v0.7.1特点修复安全性24 更新复制链接
源头控制
自托管工作区可以拥有和管理多个 GitHub 个应用
Settings → Git now supports one-click GitHub.com manifest creation and manual GitHub/GitHub Enterprise Server registration, without an Openship Cloud or OAuth dependency. Private keys, client secrets, and webhook secrets are encrypted at rest; source-specific JWTs mint short-lived repository-scoped tokens against the correct API origin; GitHub sends verified lifecycle, push, and check webhooks directly to the instance. Owners can install an App on multiple accounts, rotate and verify credentials, select a default source, and safely delete one while project bindings move to an available replacement. Existing environment-backed Apps,
gh、个人令牌和每服务器 SSH 密钥仍然是兼容的后备 (#782)。GitHub 应用安装是端到端租户安全的
Install callbacks bind a durable one-shot nonce to the initiating user and workspace and verify the reported installation against the configured App before atomically persisting and reconciling it. The cloud callback survives API replicas/restarts, rejects removed workspace members, and cannot bind another tenant's caller-supplied installation id. Installation rows, token caches, project bindings, lifecycle webhooks, and reconnects are workspace-scoped; webhook arrival order never guesses a workspace from membership order (#759).
账户和团队
自托管组织邀请现在适用于全新用户
The claim page loads safely before sign-in, routes existing users back after login, offers token-bound account creation only when authorized, and exposes a copyable link beside each pending invitation. Invitation authorization, identity, credential, personal workspace, and membership now commit under one locked transaction, so cancellation races and failed signup cannot leave an unauthorized or partial account that blocks retry. Accept, reject, cancel, and signup mutations are serialized per invitation across API replicas. API access logs and Edge request telemetry also redact invitation bearer tokens and discard query strings before storage (#743).
DNS
服务自定义域使用显式 DNS 计划/应用工作流程
Saving a service route creates the same pending domain row as every other custom domain, then the shared records panel previews provider changes and applies them only when requested. The API documentation no longer promises a silent provider write that the product deliberately does not perform (#760).
服务器设置
远程服务器在 Edge 之前始终需要 Docker
Server readiness no longer inherits the control plane's
DEPLOY_MODE。检查每个托管目标的 Docker 和 Git,同时一个共享依赖规划器跨流式设置在基于容器的 Edge 之前插入并排序 Docker,SystemManager,以及直接组件安装防护(#767)。
构建
openship.json环境现已达到 Docker 个端到端文件构建Top-level project variables are recovered from the trusted source, encrypted into each deployment snapshot, and passed through the existing shared Docker build-argument resolver for first deploys, redeploys, webhooks, folder uploads, and explicit single-app mode. Native
services[].buildArgs添加每个图像的覆盖(null继承匹配的项目值),而服务env仍然仅运行时(#795)。BuildKit 从基于 Bun 的自托管安装中构建工作
Docker's reverse h2c session now bypasses Bun's incompatible
node:http升级路径,同时保留 dockerode 的 BuildKit 会话和注册表身份验证服务。使用语法指令、缓存挂载、heredocs 和其他仅限 BuildKit 的 Docker 文件功能进行本地 Compose 构建不再失败/session在 Docker 文件开始之前 (#745)。
更新
更新提示显示产品变更日志
Dashboard and desktop update surfaces now read the matching version from the tagged
CHANGELOG.md而不是重复 GitHub 发布正文。 The native update panel keeps advisory copy separate from a resizable, scrollable changelog, and all changelog actions open the version page onopenship.io而不是 GitHub (#752)。Successful deploys no longer re-advertise stale updates
Resolving the tracked branch head refreshes its upstream cache while a deployment is in progress, and successful deployments invalidate cached upstream state before the UI refreshes. The update banner and issues feed therefore compare the live deployment against a fresh upstream version instead of an older cached commit or image digest (#726).
目录应用程序
仅端口应用程序端点实际上已发布
An explicit port-only choice now persists a fixed all-interface Docker binding, including for catalog routes such as Supabase Kong that declare a served port but no Compose
ports条目。这使得向导的服务器 URL 和{{publicUrl:…}}替换真实。重试失败的草稿可以幂等地协调绑定,并且切换到域只会删除或恢复安装程序拥有的映射 (#770)。
邮件投递
邮件设置现在在宣布成功之前证明公共可达性
The final setup step combines the target's listener table with bounded off-box TCP checks for 25, 465, 587 and 993. The Health tab shows each port as a first-class signal, reusing a coalesced 60-second sweep, and test-email timeouts now identify provider firewalls/security groups/security lists/NSGs instead of blaming a stopped SMTP daemon when Postfix is demonstrably listening (#755).
邮件运行状况不再将假 IP IPv6 答案视为损坏的 DNS
Synthetic ULA AAAA responses from Clash/sing-box are now
unknown,匹配现有的 A 记录行为。与信息性 SpamAssassin 行和规范化分割字符串 DKIM 比较一起,这将关闭 #240 中报告的所有三个误报路径。中继网络邮件保持正确的分割传递路径
Webmail continues to submit to the local Postfix on 465, which alone owns relay scope, DKIM signing, and provider credentials. The identical timeout reported in #391 now receives the shared public-port diagnosis; provider relay credentials are never copied into the webmail container.
平台发件人现在可以自我修复,而不是卡在 SMTP 535 上
Cached
openship@<domain>仅当实时邮箱和转发行保持活动状态时,才会重复使用凭据。已删除的行会自动重新创建,并且已缓存的传输程序会轮换一次,并在身份验证拒绝时安全地重试 (#754)。平台邮箱受保护且可修复
Ordinary mailbox edit and delete operations reject the Openship-owned sender, while the Mailboxes tab exposes a dedicated password rotation/repair action that also works when the row is missing.
邮件配置适用于非 root SSH 用户
Relay maps and additional-domain DKIM configuration now elevate only root-owned host-file operations while Docker commands keep the login user's daemon context. Relay credentials are published atomically as
0600,并且没有 root 或无密码 sudo 的服务器会收到可操作的类型拒绝,除非邮件绑定挂载明确设置为该登录可写 (#756)。
部署取消
现在,在映像构建后取消会停止整个部署工作人员
Cancellation propagates through post-build preflight, human prompts, host-scoped provisioning locks, activation, health checks, routing, and both single-service and Compose pipelines. A durable database signal also wakes a worker running in another API process.
重新部署等待真正的工作人员完成
A cancelled row keeps its execution lease until cleanup has finished, while the dashboard shows the cancellation still stopping instead of offering a redeploy that cannot safely start. The API and CLI report success only after that lease is released; otherwise cancellation remains explicitly pending. Refreshing reattaches to that server-backed state (#757).
取消不能取代或拆除实时发布
The cancelled transition is conditional and atomic, and cleanup excludes containers carried forward from the active Compose release. If ownership cannot be proven, cleanup fails closed.
撰写对账
存储库编辑无法静默删除服务环境变量
Removing one or more environment keys from Compose now preserves the running service configuration and creates an explicit drift review, even when the operator never edited the imported baseline. Accepting that review remains the deliberate way to apply the deletion.
本地路径 Compose 项目自动实现其服务
project create --local-path ... --type services现在使用 API 的规范扫描器并立即保留检测到的行。部署和重新部署还通过现有的三向协调器重新读取相同的本地源,因此遗留的零行项目可以自我修复,而不是进入空的服务管道(#751)。Compose env 表达式只有一个同步/部署含义
Raw manual syncs preserve
${VAR}出处并在部署时从最终项目/服务环境解析它,而 Docker Compose 标准化 CLI 同步带有显式最终值标记,因此被转义$$永远不会扩展两次(#751)。终端故障刷新后仍然存在
The deployment lifecycle writes one deduplicated terminal error into the durable build log for every lifecycle failure path, including an empty Compose service set, instead of leaving the explanation only in
deployment.error_message(#751).
命令行界面
New projects and deploys can target a registered SSH server
project create --server <id>存储初始绑定,同时deploy --server <id>通过与仪表板相同的组织范围目标解析器和部署预检来驱动 Git 和文件夹上传。部署响应公开了一个稳定的 ID--watch,project get显示已解析的目标,失败的部署永远不会重新定位项目 (#763)。