变更日志

有什么新消息

功能、修复和改进已在 OpenShip 中发布。

31 发布
11月18日2026v1.0.1特点修复13 更新

Recommended update for self-hosted startup, application image updates, and private GitHub repository access. This patch also fixes postmaster password rotation metadata and preserves referral attribution through Cloud deploy links.

Deployments and connections

  • Application updates

    Accept requests with an empty body when the action takes no options. Continue validating malformed JSON and required payloads (#1817).

  • Container image refresh

    Pull the current image when refreshing a mutable tag, and keep verified local images available for redeploys. Report failed refreshes before replacing a running service (#1816, #1819).

  • Registry credential checks

    Record confirmed login rejections and preserve the previous credential status when the registry response is inconclusive (#1816, #1819).

  • Private GitHub repositories

    Restore the connected-server token fallback for authorized self-hosted repository reads on GitHub.com. A local server without credentials no longer prevents selecting an eligible connected server (#1821, #1822).

  • Custom PHP base images

    Run build-time dependency and setup steps as root when the base image defaults to a non-root user. Keep the app running as www-data (#1810).

  • Swarm network setup

    Wait for Docker to allocate a new overlay network before checking its driver and encryption settings.

CLI and mail

  • macOS service reinstall

    Wait for launchd to unload the previous service and verify the replacement is running before reporting success (#1808).

  • CLI shutdown during startup

    Stop the API process when the foreground supervisor receives a stop signal, releasing the port and local database lock (#1809).

  • Postmaster password rotation

    Record the password change timestamp together with the new hash when rotating through the CLI or API (#1825).

Cloud and website

  • Cloud deploy referrals

    Retain the referral code through the deploy link and Cloud plan selection (#1806).

  • Social previews

    Use page-specific share cards across the website and documentation (#1824).

升级注意事项

  • Component updates

    Update the API, dashboard, Desktop and CLI for your installation. This patch adds no control-plane database migrations.

  • Image refreshes

    Use Refresh images when you want a new image for a mutable tag. A normal redeploy can reuse the local image.

11月16日2026v1.0.0特点安全性42 更新

OpenShip 1.0 brings a refreshed dashboard, edge maintenance and custom pages, deploy links, and scheduled mail workflows. Includes every change since 0.9.12, with more reliable builds, imports, billing and recovery.

Recommended update: administrators should update all OpenShip components. This release closes an authorization flaw that allowed ordinary organization members to invoke administrative operations, including host command execution.

Security and access

  • Administrative authorization

    Require administrative authority across HTTP, SDK, native and MCP access. Scoped tokens remain bounded by their owner's current organization role, including after demotion. Preserve explicitly delegated, resource-scoped administration (#1783, #1784).

  • Hostname sign-in

    Choose a sign-in page or the browser's native authentication prompt for self-hosted hostnames. Customize sign-in HTML and session duration, revoke sessions, and see enabled protection directly on domain cards.

  • Actions tracing

    Update the Actions worker to OpenTelemetry 1.47.0, fixing bypassed attribute-length limits in its tracing dependency.

  • Release build isolation

    Keep generated local mail credentials and runtime caches out of image build contexts. Bundle the shared assistant client and its dependency patch so release builds do not depend on a sibling checkout or baked development URLs.

  • Website image verification

    Include the website's client-message generator in its Docker build, and verify the production website image and its public pages before release.

Edge pages and routing

  • Edge maintenance

    Serve maintenance HTML directly from the edge while the application keeps running. Restore normal routing when maintenance is disabled.

  • Custom error pages

    Upload HTML pages and assign error statuses, with server defaults and project or hostname overrides. Customize unmatched-host and direct-IP pages.

  • Authentication header limits

    Accept larger authentication response headers and returning cookies at the edge, with bounded defaults and preserved custom buffer settings (#1763).

  • Domains & Routes

    Organize Domains & Routes into routing, access, proxy, and page controls, with inline protection settings, HTML previews, and visible loading and retry states.

  • CLI domain targeting

    Target the correct project service and port when adding domains from the CLI. Keep primary domains, aliases and www redirects consistent when editing routes.

Deployments, imports and recovery

  • Shareable deploy links

    Add shareable deploy links and openship launch, carrying the selected repository and deployment intent through sign-in and installation.

  • Independent service copies

    Copy selected services to the same server or another server as independent projects. Validate dependencies and port bindings, preserve separate volumes, and improve restoration and rollback if a transfer fails. Keep application instance scaling distinct from independent copies.

  • Compose change review

    Review Compose changes in a shared before/after dialog and apply the exact reviewed revision without repeating setup. Preserve deployment options and saved overrides, mask credentials, and require a new review if source changes (#1796).

  • Private registry guidance

    Explain private-image pull failures with the affected image and a direct link to registry connections. Preserve public-image recovery and distinguish registry credentials from GitHub repository access (#1798).

  • Compose environment values

    Reveal and hide service environment values through the shared Compose editor while retaining the existing permission checks (#1771).

  • Multi-repository Railway imports

    Import Railway projects with multiple repositories as native services and project connections, preserving source ownership and private service wiring.

  • Compose web ports

    Show container ports declared with Compose expose, explain how to publish a TCP port for a web domain, and handle protocol suffixes and port ranges.

  • Folder deployments

    Improve folder deployment names, scan errors and streamed uploads. Resolve template placeholders consistently in service ports, and explain recovery when duplicate containers block deployment.

  • BuildKit cache retention

    Retain warm BuildKit caches and reduce remote cleanup overhead without dropping build ownership, cancellation or capacity checks.

  • Empty-volume backups

    Back up verified empty Docker volumes and bind directories alongside populated sources. Refuse missing sources and preserve errors for unavailable storage.

  • Redis Sentinel readiness

    Verify every Redis Sentinel has discovered the writable primary, its replicas and the full voting group before reporting replicated databases ready.

  • Controller relocation

    Fence event-stream admission while relocating the controller, restore access when it resumes, and link server preparation to its deployment progress.

  • Mail engine updates

    Preserve the mail host's configured ignored IP addresses when updating its engine.

Mail and agents

  • Scheduled mail and snoozing

    Schedule messages, cancel queued mail with Undo Send, and snooze conversations. Recover interrupted or temporarily failed wake-ups, including messages moved or deleted before their wake-up time.

  • Mailbox agents and MCP

    Connect mailbox-scoped agents and MCP clients with encrypted state, isolated runtimes, scoped permissions and explicit approval for sending mail.

  • Assistant workspace

    Improve the agent workspace, shared conversation rendering, connection setup, and empty and error states. Add the OpenShip plugin directory submission metadata.

Cloud, billing and CLI

  • Oblien provider API

    Move the Oblien integration to SDK 3.2.0 and the provider's native versioned VM API. Preserve saved VM identities, customer metadata and purchased offers; validate scoped credentials against the selected VM.

  • Cloud checkout recovery

    Recover unfinished Cloud purchases instead of creating duplicate unpaid spaces. Open checkout after its payment URL is ready and retain a fallback action.

  • Renewals and pricing

    Keep billing accessible during pending renewals and show payment warnings in Plans & billing. Align monthly and yearly pricing across the website and dashboard.

  • Cloud setup recovery

    Recover repeated signup attempts during Cloud linking and improve first-admin recovery and Compose managed-edge setup.

  • CLI install and sign-in

    Keep the installed service's existing ports when openship up runs again. Support CLI login through public instance URLs and use Node.js for the container-to-host connectivity probe.

  • Cloud update notices

    Limit the managed Cloud update banner to verified workload-security notices.

Dashboard and website

  • Dashboard refresh

    Refresh billing, monitoring, jobs, backups, connections, server and agent screens with shared illustrations, compact controls and theme-aware surfaces.

  • Service controls

    Improve service inspectors and copy/scale flows, put actions before runtime details, and replace native disclosure markers with shared icon controls.

  • Avatar and project icons

    Add avatar and project icon URL settings, with inline editing, previews and reset.

  • Marketing site and docs

    Refresh landing, Cloud, mail, download, migration and app-catalog pages; improve Arabic headlines, language navigation and documentation navigation.

  • Comparisons and Cloud information

    Expand product comparisons, feature pages and search discovery, and publish Cloud SLA, support and privacy information.

升级注意事项

  • Component updates

    Update the API and all its replicas, dashboard, Desktop, CLI and mail components together. This release includes database migrations; retain a current instance and database backup before updating.

  • Organization roles

    Ordinary organization members no longer have implicit administrative access. Review membership roles and scoped grants for integrations that perform admin actions.

  • Oblien provider rollout

    Cloud operators must coordinate this release with the matching Oblien /v1 API, database, gateway and scoped-credential rollout. Review old unversioned OBLIEN_API_URL and gateway overrides, and verify existing-VM access before directing customers to the upgraded provider.

  • Edge requirements

    Maintenance, custom edge pages and hostname protection require the updated self-hosted edge. These controls do not protect direct application ports or hostnames outside their configured scope.

  • Service copies and database scaling

    Independent service copies are separate deployments. Managed database replicas and failover use their existing database scaling flows.

11月12日2026v0.9.12特点修复安全性46 更新

Critical update for build-secret protection, database upgrade repairs and backup/restore reliability. Includes all changes since 0.9.11, with reviewed source-image update PRs, platform imports, mail improvements and a translated website.

构建安全

  • 通过临时 BuildKit 密钥传递生成的 Docker 构建环境,而不是在 Docker 文件或映像历史记录中嵌入值。屏蔽流日志、错误摘要和故障通知中的配置值,包括拆分和多行输出。保留云工作线程限制、并行服务器构建以及取消后的清理。
  • Attribute REST audit events to the personal access token used, and audit token reads through the existing authorization path.
  • Preserve private edge-vhost permissions and verify access with unprivileged workers. Keep tunnel hostnames out of unsupported password-protection flows.

Runtime and source updates

  • 将缺少部署摘要的映像服务保持为未验证状态。通过现有部署运行时检查正在运行的映像,以检测移动的标签,具有有限读取且无部署行写入。显示不可用的更新状态,没有更新标志。
  • Propose Dockerfile and Compose image changes through reviewed GitHub pull requests. Check repository access first and guide users to reconnect or update their GitHub installation when the required permissions are missing.
  • Apply security fixes to managed runtime versions instead of repeatedly refreshing an unchanged image. Distinguish a runtime that is absent from a failed probe.

Deployments and infrastructure

  • Allow webhook and CLI deployments to approve reviewed Compose source changes through the shared approval flow.
  • Keep branch and Compose-path controls available after an unsuccessful first scan, reject blank required build commands, and offer Static Site for folder uploads.
  • Keep token-authenticated repository clones on HTTPS even when a server's global Git configuration rewrites GitHub URLs to SSH.
  • Recover orphaned builds through shared worker ownership, preserve application runtime/log access when adding services, and scope shared image-export paths.
  • Scale managed build-cache budgets with available disk and expose server cache settings. Improve local image exports without sharing another build's output.
  • Let edge upgrades finish safely after an SSH disconnect. Preserve owned mounts in imported Cloud workloads and explain host paths that cannot be imported safely.
  • Support hosted Jobs on Manage-connected SSH servers. Match BullMQ repeatable jobs by name so changing a cron schedule removes the previous schedule.
  • Accept bounded YAML aliases in imported GitHub workflows, show the latest run for every workflow, and avoid duplicate GitHub-owned workflow webhook payloads.
  • Recover failed installed-CLI updates and verify release installation and updates on disposable VPS instances before publishing images and packages.

域名

  • Configure static HTML, JSON or text responses on a domain through its normal route editor, including maintenance and verification responses without an app container.
  • 避免在注册期间重写未更改的边缘路由文件和重复远程读取。保留确切的文件内容和权限,同时保留路由验证、重新加载、证书激活和事务回滚。
  • DigitalOcean DNS

    Connect a DigitalOcean token in Settings → Connections to preview and apply a custom domain's records and issue DNS-verified HTTPS automatically, as with Cloudflare. Each record OpenShip creates is paired with an _openship-owner TXT 标记,因此删除域只会删除 OpenShip 自己的记录。

Imports, backups and database upgrades

  • Improve platform imports, including Railway and Vercel setup, source and destination review, progress reporting and cancellation.
  • Keep migration environment fields visible while entering missing secrets, with a plain section heading instead of a nested disclosure that collapses during editing.
  • Preserve source project boundaries during platform imports

    One project contains its native services, private DNS, encrypted service environments and separate volumes. Keep service environment values scoped correctly during source builds too.

  • Carry imported custom domains and aliases through the existing migration routing flow, pending normal verification. Show DNS cutover guidance and replacement notices for Railway and Vercel URLs in review and saved migration progress.
  • Restore portable instance exports with their server credentials and workspace ownership. Normalize restored data for the destination schema and keep the instance import and server selection views consistent.
  • Repair missing workspace and security-advisory fields on upgrades, including databases whose earlier migrations were already marked as applied.
  • Serialize backup execution per destination to prevent connection exhaustion. Recover orphaned Cloud backup activities through the existing ownership checks.
  • Complete local mail backups and portable restores through the shared backup orchestration, including target-server mail configuration and real mail round trips.
  • Prevent browser autofill of backup destination credentials and keep destination menus visible outside their cards.

邮件

  • Preserve mail logs and Fail2ban ban history across engine updates, and remove Dovecot's stale PID file before startup.
  • List all signed-in mailboxes and keep account menus usable when they overflow.
  • Correct webmail message colors in light/dark themes and when printing, and refresh security dependencies.
  • Protect support intake and add mailbox sender blocking.

Assistants

  • Reuse managed agent setup for custom API connections and report the actual runtime setup state.
  • Find agent CLIs installed outside the macOS GUI PATH, restore public BuildKit pulls, and correct scoped Claude startup.
  • Allow reviewed repository patches to delete regular files through the existing review and validation flow.
  • Add OpenShip plugins for Codex and Claude Code.

Dashboard, billing and website

  • Keep the shared destination dropdown available with one server or Cloud plan, with Add server in its menu across deployment and migration flows.
  • Refresh deployment state after navigation and browser resume. Unify project settings and shared environment controls with the existing service views.
  • Keep plan overview, usage and payments together under Plans & billing, align Cloud plan presentation across the website and dashboard, and retain payment recovery for expired renewals.
  • Improve deployment, verification and cancellation emails, and standardize the Referral experience.
  • Translate website content into the existing supported languages, with localized URLs, navigation and product screenshots. Correct Arabic layout and preserve English framework names. Documentation remains in English.
  • Add migration guidance for teams moving an existing app, group website navigation, and provide a direct Start on Cloud action.
  • Use the BytesMap SDK for unified Cloud telemetry and remove PostHog.

升级注意事项

  • Update the API (including all replicas), dashboard and Desktop app together. This release includes control-plane database migrations

    Keep a current instance/database backup before upgrading.

  • Build-secret protection applies to new builds. Rebuild older application images to use the updated build flow

    Upgrading does not rewrite existing images.

  • Dockerfile and Compose image pins remain controlled by the repository. Review and merge a source-update PR when the fix requires a source change, then deploy that revision. Refreshing an unchanged pin does not change its runtime version.
  • Update the mail engine as well to receive mail startup, log persistence and restore fixes.
11月6日2026v0.9.11特点修复安全性31 更新

建议更新桌面登录恢复、助手连接、存储库扫描和部署可靠性。包括自 0.9.10 以来合并到 main 中的所有更改,包括邮件管理改进和更清晰的运行时安全更新。

助手和桌面

  • 在托管实例上登录 Codex

    Use device-code sign-in on Cloud, VPS and remote assistant hosts, while keeping browser sign-in on the local Desktop host. Explain the available method in AI connections, use the shared ChatGPT mark, and update the Mindwire runtime and SDK to 0.1.61.

  • 桌面帐户恢复

    Preserve verified sign-ins during refresh and startup, and remember the administrator selected through Desktop's authenticated sign-in. Missing or stale Local User cookies recover to that saved identity without selecting an unrelated user's session or changing account permissions.

  • 克劳德·代码关于 macOS

    Make the system keychain available inside the isolated assistant home so sign-in can complete.

  • 调查和提问

    Start an explicitly requested deployment investigation when the assistant is ready. Answer agent questions above the composer while retaining drafts, separate answer state and retry behavior. Keep expanded questions focused and the latest-messages control readable.

  • 助理工作区设置

    Keep connection setup inline and use the shared drawer for agents and automations. Preserve unfinished configuration and the underlying chat, recover access to changed specialists, and refresh activation reviews when saved settings change.

部署、路由和安全

  • 撰写命令更新

    Resolve authored command expressions against the current service environment during deployment and Apply environment. Preserve referenced file defaults and explicit command edits without exposing internal source metadata as environment values.

  • 环境应用失败

    Show structured startup, health, restart and OOM evidence while retaining the existing replacement and rollback flow. Keep credentials and unrestricted provider error text out of responses, monitoring, notification failures and backup diagnostics.

  • 静态环境变化

    Offer Rebuild and redeploy for static sites and single-app Cloud deployments whose variables cannot be applied through a runtime-only refresh. Open the new build's progress and retain retry controls.

  • 静态 404 行为

    Add an explicit SPA fallback setting to shared routing controls, the API and openship.json。默认启用 SPA 回退;禁用它会返回真实的 404 响应并使用 404.html 当可用时。

  • 组成边缘库存

    Inspect loopback upstream ports through the edge's own connection, including mounted Docker sockets without host SSH. Quarantine existing routes before allocating ports and continue refusing unreadable or ambiguous inventory.

  • 私有存储库扫描

    Allow the only eligible connected server's stored token when an organization has no local server. Ask for an explicit server when several qualify, retain the choice across scan retries, and keep public reads anonymous when no credential is needed.

  • 停放的 Docker 个进口商品

    Offer an explicit finish-without-restart decision for imports awaiting cutover. Keep originals untouched and provide actionable guidance when a parked migration prevents project deletion.

  • 云主机边界

    Enforce shared safeguards against local workload execution on the SaaS API host while retaining authorized managed-server and SSH execution. Keep command availability probes separate from execution.

  • 有条件的安全审查

    Distinguish PHP's conditional session upload-progress review from confirmed runtime vulnerabilities. Share advisory guidance while retaining each service's confidence, progress and actions; offer saved configuration and an editable, scoped Fix with AI request without automatic submission. High and Critical warnings retain their priority.

  • 数据库删除冲突

    Reread controller state after explicit Kubernetes version conflicts during database cleanup. Retain object identity, ownership, generation and operation fences while tolerating status-only updates.

邮件和应用程序目录

  • Fail2ban 管理

    On self-hosted mail installations, inspect jail counters and banned addresses from Health, the API, SDK and MCP. Review the exact address and jail before banning or unbanning; stale observations disable changes until refreshed.

  • 直接别名发件人

    Allow active direct aliases to authorize their owning mailbox consistently across mail sender checks. Disabled aliases, external forwards, catch-alls and alias chains grant no sender identity. Clarify the distinction between incoming forwarding and direct-alias sending in the UI.

  • 应用程序写入设置

    Deduplicate generated credential writes and verify owner bootstrap before reporting success. Exclude the optional Geo service while its upstream PHP runtime remains affected, and document the geolocation limitation.

  • 安全刷新验证

    Reject unchanged-image refreshes, track manual remediation through deployment and runtime inspection, and show progress or a verified failure instead of silently repeating an ineffective update. Validate Compose hostname availability against scoped Cloud ownership receipts.

  • Supabase 图片

    Update the catalog's Storage, Meta and Studio image pins for the bundled Node.js/Brotli security fixes.

  • RabbitMQ 准备情况

    Run probes as the image's RabbitMQ user and wait for the management listener, avoiding the startup Erlang-cookie ownership race.

仪表板、计费和文档

  • 主题还原

    Render the saved base theme and background on the server through a validated cookie. Preserve custom theme caching, System mode and unsaved previews without flashing Light on refresh.

  • 结帐退货

    Retain the purchasing organization, server and payment receipt through hosted checkout and authorized organization switching. Keep checkout retries tied to their original payment contract.

  • 网关故障

    Request JSON from the API and explain upstream proxy errors with recovery guidance instead of showing an opaque status or HTML page.

  • 首次部署分析

    Wait for an active deployment before reading traffic for a reserved domain. Start reads when deployment activates and retain existing traffic during redeploys; genuine provider failures remain errors.

  • 快速入门措辞

    Remove an abrupt line break in the setup description.

升级注意事项

  • 一起更新 API(包括所有副本)、仪表板和桌面应用程序。此补丁没有添加新的控制平面数据库迁移。
  • 如果较旧的桌面安装已仅显示本地用户并且没有保存的经过身份验证的身份,请使用“返回设置”、“继续使用云”并登录一次。这会保留现有数据并记录所有者以供将来恢复。
  • 通过更新托管邮件引擎映像以及控制平面来应用直接别名发件人策略更改。自定义 SQL 和主机本机邮件策略仍由操作员管理。
  • 更改 SPA 回退设置后重新部署现有生成的静态站点容器。现有站点保留 SPA 行为,直到明确更改为止。
  • Runtime security refreshes verify the deployed result

    An image that still contains the affected runtime requires a corrected image configuration rather than repeated redeployment. Appwrite's optional Geo service remains excluded.

11月4日2026v0.9.10特点修复17 更新

0.9.9 中云助手启动、恢复和 OAuth 同意失败的推荐补丁。还修复了部署、路由和恢复,并包括自 0.9.9 以来合并到主版本中的所有更改,以及附加的目录应用程序和可选的日历/联系人同步。

云、代理和 GitHub 操作

  • Cloud assistant recovery

    Preserve executable launcher permissions during workspace uploads and recover dead assistant endpoints after checking health inside the guest. Keep reachable busy daemons and existing profiles intact.

  • 同意回调

    Let the consent form own OAuth continuation so automatic navigation cannot consume the same callback twice.

  • 客户电子邮件发件人

    Use the SMTP transport's authorized sender by default. Optional SMTP_SUPPORT_FROM 和 SMTP_BILLING_FROM 别名需要该 SMTP 帐户的发送权限;别名不参与云中继。

  • 推荐定价

    Show referral discounts consistently in plan cards for monthly and annual billing, using the existing shared pricing calculation.

  • 拉取请求操作

    Verify the executed merge against the captured base and head, and publish Checks on the pull request head. Preserve trusted workflow selection, fork restrictions and per-attempt Check identity.

部署、域和备份

  • 撰写重新配置

    Retain existing DNS setup when redeploying to the same destination; request setup only for new hostnames. Normalize saved endpoint ports before submitting the deployment so source-review redeploys no longer fail with Expected string.

  • 存储的映像部署

    Retain stored image-only Compose services and their environment when a containerized controller cannot read the original local directory. Source-built services still require their build inputs.

  • 服务 www 重定向

    Share the apex/www controls across the wizard and Add domain form, and support editing existing service redirects. Preserve portless redirect intent, reject missing targets and loops before service writes, and commit domain API changes with their service endpoint atomically.

  • 通配符路由规则

    Enforce the configured wildcard virtual host's policies when no exact-host policy exists, while preserving exact-host overrides.

  • 音量恢复安全

    Finish and validate the incoming archive before clearing destination contents. Failed, truncated or timed-out uploads preserve existing data; temporary staging files are cleaned up on completion or failure.

目录、邮件和仪表板

  • 应用目录

    Add Appwrite, Prometheus, Alertmanager, VictoriaMetrics, Loki, OpenTelemetry Collector, Beszel, Listmonk and pgAdmin4, with setup guidance, service icons and runtime smoke coverage.

  • 目录端口路由

    Publish Listmonk and pgAdmin4 on their own host ports instead of accidentally reusing another service's port.

  • 日历和联系人

    Add an optional Radicale template and setup guidance for calendar/contact sync alongside the existing mail installation.

  • 错误详情

    Add a copy action to error toasts for sharing diagnostics.

升级注意事项

  • 一起更新 API、仪表板和所有 API 副本。此补丁没有添加新的数据库迁移。从 0.9.9 之前的版本升级时,还请遵循下面该版本的身份验证、连接和 SMTP 升级说明。
  • 卷恢复现在需要足够的临时磁盘空间来在提取之前暂存传入的存档。验证后的提取不是事务性的。
  • 版本验证保留已发布的 0.9.9 Compose 模板,因此更新门会测试之前的实际安装,包括存储的数据和路由。
11月3日2026v0.9.9特点修复安全性27 更新

重要安全更新,涵盖身份验证、云连接批准、服务器隔离和加密电子邮件传送。包括自 0.9.8 以来合并到主版本中的所有更改,以及部署、计费、助手和仪表板改进。

安全性

  • 身份验证依赖项

    Upgrade Better Auth and its plugins/adapters to 1.7.15 and the Hono Node adapter to 2.1.3. Address OAuth state, proxy, consent, rate-limit and static-path middleware advisories.

  • OAuth 和登录兼容性

    Use the provider's supported APIs for resources, signing, PKCE and refresh rotation. Preserve GET/POST authorization parameters, silent-request validation, signed login/MFA continuation, OIDC callbacks and existing MCP endpoint aliases. Register resources and token issuers from trusted instance configuration, while retaining HTTP setup and desktop loopback support.

  • 云连接审批

    Require explicit approval before connecting Desktop to a Cloud account. Headless CLI connections require the code shown in the terminal, bound to an expiring, single-use request and its PKCE proof. Recheck the approving session against live state. Share Better Auth's cookie and session handling across bridges and preserve issued bearer lifetimes.

  • 客户身份和限制

    Apply auth rate limits to the client's IP, using the existing trusted-proxy boundary. Normalize linked-instance IP fingerprints without combining distinct IPv6 hosts.

  • 服务器隔离

    Resolve shared network/PID namespaces only through services in the same stack; reject authored raw container references and host namespaces. Restrict host bind mounts across HTTP, MCP, native SDK and background deployment paths. Managed Docker repository mounts remain confined to prepared project storage. Reading local source contents or environment values over HTTP requires instance authority.

  • 加密的 SMTP

    Require TLS for authenticated mail delivery, including verified STARTTLS on submission ports. Refuse a plaintext fallback when the server cannot provide the required encryption.

  • 鲜味目录

    Update the PostgreSQL image to 2.20.2 and verify the catalog's configuration remains compatible.

安全建议和主机维护

  • 已审核主机补丁

    Inspect supported Ubuntu hosts, review the exact package changes, and apply scoped security fixes through the dashboard, CLI, SDK or MCP. Verify signed advisory data, trusted package origins, current permissions and server state before execution. A kernel reboot requires a separate review; unsupported hosts retain manual guidance.

  • 可观察的维护

    Persist task steps and bounded logs, reconnect to running jobs, and verify the resulting package/kernel state. Keep pending reboots visible and expose maintenance runs from the server and Monitoring.

  • 咨询偏好

    Let workspace owners/admins pause advisory checks, and save each user's banner visibility preference. Show scan freshness and availability accurately, preserve upstream severity, and explain when an application runtime must change before refreshing images can fix a finding.

部署和主机支持

  • 撰写来源评论

    Show added, changed and removed source services before redeploying. Reject a stale review, preserve saved settings when adopting an older baseline, and retire removed services only after a successful cutover. Preserve volumes and keep archived services available to rollback handling.

  • 固定的 Git 构建

    Fetch a requested commit even when it is outside the cloned branch. Improve submodule preparation and credential handling across local and remote build paths.

  • 边缘恢复

    Preserve unreadable virtual-host configurations during cleanup, and avoid identifying similarly named application containers as the OpenShip edge.

  • Arch 家庭主人

    Use pacman for Arch/Manjaro package preparation and component version checks instead of Debian commands.

  • 新鲜的 GeoIP 数据

    Refresh and validate the country database before creating release tags, with a scheduled refresh workflow for ongoing updates.

  • 发布验证

    Retain the published 0.9.8 Compose template for real upgrade tests. Retry transient Apple ticket-validation failures while still requiring a successfully validated installer before publication.

云、计费和电子邮件

  • 结账恢复

    Cancel unconfirmed purchases without manual cleanup, and recover the billing workspace after removing a canceled checkout's server. Preserve payment verification and scoped provider ownership.

  • 供应升级

    Send exhausted provisioning failures to support once, retaining the recovery context without duplicate escalation.

  • 客户电子邮件

    Welcome verified Cloud signups and confirmed purchasers, and send separate payment/renewal notices with scoped billing links. Queue mail durably, deduplicate webhook events, recheck the recipient's verified ownership, and retry delivery failures. The billing provider remains the invoice issuer.

  • 云计划指导

    Update the public plan descriptions and Hobby plan guidance, and make plan-selection hints more compact in the dashboard.

助手和仪表板

  • 互联模型发现

    List models through the connected assistant runtime and MCP, keeping connection setup and agent selection consistent.

  • 付费云服务器上的代理

    Prepare and run agents on an existing paid instance while preserving host access checks, profiles and sign-ins.

  • 紧凑的工具活动

    Keep routine assistant lookups inline, with detailed previews available when useful instead of expanding every tool result into a card.

  • 域名和推荐

    Simplify domain actions and plan guidance. Use consistent referral wording across the dashboard and website, and place referral code entry below the plan controls.

升级注意事项

  • Deploy the API, dashboard and all API replicas together. The OAuth migration preserves accounts and client registrations but expires legacy access/refresh tokens

    Reconnect existing MCP clients, assistant connections and chat connectors. Some older confidential clients may need to register again. Check for duplicate (provider_id, account_id) account pairs before upgrading from Better Auth 1.6.

  • 替换作者 container: 命名空间引用 service:<name> 对于同一堆栈中的服务。默认情况下禁用主机绑定安装。受信任的自托管实例的运营商可以显式启用 OPENSHIP_ALLOW_HOST_BIND_MOUNTS=true;云主机安装仍然受到限制。
  • 经过身份验证的 SMTP 必须支持经过验证的 TLS/STARTTLS。如果之前的端点仅接受纯文本传输,请配置支持 TLS 的提交端点。
11月2日2026v0.9.8特点2 更新

建议使用补丁恢复 0.9.7 中引入的范围代理创建和代理支持的自动化。

  • 兼容的助手运行时

    Update all Mindwire dependencies to 0.1.60, which supports the required bot protocol 9 and application-managed tools. OpenShip provisions the matching runtime on local and remote assistant hosts while preserving existing profiles and sign-ins.

  • 发布验证

    Create, edit and reopen scoped Codex and Claude profiles against the actual released daemon, and verify scoped agent creation and reuse over SSH before publishing. Keep the protocol and permission checks.

11月1日2026v0.9.7特点修复安全性18 更新

建议更新引入范围内的人工智能代理、经过审查的自动化和聊天应用程序集成。包括依赖项安全更新和所有 0.9.6 修复。

  • 特工角色

    Choose from 16 original flat bots with distinct silhouettes, gazes and expressions. Give default specialists a stable individual look across the switcher, automation setup and tool results, and preserve the chosen character when saving a new agent. Keep the chat header to the agent's name and role.

  • 监控AI快捷方式

    Prepare scoped repairs from the shorter Fix with AI action on app issues and a read-only workspace health report from the Monitoring header. Keep status labels in a dedicated column and move actions below details when the list is narrow.

  • 助理动作交接

    Offer a compact inline review when enabling saved automations, approve the exact revisions together, and continue the task in the same chat. Recheck existing permissions and reject stale batches atomically. Clarify that authorized MCP actions should be executed and verified, not handed back as manual instructions. Simplify the chat header and float the composer above the transcript without reducing its scrolling area.

  • AI 代理工作区

    Switch between the general assistant, specialists and automations in a collapsible 340px right column. Resume each agent's last valid chat, browse conversations from the header’s history drawer, and inspect automation runs with their existing investigation chats. Use a right drawer on mobile and keep agent configuration in the shared drawer. Simplify the conversation header and preserve scoped navigation, fresh requests and paused flow controls.

  • 自动化编辑

    Show Trigger, Investigate, Respond and Notify as compact connected settings rows, with fields expanding in place and full-width hover/focus. Keep saved summaries visible while fields load, and use matching skeletons across the agents workspace, conversations and editors. Edit a selected automation inline in AI Agents using the same forms, permissions and save checks as the dedicated editor. Use one app/status line and Save/Cancel toolbar, and return to run history after editing. Reuse the row summary in expanded chat previews. Chat-created flows stay paused until reviewed.

  • 用人工智能进行调查

    Open a prepared assistant request from failed deployment headers, failed app setup pages and active app issues. Keep the original app and deployment context through setup, use existing permissions, and scope the handoff to its originating account and workspace. Logs and errors stay out of shortcut URLs.

  • 助理代理范围

    Create specialists with saved instructions, an AI connection and named resource permissions. Assign tasks or select a specialist in an automation. Each task uses one inspectable conversation, including live follow-ups, through the existing Assistant and MCP execution path. Add agent and automation tools to the normal API, inline task links, and paused flow drafts for user review. Bound each task to its original authority; recheck scope changes, deduplicate requests, and revoke temporary execution tokens on completion or agent edits. Manage agents in an animated drawer, expand creation and editing across the screen, choose a flat character avatar, and open scoped chats in the main assistant workspace. The chat header identifies the active assistant or specialist and the current conversation. Keep connection management in the overflow menu and Assistant settings.

  • AI智能体介绍

    Show what agents can do through selectable deployment, investigation and automation examples. Keep one enable action, a compact host choice and original Codex/Claude Code marks. Put setup first on mobile and show a permissions-shaped skeleton while access setup loads.

  • 原生线束标识

    Show Codex and Claude Code with their native marks across the composer, connections, history and agent settings. Preserve the harness’s original authentication prompts, including ChatGPT sign-in for Codex.

  • 助理实时聊天和作曲家

    Smooth incoming text and scrolling, expand live thinking, and show animated tool activity with reduced-motion support. Attach, paste or drop images with removable previews, and switch models between replies in the same conversation. Images use Mindwire's conversation-bound uploads on the selected agent host; size/type validation and existing workspace permissions apply. Show immediate send progress and keep activity visible between replies and tool steps; use a solid stop icon. Clear the composer on send and reset conversation input to a medium-height, two-line field; restore failed submissions with their original attachments for retry.

  • 助理降价

    Render streaming replies with Streamdown, syntax-highlighted code, readable tables and nested lists across light, dim and dark themes. Keep copy controls tied to completed text and retain safe links without loading model-supplied images or executing raw HTML.

  • 助理访问和工具结果

    Stop offering instance-only diagnostics to workspace-scoped MCP connections. Keep the shared instance authorization gate for direct calls, and refresh completed chats after permission edits. Retire stale access requests and carry the last request into a new chat as an unsent draft. Add expandable tool activity, per-call request/result inspection, and inline app, server, deployment, service and repository cards using the existing view/import flows.

  • 聊天应用程序中的助手

    Talk to your own Claude Code or Codex agent from Slack, Discord, Telegram and Teams through the existing Assistant runtime and MCP grant. Workspace allowance and personal opt-in start off. Conversations are isolated by sender and chat; history, resume, new and stop reuse native conversations. Continue chat-origin conversations in the dashboard with the same approved access. Choose dedicated Assistant, deployment-command or combined bots. Durable replies read the exact native turn, including after dashboard continuation, and survive delivery retries without replaying turns. Access changes stop further execution. Add settings and per-provider setup guidance; preserve private command replies and assistant threads in the shared chat transport.

  • 助理自动化

    Add Assistant settings and an opt-in flow editor for failed deployments and confirmed service incidents. Investigate and notify, request approval, or explicitly choose app recovery and repository permissions. Support custom API endpoints and models, code fixes on new branches and draft PRs. Each flow stays within existing Assistant consent; exact patches are reviewed before approval and published through shared GitHub operations. Results appear in the agent conversation, with optional existing notification channels. Reuses MCP, deployment, jobs and notification paths, with private investigations, fresh health verification, run history, cooldowns and daily limits. Duplicate incidents and action retries cannot execute twice; changing access or pausing invalidates pending work. Cloud agents remain on the chosen customer server.

  • 聊天应用命令

    Connect Slack, Discord, Telegram or Microsoft Teams in Settings to list projects, check deployments, open private logs, and confirm redeploys or restarts. Each sender links their own account through the existing permission flow. Commands are opt-in, use the normal deployment path without AI, and deduplicate provider retries. Slack Socket Mode, Discord Gateway and Telegram polling work from Desktop or private servers without a public URL. Connections report their status, reconnect and recover durable cursors; Teams retains its public HTTPS webhook requirement. Bot connectivity runs directly in OpenShip with encrypted credentials and a durable inbox, without installing or requiring Mindwire. Only the optional assistant uses its agent runtime. Add separate account-link instructions and URL messages, localized replies following each user’s OpenShip language, and Telegram welcome, project and confirmation buttons. Share project command syntax between CLI and chat through @repo/commands;保留权限检查并通过重试跟踪各个回复消息。

  • 选择加入助理

    Use Claude Code or Codex through Mindwire in the Assistant tab, with streaming conversations, structured questions, tool results, agent connections and private history. Inline permission review reuses the existing MCP consent form; operations use the normal MCP permissions, deployment flows and audit rules. Native tools are restricted, retries reuse request receipts, and changing access requires a new conversation. Disabled by default; available on macOS and Linux hosts. Cloud uses a private Mindwire profile on the chosen customer server; Desktop can reuse local sign-in, while self-hosted and Cloud keep separate agent credentials. Tenant checks, durable consent and renewable turn leases protect conversations across API replicas. Agents can request additional access in the conversation; users review it in the shared permission editor. Requests grant nothing, retain current permissions until saved, and never retry a task automatically. Remote assistant hosts tolerate slow startup and retain their private connection record so a retry can reconnect to the same daemon.

  • 脱模硬化

    Include the shared commands package in self-hosted source distributions, keep repository changes explicitly classified as source writes, report safe background failure summaries without logging native credentials, and refresh the generated API and MCP references. Update compatible dependencies for published security fixes while retaining the existing OAuth/MCP data model. Implicit OAuth account linking now requires a verified local account as well as a provider-verified email, preventing pre-registered account hijacking. Migrate authenticator confirmation and lockout fields while preserving existing active factors and unfinished enrollments, including older instance backups. Preserve failed authenticator and recovery-code counters across denied requests, so challenge attempt limits and account lockouts cannot be reset by transaction rollback. Include the assistant type dependency in the public SDK and catalog new audit events.

  • 部署修复

    Redact long clone tokens from stored errors and skip the workspace dependency crawl when checking changes for Compose projects (#1546, #1547).

11月1日2026v0.9.6特点安全性34 更新

针对数据库恢复、可靠构建和迁移、GitHub 操作计划和托管基础架构更新的推荐更新。

  • 容器崩溃后恢复 PGlite

    Hold a Linux kernel file lock so reused PIDs cannot strand the database or admit an owner in another container. Preserve conservative checks for older locks and other operating systems (#1524).

  • 保持 Docker 个构建失败可读

    Surface the cause before long generated commands, preserve the full output in build logs, and retain Cloud recovery guidance after reload. Exit 137 is reported as a killed process with possible memory pressure, without claiming a confirmed out-of-memory event.

  • 保持 monorepo 运行时镜像与每个服务保持一致

    Use the service's framework and selected builder for its runtime instead of inheriting an unrelated parent image. Fill missing builders from the stack registry, preserve explicit runtime selections for unchanged apps, and use the same resolution when checking whether runtime images can be refreshed.

  • 添加范围 Kubernetes 清单基础

    Admit supported resources into a project's namespace with ownership checks on objects, pod/job templates and selectors. Validate the full change against Kubernetes before writing, reject changed Job definitions, and preserve conflict checks when updating or pruning. Exercise apply, update and cleanup against K3s in CI and the release gate. This foundation does not yet expose a manifest upload UI or deployment route (#1039).

  • 保留实时 Docker 日志

    Decode stdout and stderr independently across split frames and UTF-8 characters, keep TTY logs intact, and report malformed or truncated streams so the existing reconnect flow can recover (#1482).

  • 支持经过验证的自托管 OIDC 登录

    Discover a configured identity provider and verify signed ID tokens, issuer, audience, expiry and sign-in nonce before creating sessions. Preserve invitation and two-factor checks, require matching UserInfo subjects, and refuse insecure or redirected provider endpoints. Require verified email, scope accounts to the issuer and exact subject, and keep instance OIDC disabled on Openship Cloud and outside local-account auth mode (#1489).

  • 让 BuildKit 会话保持活动状态

    Answer Docker’s session health checks so builds can use optional secret mounts after long install/build steps. Close sessions on completion, cancellation, and transport errors (#1488).

  • 在服务器之间移动摘要引用的图像

    Use the reference restored by Docker load for migration's one-time deployment handover. Direct and relayed transfers no longer try to create a Docker tag containing a digest (#1526).

  • 在服务器之间移动无状态单一应用程序项目

    Deploy a project-owned app with no service rows through its single-app pipeline using the transferred image. Reject unsafe empty service scopes before copying data or stopping the source; reused containers stay outside the deployment scope. Single apps with mounted data remain unsupported and are refused before data movement (#1525).

  • 保持排队的 GitHub 个作业移动

    Replace a registration that GitHub assigned to another job, and only count spare registrations whose runners remain admitted and capable for the waiting workflow. Excluded runners, stale approvals and incompatible hosts no longer block dispatch (#1505, #1509, #1541).

  • 在副本启动期间保持云诊断可用

    Allow bounded schema initialization to wait for another replica, while preserving the short write deadlines and local-log fallback used during normal operation.

  • 更换服务容器后恢复健康

    Refresh only the stale service binding when the continuous watcher verifies a healthy successor under the same active deployment. Preserve native and Compose service identity through managed edge updates and rollback; leave unrelated services and deployment history intact (#1496).

  • 使用服务器凭据扫描私有存储库

    Repository preparation, monorepo folder selection and branch rescans use the shared GitHub credential chain, including the selected self-hosted server's saved token. Without a selection, only the active organization's local server is eligible. Borrowing requires repository access and server write permission; SSH provisioning, GitHub mutations and Cloud authentication remain unchanged (#1500).

  • 将 Laravel 工作人员建议与生产依赖项相匹配

    Suggest the standard queue worker when Horizon is only in require-dev,匹配默认的Composer --no-dev 安装。明确的角色选择仍然可用(#1171)。

  • 删除附加服务后保持运行时角色可用

    A single source app retains its existing deployment and role configuration flow after the last attached service is removed or disabled, preserving its service and routing identity (#1308).

  • 防止部署后出现错误的过时角色警告

    Background image cleanup updates storage measurements without changing the project's configuration revision. Real configuration edits still invalidate previously reviewed changes.

  • OpenShip 赚取

    Explain the Cloud affiliate program at /affiliates,具有交互式佣金分配、每月和每年的奖励时间、支付指导以及专门的社交预览。使用左侧边栏中的礼品盒图标标记仪表板附属条目“赚取”。

  • 正确启动CockroachDB服务

    Pass the required single-node command to the official image, generate an application password, and persist TLS certificates alongside the existing data volume. New services keep TLS and password authentication enabled; container replacement preserves both data and certificates. Include recovery steps for saved services missing the command (#1484).

  • 从缓慢的构建缓存扫描中恢复存储

    When free disk space or inodes already block deployment, allow up to two minutes to measure unused, owned build caches before reclaiming them. Healthy hosts retain the short best-effort scan; defer timed-out SSH measurements during automatic retention without blocking unrelated builds. Explicit cleanup still reports measurement failures; active builders and application volumes remain protected (#1527).

  • Reclaim images from interrupted first deployments

    Include projects that have never reached a running release in managed image collection. Resolve the last attempt through the existing tenant checks and retain the same rollback, retry, pin and in-use protections, so failed builds cannot fill the server with orphaned images.

  • 云联盟计划

    Create and revoke referral links with optional customer discounts, follow verified payments, renewals and expiry, and request reviewed cash payouts. Staff can review pending requests in a private operator queue and reconcile transfers, including after an account is deleted. Oblien owns the ledger and atomically reserves payout funds. The default minimum is $50, with trusted per-user overrides. Eligible monthly and annual Cloud compute starts at $10 per month equivalent; Manage, PAYG and top-ups are excluded. Program guidance lives beside the referral lists, with illustrated empty states, a two-step discount and plan picker, monthly/yearly eligibility enforced at checkout, encrypted manual payout accounts with immutable request destinations, payment-method guidance and a screenshot walkthrough in the docs. The program remains off until the provider and its explicit policy grant are configured.

  • 查看共享环境编辑

    Preview which services inherit an edited project variable, then save shared values and service overrides together. Stale reviews are rejected inside the write transaction; project write access is required, and saving alone does not restart applications.

  • 澄清推荐结账和收入

    Retain unavailable referral codes through sign-in until the customer removes them, and show commission per confirmed payment with renewals limited to the program's reward period.

  • 映像更新中断后恢复托管服务

    Attempt to restore the previous edge or mail image when replacement startup throws, including a lost SSH command channel after removal. Report unsuccessful recovery instead of treating a connection failure as proof of an outage (#1540).

  • 启动时验证权限资源名称

    Reject unknown permission leaf types during route registration using the shared authorization validator, so misspelled tags cannot reach request-time resource resolution (#1521).

  • 加载所选应用程序的源环境

    Use the app folder's openship.json 如果存在,则返回到存储库根目录,否则匹配设置期间显示的配置(#1480)。

  • 使用所选的 GitHub 令牌对私有子模块进行身份验证

    Support relative, HTTPS, SSH and recursive private dependencies through the shared deployment credential helper, while preserving repository and namespace scope and keeping credentials out of saved remote URLs (#1522).

  • 保留 Docker 次重新启动重试和端口映射

    Retain configured on-failure 容器创建期间的重试限制和每个已发布的绑定。

  • 在首次部署之前保持边缘路由可用

    Resolve domains through the project's saved server binding, preserve the origin of password-form submissions, and forward the visitor country to upstream applications. Document the scope of edge password protection and direct-port access (#1498, #1515, #1506).

  • 保持部署源身份完整

    Expose the selected revision as OPENSHIP_COMMIT_SHA,保留携带的 Compose 映像摘要,并一致地应用配置的部署路径(#1499、#1475、#1472)。

  • 显示正确的仪表板反馈

    Use custom apps' own logos, keep open card menus above adjacent controls, and clarify expiring-domain notifications (#1508, #1518, #1512).

  • 保留更新咨询范围

    Keep installation-specific notices scoped in Monitoring and recheck deployment eligibility before presenting update actions (#1467).

  • 将云定价与计费周期保持一致

    Present management plans and recurring compute charges using their actual billing periods (#1466).

  • 保持桌面版本可用

    Build and notarize macOS installers on the supported macOS 15 runner.

10月24日2026v0.9.5特点修复安全性4 更新

此修补程序在 0.9.4 更新后恢复自托管 Compose 启动。

  • 恢复仪表板就绪状态和边缘启动

    Bind the dashboard's Next.js server to 0.0.0.0 在其容器内,以便环回运行状况检查可以到达它。在 CLI 生成的参考自托管和源 Compose 环境中应用相同的绑定设置。已发布的主机端口保留其现有的环回默认值 (#1461)。

  • 测试完整的客户升级

    Gate image publication on upgrades from 0.9.3 and the previous release using their published API, dashboard and edge images and CLI templates. Verify populated PostgreSQL and Redis storage, custom ports, preserved secrets, admin credentials and signed sessions, saved edge routing, dashboard-to-API access, cold restart and fresh installation. Probe both dashboard image architectures before publication; an API-only migration check no longer stands in for a stack upgrade.

  • 解释安全刷新之前的源重建先决条件

    Global and project advisory views use the same runtime-update preflight as the deployment action. Replayed or revisionless source images show their prerequisite and an 开源重新部署 操作而不是提供会失败的刷新。 Redeploy仍然使用现有的项目部署控制;源出处、图像 pin 和租户授权仍然强制执行 (#1462)。

  • 包括打包工人图像校正

    Source builds of managed workers require Git checkout metadata. Bundled Dockerfiles in the released API no longer trigger a development worker build.

从 0.9.4 恢复

运行 openship update 0.9.5发布后。此更新通过正常管道重新创建 API、仪表板和边缘,并保留现有数据库、Redis 和应用程序存储。对于 0.9.4 上的临时恢复,设置 HOSTNAME: "0.0.0.0" 在仪表板服务的 Compose 中 environment 并运行 docker compose up -d 使用该安装的现有 Compose 文件和项目名称。稍后运行 CLI 会重新生成该文件;更新至 0.9.5 以进行永久修复。

10月24日2026v0.9.4特点修复安全性Breaking80 更新

此版本添加了对现有 Docker Swarm 集群的部署、审核的数据库复制、年度云计费、OpenShip 管理支持计划、运行时安全建议、显式 monorepo 应用选择和边缘密码保护。部署恢复、持久存储、云操作和网络邮件获得可靠性和安全修复。这些注释涵盖了自 0.9.3 以来的更改。

项目、存储库和环境

  • 选择要部署的 monorepo 应用程序

    New imports ask for an explicit app selection instead of enabling every detected package or port. Add more apps, browse or enter repository folders, and retain saved selections, manually added roots, custom commands and private access when rescanning or reopening a project.

  • 保持大型域列表易于管理

    The wizard groups routes by their owning app, shows a total and the first three rows, and offers View all. Apps using the same port keep separate domain ownership; changing deployment mode preserves the selected app's routes and privacy settings.

  • 从存储库构建附加服务

    Services and Topology share a From repository form with folder, build-context and Dockerfile selection. Save the service, then deploy it through the normal pipeline. Manual paths and retry remain available when browsing fails. Catalog selection gains compact source tabs, search and category filtering while retaining generated credentials.

  • 在检测期间保留 Compose 拓扑

    A root Dockerfile alongside a Compose file retains the declared services and volumes even when framework detection also matches. Development-only Compose files beside ordinary framework projects remain opt-in; explicitly selected configuration retains precedence.

  • 跳过不相关的工作区推送

    Single-app subfolder projects consider transitive workspace dependencies, shared build inputs and lockfiles before automatic deployment. The update banner uses the same decision. Configure autoDeployPaths.include 和 exclude 明确的规则;不确定的分析会保留部署,而不是默默地跳过更改。

  • 一致地阅读所请求的源版本

    Retries and explicit-commit deployments read Compose files and openship.json 来自该提交的默认值,而不是将旧的签出与分支的最新配置混合在一起。

  • 使用一种有效的环境视图

    The Compose wizard and service editor resolve defaults and interpolation consistently while preserving the original templates and masked secrets. Save persists intentional service edits; existing projects also offer Cancel without writing changes. Revealed values and late lookup responses no longer restore an old value after saving.

  • 阐明保存和应用环境更改

    Save and Apply & restart describe their separate effects. Runtime-only values appear in a compact disclosure, unchanged image defaults no longer produce recovery warnings, and Apply can resolve an owned live legacy service without a populated per-service deployment record. Missing containers lead to the existing deployment action.

  • 完成 GitHub 个连接和私有克隆

    Hosted App setup, installation selection and attempt polling use the owning Cloud connection consistently. Self-hosted App creation sends a valid manifest redirect URL. Authorized same-owner private submodules receive scoped, short-lived credentials without persisting tokens in clone URLs or Git configuration.

  • 显示构建实际运行的位置

    Remote Docker deployments no longer offer an unsupported local-image build or label a remote build as local. Genuine local bare builds and independent clone-location choices remain available.

部署、存储和恢复

  • 从打包安装中提取托管工作人员映像

    Bundled workspace files no longer make a release installation look like a development checkout. Automatic source builds require Git checkout metadata; explicit administrator build contexts still work for source archives. Remote builds use the published protected worker matching the release.

  • 备份独立应用程序存储

    Project backup policies now capture a single app's persistent volumes even when it has no service rows. Manual, scheduled and pre-deploy runs share the existing backup and restore flow, including integrity verification, confirmation and retention. App restore points remain distinct from deleted-service history (#1444).

  • 使用带有附加基础设施的发布命令和角色

    Supported self-hosted/Desktop Docker projects can keep one primary source app on the normal release-command, worker and scheduler pipeline while preparing attached private image services first. Infrastructure health gates app activation; retries, cancellation and rollback preserve confirmed databases and volumes. General Compose, multiple source apps, Cloud and cluster targets retain their existing role/release-command restrictions.

  • 解释不支持的角色配置

    Refusals describe which saved release command or role must change instead of recommending the Docker runtime already in use. Eligible older projects without a persisted runtime mode can configure roles through the same runtime resolver as deployment.

  • 在构建之前检查所需的 Compose 变量

    Validate the effective enabled service cohort before image builds, registry pulls or cutover. Errors list missing keys by service without exposing values; frozen rollback settings and explicit service scopes retain their existing precedence.

  • 重试已完成的 Docker 构建

    Retry deployment can reuse a retained, ownership-verified image after activation fails. It preserves the source revision and destination, with no rebuild or replacement pull. Missing artifacts fail clearly; unsupported bare/static and source-bind attempts do not offer an image-only retry.

  • 故意刷新运行时图像

    The wizard exposes runtime versions, build images and production images. On-demand checks compare available image digests, and Refresh images & redeploy uses the normal readiness and rollback pipeline. Configured version tags, digest pins and deployment scope stay intact; unavailable comparisons remain unknown and pins never advance automatically.

  • 通过符合条件的 Compose 替代品来保留现任者

    Supported self-hosted Docker deployments can prepare an overlapping candidate when saved limits, measured headroom, port provenance and storage compatibility permit it. The old service remains until routing and the successful release are committed. Other targets keep normal replacement order; concurrent writable storage needs an explicit opt-in for the exact mount.

  • 在允许重试之前解决中断的路由恢复

    A timed-out Compose recovery requests cancellation and waits for its in-flight route pass to finish before releasing deployment ownership. Uncertain recovery retains the containers needed for recovery instead of allowing a late route write to overwrite a newer deployment.

  • 在重新部署中保留映像声明的数据

    Self-hosted and Desktop-managed Docker replacements reuse stable project-owned volumes for image VOLUME 声明。从经过精确验证的输出容器中恢复旧存储;丢失或冲突的所有权会停止部署,而不是附加不相关的孤儿或从空数据开始。显式安装优先,保留的自有卷显示在删除预览中。

  • 裸部署需要工作持久性

    Provision writable build, shared-data, process metadata and log directories through the deployment login. Persistence failures stop activation instead of silently leaving data inside a replaceable release directory. Hosts needing one-time permission setup receive actionable guidance.

  • 使用空存储启动服务而不擦除其旧数据

    Writable named volumes offer Start with empty storage, with service-name confirmation and a preview of the new and retained volume names. The existing service deployment applies the change; failed admission can retry the same saved volume selection. Other mounts, backups and the previous volume remain available for recovery.

  • 使工件保留适应磁盘容量

    Automatic retention can reclaim eligible older Docker release artifacts under measured storage pressure while protecting active releases, pins, shared references and ongoing work. Reclamation requires a verified rebuild or immutable-image recovery path. Managed idle-cache budgets scale with filesystem size; application containers and volumes are excluded from pressure cleanup.

  • 报告有用的恢复失败

    When a Docker restore helper exits without delivering its diagnostic output, collect a bounded tail of its logs. Stalled or unavailable log reads cannot hide the original failure or indefinitely delay cancellation and helper cleanup. Restore ordering and the separate attach-input issue are unchanged.

  • 可靠地应用 Compose 控制平面更新

    Explicit updates recreate API, dashboard and edge services even when an earlier image prefetch already changed the environment. Updates wait for application readiness and report failures; PostgreSQL and Redis are not targets of forced recreation.

  • 公开每个服务的交换控制

    Opt into resources.swapDisabled 适用于具有正内存限制和经过验证的交换记帐的受支持的 Docker 服务。共享验证保留了配置编辑所需的上限。这会更改选定的服务,而不会更改主机范围的交换或施加新的构建限制。

  • 保持部署时间准确

    Build measurements survive terminal outcome writes, service timings include image preparation, and measurements freeze before cleanup. Unknown durations remain unknown, skipped builds display 0s,并且未触及的服务不会获取发明的测量值。

集群、扩展和拓扑

  • 部署到现有的 Docker Swarm

    Desktop and self-hosted controllers can inspect an existing Linux manager, connect its cluster, and deploy new application or Compose workloads through the shared deployment, routing, scaling and rollback flow. Nodes pull immutable image digests and use release-scoped secrets. Existing Swarm tasks and routing-mesh ports stay protected from standalone adoption and edge takeover. Moving a previously deployed project requires an explicit migration.

  • 检查扩展和数据库复制

    Topology Scale reviews application changes before applying them. Self-hosted Kubernetes can manage PostgreSQL readers and authenticated Redis/Sentinel replication through the existing operators, with verified backups and explicit writer/reader connection changes. Reader removal checks dependent consumers; unsafe Redis reductions use a verified smaller copy that preserves the original until the connection switch is approved. Swarm application scaling remains supported; synchronized database replication requires Kubernetes and is separate from copying a database.

  • 在概述中查看数据库成员

    Primary and replica cards show their observed roles, health, servers and replication links. Larger graphs can switch to a compact view; Redis Sentinel voters remain distinct from data replicas. Missing observations do not invent a primary or a running member.

  • 让 K3s 设置和恢复更加清晰

    Require cgroup v2 before installation, prefer This Server for the initial gateway/control roles, and correct private kubelet connectivity. Retries can migrate an unchanged Openship-owned legacy configuration and finish its required restart; edited or unverified configurations stop with bounded, credential-redacted diagnostics.

域名、入口和证书

  • 密码保护自托管路由和本机预览

    Configure a shared password at the OpenResty edge. Authenticated requests verify a signed browser cookie locally, without an API, database or Redis lookup per request. Public routes keep their existing path. Password changes and revocation invalidate sessions; protected responses disable caching.

  • 一起完成服务路由和HTTPS

    Project and service domain saves share the existing routing preparation and certificate checks. First-route setup uses an inline progress viewer, retains explicit edge/DNS-01 consent, and refreshes canonical status after success or partial failure. A ready proxy no longer masks a failed or disconnected HTTPS check.

  • 发布没有目标端口的仅重定向域

    Compose www/apex redirects can reach the edge even when the domain has no upstream service port.

  • 让无路由工作负载独立于边缘

    Private deployments without hostname routes skip unnecessary edge takeover, challenge and vhost preparation. Fixed-port services retain their explicit bindings; automatic allocations still require verified inventory and durable port claims.

  • 在没有自定义域的情况下打开 pgAdmin

    PostgreSQL + pgAdmin supports an explicit Port only option while PostgreSQL stays internal. New catalog services also generate required PostgreSQL, MySQL, MariaDB, MongoDB and Typesense credentials instead of leaving their bootstrap secrets empty.

  • 保持目录图像可用

    Convex uses its new official registry namespace with the existing version pin. The retired Mindwire Console/runtime template is hidden and disabled for new installs; existing project data stays unchanged.

  • 重复使用有效的父通配符证书

    Immediate subdomains can inherit a validated parent wildcard certificate when an exact certificate is absent. Exact certificates retain precedence; read failures preserve the working route rather than initiating replacement issuance or copying private keys.

  • 替换手动证书而不破坏续订状态

    Remove only the selected hostname's obsolete Certbot renewal record after validation. Failed installation restores the prior certificate, key or archive links and renewal configuration before any reload; unrelated lineages remain intact.

  • 改进路由恢复和诊断

    Control-plane setup can reclaim its own quarantined dashboard port without taking another workload's claim. ACME 502/504 errors describe challenge forwarding and the temporary listener; safe Cloud routing errors retain their actionable cause instead of blaming a healthy server connection.

  • 将隧道管理保留在路线菜单中

    Cloudflare Tunnel settings move into the existing context menu, retaining per-domain Access settings, retry and readiness behavior without a persistent management row on every card.

云、计费、监控和操作

  • 从云管理客户拥有的基础设施

    Openship Manage Basic costs $5/month per organization with email support; Priority costs $20/month with priority support. Both include two connected servers, plus $3/month per extra server. Paid Cloud includes the Basic allowance once per organization; Priority retains its support fee. Expiration ends management access after the paid period while applications and data remain on the customer's hosts. Self-hosted control planes remain free.

  • 选择按月或按年云计费

    Hobby, Starter, Pro and Scale cost $12, $24, $47 and $119 per month, or $120, $240, $468 and $1,188 billed annually. The purchase view defaults to Yearly when supported by the provider, shows the monthly equivalent and full annual charge, and retains an explicit Monthly switch. Custom resources use the selected interval through quote, checkout and plan changes. Existing subscriptions retain their saved prices and allowances.

  • 更新入门级云容量

    New Hobby purchases include 1 vCPU, 4 GB RAM, 50 GB storage and email support. New Scale offers allow 50 projects. These catalog changes do not rewrite existing paid contracts.

  • 简化计划选择和付款回收

    Cloud plans, Prepaid PAYG and Manage your server share the purchase view. Manage plans are also available directly when connecting a server. Pending purchases appear under Payments & invoices with a count, and Manage checkout keeps the server allowance and total beside the selected support plan.

  • 保持管理计费和访问的协调

    Durable checkout intent and receipt validation protect purchase retries. Paid Cloud organizations receive their included management allowance once, and allowance changes coordinate with server connections. Increasing recurring charges after Cloud coverage ends requires explicit consent.

  • 恢复待结帐冲突

    Explain when a purchase must be completed or cancelled, and open the existing payment recovery dialog. Checkout limits, pending resource changes, verification failures and cancellation in progress receive specific guidance instead of a generic retry message.

  • 重新连接云使用流

    Interrupted read-only subscriptions recover from retryable disconnects with bounded backoff. Authentication failures, malformed data and stalled subscriptions still fail clearly; cancellation releases readers, requests and timers.

  • 精准恢复孤立云终端

    Refresh expiring namespace credentials for dispatch and teardown, then recover only the marked commands belonging to the interrupted operation. Ownership is cleared only after confirmed process exit; live controllers and another installation's claims remain protected.

  • 重用范围内的提供商凭据并保留限制指导

    Concurrent Cloud lookups share short-lived namespace tokens after ownership checks. Rejected token generations are invalidated without evicting newer credentials or replaying mutations. HTTP 429/503 and bounded Retry-After guidance survive the transport.

  • 解释与资源相关的部署失败

    Supported OOM, heap-limit and storage evidence produces a saved diagnosis and Review capacity action for the affected Cloud space. The explanation survives reloads and compacted logs. Long builds receive optional advice rather than an invented capacity failure; upgrades and retries remain explicit.

  • 在项目状态中反映运行时事件

    Known incidents on the active self-hosted workload show Action Required and link to Monitoring & Logs. Status clears after observed recovery; intentional stops, retired workloads and monitoring opt-outs do not create stale attention.

  • 计算请求的响应平均值

    Overview and CLI traffic metrics divide total request duration by total request count, with consistent millisecond conversion for Cloud and self-hosted data. Uneven traffic and live/archive refreshes no longer inflate the reported average. Edge collection is unchanged.

  • 通过临时 API 故障保留活跃的 Actions 运行者

    Retry transient provider, GitHub and App-token renewal failures without cancelling the worker, releasing its capacity or silently falling back to broader user credentials. Persist supervisor completion before external cleanup and retain verified infrastructure errors when GitHub synchronization finishes.

  • 可靠地合并操作历史记录

    Local timestamps and Cloud date strings sort together without crashing the Actions page. Failed Cloud augmentation preserves the local run list. Service connection/unlink messages also reflect the existing automatic deployment attempt instead of asking users to trigger it twice.

  • 在帐户变更期间保持活跃的个人工作空间

    Deleting or leaving the selected team workspace restores the stored session owner's personal workspace instead of failing while clearing the active organization.

安全和凭证

  • 修补DOM测试环境

    Dashboard and webmail tests use Happy DOM 21.0.4, which fixes the module import alias code-execution vulnerability (GHSA-834v-8h66-3h79).

  • 将运行时安全建议与已部署的工作负载相匹配

    Verify a public, signed advisory feed and match affected image digests or observed runtime versions. New runtime rules, deployment changes and Check again refresh bounded container observations; ordinary polling reuses one current observation per project. Findings appear in the existing global critical/update banner with a shared affected-app review; no project visit is needed. The banner reads cached, workspace-authorized evidence without probing containers. Missing evidence stays unknown. Initial notices cover Node.js/Bun Brotli fixes and PHP's October security guidance, including a separate manual configuration warning that an image update alone cannot clear.

  • 通过部署管道应用经过审核的补丁

    Refresh images & redeploy can pull a replacement behind the same tag, or rebuild the deployed Git revision with refreshed base images. Automatic refresh is off by default and requires explicit consent, a signed affected/fixed digest pair, an eligible image service and unchanged configuration. It pins the approved replacement, uses the normal refresh and environment-resolution flow, preserves persistent volumes, and verifies the deployed result. Late environment changes stop an automatic update for review. Concurrent requests admit one automatic attempt; rollback clears the one-time approval. Explicit digest pins remain fixed.

  • 通过现有通知渠道发送安全通知

    Verified, enabled channels receive matching alerts by default, with a per-channel opt-out and durable delivery deduplication. Feed checks share authentication-aware polling, conditional requests and backoff with release updates: five minutes when authenticated, one hour without authentication. Advisory metadata cannot supply executable commands.

  • 固定修补的运行时和构建工具

    Use Node 22.23.4 and Bun 1.4.4 across the affected control-plane, website, webmail and worker image stages, with verified image digests. Desktop moves to supported Electron 44.9.2; Actions distributions use Go 1.26.9 and updated Git, archive, SSH/HTTP and telemetry dependencies.

  • 在发布检查中保留运行时回归

    Exercise the upstream Brotli decoder rejection case, streaming input, private-CA HTTPS, hostname verification and authenticated asynchronous WebSockets. TLS SNI is sent only for DNS names, and package-manager bootstrapping works when node 是 Bun 的别名。

  • 跨租户和航站楼边界保留权限

    Service, server and proxied Cloud terminals retain the caller's credential restrictions and recheck expiry, revocation and current administrative access. SaaS-managed customer hosts use verified public destinations, SSH host-key pins and encrypted uploaded credentials; operator identities and private certificate-provider settings remain outside tenant-controlled host configuration.

  • 使用时范围备份连接

    Cloud S3/SFTP destinations pass the shared public-network checks before connecting to the validated address. Server SSH identity and existing host-key pins remain enforced for SFTP; self-hosted private backup storage stays supported.

  • 授予更窄的代币功能

    Personal access tokens and MCP clients can receive project-scoped domain read/write/delete and deployment read/trigger permissions. Minting checks the creator's authority, and cancellation, rollback and deployment deletion retain their administrative requirement.

  • 保护来自元数据目标的远程 Docker 构建

    Rootful Linux SSH and Cloud builds use the project-owned BuildKit worker's IPv4/IPv6 metadata and credential-endpoint policy, including after restart. Missing required executor or policy support fails before repository commands; local Engine API, bare and Kubernetes builds remain outside this policy's scope.

  • 在发布依赖包之前验证工作人员发布

    Publish and anonymously verify the protected worker for both supported Linux architectures before dependent image and bundled-release publication. Release receipts must match the tag and source commit; missing or private images stop publication.

  • 隔离禁用的预览服务

    Disabled service copies retain their disabled state while host bind mounts and external host/container namespace references are removed. Named/anonymous volumes and sibling service references stay usable; production configuration is unchanged.

  • 共享地址后面的单独 Webhook 端点配额

    Unrelated hooks no longer exhaust one another's source-IP bucket. Endpoint quotas share the existing limiter with a separate aggregate IP ceiling; authentication, signatures and credential redaction remain enforced.

桌面、网络邮件、网站和文档

  • 使用已修补的运行时构建 Windows 个安装程序

    Stage SSH and Docker dependencies from a package manifest so version ranges do not pass through Windows command shims. The packaged dependency load check remains required.

  • 恢复可见的脱机桌面启动

    Embed the shared generated theme palette in the native loading page so its text and artwork remain visible before the dashboard loads.

  • 修复较旧的托管 Web 邮件主机映射

    Backfill the missing host-gateway alias for the explicitly linked webmail service on its own self-hosted mail server. The repair preserves credentials and volumes and takes effect through the next normal deployment.

  • 使用有界渲染预览 Office 附件

    XLSX, DOCX and CSV files gain readable, sandboxed previews with limits on parsing and rendered content. Unsupported, encrypted, corrupt or truncated content retains a download option. Active HTML/SVG/XML and unknown attachment types download instead of executing in the signed-in webmail origin.

  • 一致更新邮件和编辑器依赖项

    Align the patched editor dependency graph across direct and nested imports, update Nodemailer and Mailparser, and preserve reviewed runtime overrides in Docker and tarball packages. Existing SMTP modes and credential repair remain supported.

  • 保持公共页面社交预览完好无损

    Pricing, marketing, catalog, feature, blog, changelog and mail-guide pages inherit the shared Open Graph and Twitter images while retaining explicit page images and metadata. The release checks validate the rendered image tags and their image responses.

  • 在网站导航中显示 GitHub 颗星

    Desktop and mobile navigation display the cached repository star count, with an accessible exact count and a fallback when GitHub is unavailable.

  • 完善运营指导

    Document Docker socket permissions and reconnecting after group changes, update the shared API/SDK/CLI/MCP references, and explain the supported cluster, recovery and runtime-image workflows.

升级注意事项

  • Rebuild or recreate the affected control-plane and webmail deployments to apply their runtime updates. Explicit project runtime versions and image digest pins are preserved

    Updating Openship alone does not update every deployed app.

  • 受保护的 rootful SSH Docker 版本需要 Buildx 和 root 或无密码 sudo 来进行可信工作线程策略和缓存文件系统操作。普通显式 CPU/RAM 限制和未配置的资源共享保留其现有行为。
  • 现有 Swarm 支持适用于桌面/自托管控制器,在连接的管理器上提供停止优先切换和单实例持久服务。它不采用任意现有堆栈或添加托管云集群。托管PostgreSQL/Redis复制需要自托管Kubernetes运算符。
10月17日2026v0.9.3特点修复25 更新

此版本改进了云监控和构建缓存的可靠性,添加了部署自动化和独立的拉取请求预览,并使工作人员和调度程序更易于配置、观察和恢复。这些注释涵盖了自 0.9.2 以来的所有合并更改。

部署自动化和预览

  • 将命令变量移至环境中

    Review literal environment assignments in install, build and start commands, then migrate them into encrypted project or service settings. Conflicts and concurrent edits stop the migration before partial changes are saved. Import and saved settings share the same parser and guidance.

  • 自动准备框架输出

    Next.js standalone monorepos and Nuxt builds retain their required workspace dependencies, public/static assets and selected Node or Bun runtime. Managed direct-server defaults start from the configured app directory; explicit custom commands retain their working directory.

  • 查看旧的手动缓存安装

    Detect duplicate package/framework cache mounts and offer configuration migration only after a successful build proves managed cache support for those paths. Existing volume data is retained. Build logs report observed cache reuse and build-time comparisons.

  • 尽早发现设置问题

    Pre-install checks identify missing app roots and environment examples; command-variable, standalone startup and duplicate-mount guidance explains what needs attention without exposing variable values.

  • 选择加入 GitHub 个拉取请求预览

    Same-repository, non-draft pull requests can deploy their exact commit into a separate preview environment with preview-only variables, isolated volumes and per-service URLs. Production variables are not copied. Forks and unsafe shared-storage configurations are excluded.

  • 恢复预览生命周期操作

    Durable coordination handles repeated webhooks, controller restarts and retryable close/merge cleanup. Optional GitHub comments update one existing comment, alongside the existing deployment Checks. Whole-instance transfers preserve preview ownership; individual project imports clear preview automation that cannot safely transfer.

  • 使用 SDK 中的自动化

    Configure and list previews, inspect or migrate manual cache mounts, and move command variables through the shared validated project operations.

工作人员、调度程序和回滚

  • 配置角色而无需重建 Web 应用程序

    Apps & Services → Configure roles can add or change workers and singleton schedulers on active single-app self-hosted Docker deployments. The normal deployment engine reuses the verified image and frozen environment while preserving the web container and unchanged replicas. The API, SDK and CLI expose the same operation. Cloud, bare, static, cluster and multi-service targets are outside this editor's scope.

  • 查看和检查后台进程

    Runtime roles appear in project service views and topology, with role/replica log selection and retry states. Health monitoring includes worker and scheduler failures instead of observing only the foreground container.

  • 保留独立的角色建议

    Framework scans expose matching presets at the selected app root. Only presets competing for the same declared slot exclude one another; explicit roles, including an empty list, retain precedence. Suggestions do not automatically enable background processes.

  • 恢复中断的角色切换

    Persist exact container identities and ownership before replacement, predecessor shutdown and publication. Startup and deployment reconciliation either finish a published handover or safely restore its predecessor; uncertain cleanup remains pending before conflicting work.

  • 保护活动和回滚映像

    Retained role replicas keep their required image artifacts protected during configuration changes and release cleanup.

  • 准确恢复冻结的 Compose 环境

    Rollback preserves encrypted deployment snapshots without confusing literal redaction-like values with missing secrets. Incomplete legacy snapshots fail clearly rather than borrowing mutable current service settings.

云监控、缓存和存储

  • 避免昂贵的监控扫描

    Cloud hosts using fuse-overlayfs skip Docker's full storage inventory, which can exhaust daemon memory. Host totals remain measured; unavailable detailed project storage stays unknown.

  • 显示访客 RAM 使用情况

    Use verified guest counters instead of hypervisor process memory and overhead. Older guests receive a bounded, read-only memory sample; stream teardown releases the executor.

  • 保持部分指标有用

    Missing disk or memory fields in a live frame retain the latest measured value for that metric, with its measurement time. Purchased capacity is never substituted for measured consumption.

  • 保持云缓存清理范围

    Collect only owned, idle project-worker caches and stop before Docker Engine's global builder prune. Cache reuse, worker GC, existing build concurrency and user-configured resource limits are unchanged. Cloud builds require their isolated BuildKit executor instead of silently falling back to the embedded builder. Existing legacy daemon state and autonomous Docker GC remain separate host-maintenance concerns.

  • 接受没有固定 inode 总数的文件系统

    Unsupported or zero inode totals mean unknown availability rather than confirmed exhaustion. Real free-space and supported inode-exhaustion checks still protect deployment admission.

域和入口

  • 在首次部署时路由经过验证的自定义域

    Single-app domains without a saved destination use the verified serving port through the shared route planner. Explicit endpoints and service-group destinations retain their ownership instead of selecting a sibling service.

  • 避免临时辅助主机端口

    Secondary loopback publications use the existing allocator and the target host's ephemeral-range checks.

  • 处理各种Cloudflare访问应用程序

    Accounts containing launcher or other domain-less applications no longer crash managed ingress setup. Inventory and write receipts are validated while overlap and foreign-resource ownership protection remain enforced.

  • 明确边缘可用性

    Documentation explains edge failure behavior and recovery responsibilities for deployed applications.

网络邮件

  • 解析操作的确切消息 ID

    Thread reads, deletion, labels and flags validate exact IMAP envelope identities instead of trusting substring search matches. Literal percent sequences remain unchanged, stale UID hints are rejected, and missing or refused operations no longer report success.

  • 正确缓存应用程序资源

    Fingerprinted assets receive immutable caching while application HTML is revalidated.

  • 提供预压缩资产

    Negotiate available Brotli or gzip files with appropriate content types, encoding and cache headers.

10月16日2026v0.9.2特点安全性39 更新

此补丁添加了工作线程和调度程序执行、个人外观自定义以及自托管服务器的托管 Cloudflare 隧道设置。云空间、可重用的构建缓存、更多的目录应用程序和更安全的存储清理可改善日常操作。这些注释涵盖了自 0.9.1 以来的所有合并更改。

工人和调度员

  • 在您的网络应用程序旁边运行角色

    Declare workers and schedulers in openship.json 或项目 API。单一应用 Docker 部署从应用映像启动单独的容器,具有共享环境、卷和连接的网络、自己的命令和关闭设置,并且没有发布的端口。角色包括暂停、恢复、重新启动、回滚和项目删除。

  • 安全移交单身人士

    Scheduler renames, command changes, name swaps and conversions into workers stop and retain outgoing singletons before starting potentially conflicting replacements. Failed deployments restore them only after those replacements are confirmed removed. Failed retirement of an old role is surfaced in the deployment warning with its container identity.

  • 需要经过验证的启动

    Every replica needs exactly one stable result for its container ID before optional exec health checks run. Missing inspections, duplicate results and processes that already exited successfully fail startup. Both project-defined and image-inherited PORT 值已从角色中删除。

  • 明确角色配置

    Move and copy refuse active, unfinished or preserved-cancelled role workloads even after saved roles are cleared. Preset-only when 和 unless keys in declared roles produce warnings rather than silently appearing to control execution. Automatic framework role selection and cross-server role migration are not included.

  • 改进框架关闭默认值

    Rails presets have measured stop settings, and Laravel's scheduler preset uses SIGTERM with a 10-second grace period while queue and Horizon workers retain 90 seconds. Customize these bounds for long-running tasks; they do not guarantee task completion or exactly-once scheduling. Laravel web-role cache warming is available as an opt-in setting.

外观及仪表板

  • 定制您自己的外观

    Settings → General → Customize previews color tokens and typography live, with explicit Save, Discard and Reset. Import themes from JSON, a file or an HTTPS URL; export themes and libraries, including supported WOFF2 fonts. Preferences belong to the signed-in user and stay isolated across accounts and instances. API, SDK, CLI and MCP operations use the same theme format.

  • 将操作工具放在一起

    Project monitoring and logs share one navigation entry with their own views. Backups moves under Infrastructure. Project sidebars show assigned domains, migration retries retain destination choices, and migrated service deployments use the correct icons.

  • 减少错误的断电警报

    The health watcher confirms repeated bounded Docker probe failures before announcing a server outage. Late probe replies cannot falsely announce recovery. Self-hosted administrators can clear resolved monitoring history with confirmation while retaining open incidents.

  • 提高导航和终端可靠性

    GitHub discovery no longer blocks dashboard pages, selection controls use consistent states, and leaving a server terminal during WebGL loading cancels setup and disposes the terminal. Instance connection and move actions have clearer setup and recovery guidance.

Cloudflare 隧道和域

  • 管理来自 OpenShip 的自托管入口

    Server → Security can connect or create a remotely managed named Cloudflare Tunnel using saved credentials, configure proxied DNS and optionally apply an existing reusable Access policy. Install a pinned connector on a supported Linux server or use its existing connector. Managed Openship Cloud routing retains its existing path.

  • 使用可恢复设置注册域

    Explicitly enable automatic tunnel enrollment for new custom domains or connect existing domains individually. Setup records Access, tunnel and DNS progress, supports retry after interrupted requests, and removes only owned resources. External edits remain visible for review instead of being overwritten. Exact hostnames and www 同伴得到支持;通配符自动注册不是。

  • 选择主要和 www 行为

    The deployment wizard defaults a newly included companion hostname to a 301 redirect to the entered primary. Choose bare primary, www primary or Serve both on Cloud and self-hosted destinations. Redirect rows show their target instead of duplicate runtime inputs.

  • 保持域操作一致

    Service aliases on the same port are preserved, domains added through the CLI receive routing, and Cloud routing retries recover missing Pages through the owning Cloud connection.

  • 尊重容器化边缘上的可信代理

    Operator-declared proxy IPs reach the edge without rebuilding its image. Invalid addresses and CIDR prefixes are discarded. Failed configuration updates restore the previous shared trust include, and an incomplete rollback cannot activate a partial configuration.

云空间、计费和连接

  • 将托管容量视为云空间

    A shared picker, Overview and Activity views show projects, purchased capacity and measured usage, with clear retry states for unavailable readings. Existing allocations and subscriptions keep their identity; connected self-hosted server tools remain available.

  • 始终使用拥有的云帐户

    Connected Desktop and self-hosted installations create Cloud projects through Cloud's API. Server, project and deployment operations enforce their organization and provider namespace. Cloud consent shows the actual account and organization and lets you switch either before explicitly authorizing the connection.

  • 继续购买,无需重复选择计划

    Pricing links carry the chosen plan into the signed-in app's checkout flow. Pending unpaid payments can be cancelled when supported by the provider so another plan can be selected; retries retain the original payment identity. Server cancellation is easier to find and repeated requests cannot create duplicate operations.

  • 在现有空间上配置操作

    Cloud's Add runner flow opens the capability form directly with the space picker. Local Actions lists remain available when Cloud discovery fails, and official runner containers support non-root SSH supervisors. Temporary runner profiles retain their separate funding flow.

  • 保持实例与其源的切换

    Control-plane provisioning on a linked managed destination stays owned by the source controller until the move transfers the instance, including resumed API-only and dashboard installations.

构建性能和资源控制

  • 保持未配置的资源不受限制

    Omitted build and service CPU/RAM limits no longer become sampled capacity caps or catalog sizing recommendations. Containers share the selected server's capacity unless limits are explicitly configured. Cloud plans and VM capacity still apply. Existing saved limits are preserved; select Full capacity to remove an older unwanted limit.

  • 允许并发云提交

    Different projects can submit builds while a sibling build is active. Unspecified resource dimensions remain shared; explicit limits, saved plan concurrency and exclusive maintenance protection remain enforced.

  • 重用有界项目构建缓存

    Compatible builds retain project-owned BuildKit state and supported package/compiler caches while temporary workers are removed. Idle cache collection uses retention targets and storage-pressure checks, preserving active workers, release images and application data.

  • 可选择温暖的新云空间

    Operators can select a provider software disk with public build-image layers for new spaces. Matching images are pinned against their current upstream digest; unavailable or outdated packs fall back to registry resolution. Existing spaces are not reattached by an API redeploy.

  • 显示图像准备正在做什么

    Registry pulls stream progress, preparation heartbeats and elapsed time into deployment logs. Build cleanup waits for tracked Docker commands to acknowledge completion, and static export publication normalizes public file permissions.

目录、GPU 和共享数据库

  • 添加文档、仪表板和媒体应用程序

    Install Paperless-ngx, Wiki.js, Homepage, Immich and Jellyfin using pinned published images, persistent storage and protected initial setup. Homepage does not require a Docker socket.

  • 运行自托管 AI 应用程序

    Ollama offers CPU or one NVIDIA GPU, and Open WebUI connects to an existing backend with protected chat access. These templates use connected self-hosted destinations, not managed Cloud capacity. vLLM remains a disabled preview pending hardware verification.

  • 部署NVIDIA GPU服务

    Compose import, SDK/CLI sync and adoption share validated GPU selection and Docker device requests. Server detection and picker hints help choose a compatible destination. Unsupported or conflicting requests fail before image acquisition or service replacement.

  • 跳过不必要的 WordPress 和 Odoo 构建

    New catalog installs pull the official images and mount setup helpers through the normal deployment engine. Existing installations retain their saved recipes; reviewed catalog repair can update the application service while preserving database siblings, credentials and data.

  • 显式共享本机数据库

    Use in a project can connect ready native PostgreSQL or Redis databases to authorized projects in the same cluster. Saved grants and private network rules are checked together; ownership, backups and database management stay with the source project.

存储、删除和迁移安全

  • 分离新的云应用程序数据

    New logical volume names use immutable project IDs so reinstalling a deleted slug cannot adopt another project's data. Owned legacy mounts and explicitly imported volume identities remain intact.

  • 清晰恢复失败的删除

    Failed first installs offer the existing explicit data-removal option, including owned volumes with no container. Data retention stays the default. Cleanup failures remain retryable operations instead of making a partly deleted project appear Live again.

  • 保留属于其他项目的资源

    Teardown can retain stale Cloud route and network references whose foreign ownership is confirmed. Unreadable or ambiguous ownership still blocks cleanup, and owned networks are removed by immutable identity rather than a potentially reused name.

  • 避免短暂的主机端口冲突

    Docker allocation checks the target kernel's ephemeral range for both saved preferred ports and fresh candidates. Unsafe legacy allocations move to a safe port during deployment; if no safe candidate exists, allocation fails before reserving a replacement.

邮件、安全和本地化

  • 保持网络邮件后端连接

    Webmail deployed on its mail server saves the host-gateway mapping through normal service settings and deployment snapshots while retaining the certificate hostname for TLS. Sign-in connection attempts have bounded timeouts rather than hanging indefinitely.

  • 从云端连接现有邮箱

    The Emails screen installs the standard webmail client for existing IMAP/SMTP servers. It does not provision or administer a self-hosted mail server in Cloud; managed email remains Coming soon.

  • 修复容器化邮件操作

    Boot restores maildir ownership, backups and restores use the actual host-mounted mail path, and fail2ban uses valid nftables syntax and explicit private PostgreSQL sidecar credentials. Database and unban failures no longer report success.

  • 调整收件箱和阅读窗格的大小

    Drag the divider or use its keyboard controls. Desktop widths are remembered separately from the mobile layout.

  • 防止仪表板点击劫持

    Dashboard pages, authentication routes and redirects deny framing through CSP and X-Frame-Options. Customer application routing and headers are unchanged.

  • 扩展翻译后的指南和文档

    Supported dashboard locales include preferences, transfer, jobs, issues, pricing, diagnostics and audit descriptions. The website adds a blog and broader feature discovery, alongside updated catalog, runtime-role, Cloud, API, SDK, CLI and MCP documentation.

在使用需要 0.9.2 的新设置、托管隧道操作或目录配方之前,请更新 API 以及桌面/仪表板客户端。包含的数据库迁移通过正常的 API 启动运行。

10月13日2026v0.9.1特点修复16 更新

该补丁添加了公共应用程序目录、俄语仪表板支持和运行时图像控件。它修复了工作流程保存和云恢复、实时更新网络邮件,并改进了重新部署期间的路由、构建容量和图像处理。这些注释涵盖了自 0.9.0 以来的所有更改。

应用程序、语言和工作流程设置

  • 安装前浏览应用程序

    The public website now has an Apps directory with search, category filters and individual pages showing features, included services and app overviews. Installation opens the existing Cloud setup flow; self-hosted users can follow the installation guide. Returning to the directory preserves search and category selections.

  • 俄语支持

    Select Russian during onboarding or in dashboard language settings. Dashboard translations cover workflow setup, Cloud reconnect and webmail recovery, and a Russian README is available alongside the existing localized introductions.

  • 保存自定义操作工作流程

    New standalone workflows initialize their name from validated YAML, so valid starter workflows can be saved after setup. Missing names, runners, files, source validation or access settings now have inline guidance that leads back to the relevant control or editor. Repository setup also offers a direct custom-workflow option.

云和网络邮件恢复

  • 登录后继续安装应用并选择计划

    App and plan links retain their destination through login, registration, verification, password reset and 2FA. App installation resumes its confirmed configuration, server and existing draft after checkout; failed retries remain recoverable. Plan links select an offer for review, with an explicit action still required to purchase.

  • 重新连接已保存的云服务器链接

    Disconnected links show a Cloud sign-in action, with separate guidance for account mismatches and temporary failures. Live controls wait for a verified connection, and reconnecting reuses the saved server link. Controls missing from an older Cloud API show availability guidance; refreshing retries reads without repeating a write.

  • 恢复现有的网络邮件应用程序

    When a mail registration loses its webmail link, select an accessible existing app on the same mail server and hostname and choose 重新连接并部署。恢复重用项目、凭据和持久卷,同时保留域所有权和权限检查。

运行时配置和部署安全

  • 选择匹配的运行时版本和自定义生产映像

    Generated PHP builds support PHP 8.3 and 8.4 through the generic runtimeVersion 设置。 Docker 源版本提供了高级功能 runtimeImage 覆盖。堆栈选择的配方在激活之前验证实际的运行时功能和兼容性;无效的设置不会部分更新项目,保留映像回滚会保留原始版本和映像配置。

  • 从连接的实例恢复云操作

    Desktop and self-hosted clients forward Cloud workflow and runner operations to their owning Cloud instance, with the same scope and permission checks.

  • 使用服务器的实际可用构建容量

    Automatic Cloud builds account for running workloads and pending CPU reservations before choosing their worker size. Build setup also reports the effective workspace capacity.

  • 重新检查部署运行状况

    Project status and workload selection reuse current startup-health verification while retaining earlier warnings for review.

  • 在 Compose 重新部署期间跟踪当前容器映像

    Cached Docker inventory preserves immutable image identity, so port preflight and rollback can verify running services safely.

  • 接收实时收件箱更改

    Webmail refreshes after IMAP IDLE events, with event streams flushed through buffering proxies and correct folder routing.

  • 简化项目备份页面

    The existing project header supplies its title, removing the duplicated backup heading and description.

  • 验证声明的运行时角色

    Stack-role configuration rejects missing kinds, empty commands, incomplete exec probes and invalid replica counts. This is configuration/detection support for future role execution.

  • 保留仅路由特定路径的域

    Migrations now discover and retain domains with exact or prefix routes and no catch-all service. OpenResty and Cloud routing preserve those paths; unmatched requests return 404. Omitting an existing source catch-all requires a decision before project creation or source container changes. Routing retries keep the previous complete table when a selected upstream is unavailable.

  • 替换服务之前刷新部署映像

    Manual Docker redeploys refresh mutable registry tags while preserving locally built images and pinned rollback artifacts. Full redeploys keep otherwise unchanged external services, including databases, running when their actual image content matches. Docker validates every replacement image and freezes its reference before activating any service; failed preparation leaves existing containers running. Image preparation is all-or-nothing, while container replacement remains sequential rather than a transaction across the whole stack.

10月12日2026v0.9.0特点修复40 更新

OpenShip Actions 将存储库 CI 引入您自己的 Linux 和 macOS 服务器以及云运行器。此版本还允许您在桌面和服务器之间移动 OpenShip 控制平面,添加 GitHub 部署检查和共享通知,并改进云构建计划、路由、监控和网络邮件。这些注释涵盖了自 0.8.2 以来的所有更改。

OpenShip 操作

  • 独立于 GitHub 操作运行 CI

    Workflows in .openship/workflows/ 使用 GitHub 样式的 YAML 并在选定的目标上运行 OpenShip。通过存储库推送或拉取请求、按计划、通过经过身份验证的调度或从作业手动触发它们。 GitHub 可以提供源、事件和提交检查,而无需运行工作流本身。

  • Use existing GitHub workflows with OpenShip runners

    Workflows in .github/workflows/ 保留GitHub的编排、秘密、环境和检查。在 OpenShip 个目的地注册官方跑步者并定位其自托管标签。定位 GitHub 托管标签的作业仍在 GitHub 上运行;导入工作流不会默默地更改其执行平台。

  • 一个工作流程编辑器

    Import multiple workflow files from a repository or create a standalone workflow. Topology, list and YAML views share the same draft. Connected job and step nodes, inline step editing, per-file trigger rules, branch controls and repository-change review keep setup in one flow. Repository sync can apply updates automatically or wait for confirmation.

  • 可重用的工作流程和高级作业

    Local and authorized remote reusable workflows support nested calls, typed inputs, secret forwarding and outputs. Dependencies, matrices, expressions and job permissions use the pinned execution engine rather than a second shell-only workflow implementation. Unsupported constructs return explicit errors instead of being silently skipped.

  • 根据经过验证的能力选择跑步者

    Destinations report operating system, architecture and available tools. Linux runners support container images and explicit QEMU setup for supported cross-architecture execution; macOS runners use native tools. Runner labels and job images are separate settings. Create a runner from the shared server picker without leaving workflow setup.

  • 执行前检查访问权限

    Workflow access can be limited to your account or selected repository users, with approval required for each attempt. Approvals bind the actor, commit, attempt and destinations. Fork code is blocked by default; explicitly approved fork execution uses disposable Cloud runners without privileged secrets or write credentials. Work never falls back to an unselected control-plane host.

  • 跟随跑步而不会失去位置

    Expandable jobs and steps sit beside masked logs, with a topology view and a separate approvals tab. Waiting work has visible progress; selection and log position survive refreshes. Independent runs stream logs in Openship. GitHub-coordinated runs link to live GitHub logs and import completed logs.

  • 工件、缓存和 OIDC

    Independent workflows support artifact/cache actions through scoped storage access and configured backup destinations. Jobs with id-token: write 可以从 HTTPS 实例请求短期 OpenShip OIDC 令牌。身份提供商必须明确信任 OpenShip 颁发者;这些不是 GitHub 发行的代币。签名密钥随实例移动而移动。

  • 知道界限

    Independent execution does not implement GitHub protected environments or attestations. Windows runners and GitHub Enterprise Server are not supported. A fresh independent run does not resume or replace a failed GitHub run. Native runners and runners with a host Docker socket execute trusted code with that server user's access; use disposable VMs for stronger separation.

Cloud Actions 目的地和资金

  • 重用一台服务器或添加一台服务器

    Actions can use an existing authorized Cloud server pool or a dedicated managed server purchased through the normal catalog. These use the server's existing capacity and billing.

  • 每个工作的临时跑步者

    Prepaid Actions profiles provide Linux VMs with 2 vCPU / 4 GiB RAM / 40 GiB disk, 4 / 8 / 80, or 8 / 16 / 160. Executable jobs provision a temporary VM and remove it after cleanup; queued work allocates no VM. Temporary runners use a separate prepaid balance covering provider compute and transfer charges, rather than an application's monthly server allowance.

  • 资金和回收

    $5, $20, $50 And $100 top-ups use hosted checkout. Provider-confirmed payment funds the runner budget; duplicate receipts cannot grant credits twice, and background recovery continues if the browser closes. Setup failures retain paid credit for retry. Pricing and estimated minutes use the provider's current tariff, not guaranteed fixed minutes.

  • 云运营商设置

    Temporary-runner purchases require enabled Cloud billing, provider credentials and live pricing. Regular-server PAYG purchases remain disabled. Verify a real paid Actions top-up before enabling the purchase flow for customers; automated payment recovery tests and live VM execution do not replace that checkout test.

GitHub 检查和通知

  • 默认启用部署检查

    Repository-backed deployments can publish project/environment results and individual service Checks, including deployment failures. Configure the selected Checks and their names or disable reporting from project settings and the project wizard, in self-hosted and Cloud installations.

  • 检查设置显示实际访问权限

    Workflow setup displays the connected GitHub account, repository and access status, with inline connect, review and retry actions. Independent reporting requires a GitHub App with Checks write access; a personal token or CLI source connection alone does not grant it.

  • 添加内联通知渠道

    Create a channel using the shared Settings form, send a test, then select it without leaving the workflow. Unverified channels remain unselected until verification succeeds. Completion notifications cover selected outcomes with durable delivery and retry.

  • 1个通知编辑器

    Instance defaults and project overrides use the same channel controls. Failed preference reads show an error and retry rather than editable empty defaults; account switches discard stale settings.

桌面连接和实例移动

  • 将控制权移至服务器

    Settings → Instance can deploy an API-only instance for Desktop access or an API and dashboard for browser access. Select a connected or managed Cloud server, configure its address and review the move. Projects, users, server connections, credentials, history and settings transfer together while application workloads remain on their existing servers.

  • 使用最新数据向后移动

    A connected Desktop can receive the current remote instance, including changes made on the server. Existing hosted instances can also move to Desktop. Both ends verify compatible versions; interrupted transfers retain a journal and recovery snapshot and can resume without activating two controllers or reverting to stale local data.

  • 无需移动数据即可连接

    Enter an existing instance URL and sign in, or use a short-lived connection code from your signed-in account. Desktop connects to that instance with your permissions; returning to the local instance resumes its separate data.

  • 在桌面中打开的邀请

    Team invitations offer email delivery through the configured mail service or a copyable, recipient-bound link. Links open Desktop when available, with a manual URL fallback. Recipients sign in and review the instance, workspace, inviter and role before accepting. Team and webhook settings link to the same hosted-instance setup when a public control plane is required.

托管云服务器、构建和托管

  • 在一处管理服务器访问

    Managed server tabs expose settings, boot logs, SSH access, temporary credentials, Runtime API token reveal/rotation and manually managed workloads. Outbound internet and hostname allowlists use revision checks and preserve unrelated ingress, routes and private networking.

  • 耐用的构建入场

    Explicitly submitted builds queue against their selected server's saved offer and available resources. Different projects can build concurrently when capacity allows; the same project's builds remain serialized. Queue position, waiting reasons and upgrade actions are visible. Image-only deployments do not reserve a source-build slot.

  • 保存的计划津贴

    New Hobby, Starter, Pro and Scale offers enforce project/app, running-service and build-admission ceilings. Existing purchases retain their saved terms. Physical CPU, free memory and host headroom can admit fewer builds than the plan ceiling; explicit resource requests are not silently reduced. These Cloud quota gates do not apply to self-hosted servers.

  • 安全地恢复中断的构建

    Durable activity ownership coordinates builds, backups and server maintenance across controllers. Capacity is released after tracked commands and Docker-owned BuildKit workers are confirmed stopped. Crash recovery settles interrupted deployment state before acknowledging its execution, preserves live releases and retries failed recovery writes.

  • 静态网站默认为 Cloud Pages

    Build on the selected managed server and publish the static output without retaining an application container. Choose Managed server hosting when an nginx container is preferred. Each release saves its hosting choice for rollback; failed publication preserves the previous site. Backend applications keep their server runtime even when static assets exist.

  • 应用程序启动更可靠

    Generated Node images respect declared Node requirements and explicit image pins. Managed public Node listeners can adapt loopback bindings without exposing private listeners. Cloud verifies startup before reporting container deployments ready and surfaces crash details.

  • 一致的包管理器

    Generated npm, pnpm, Yarn and Bun builds honor explicit versions, supported lockfiles and monorepo parent settings, then verify the executable actually used. Private catalog services retain private access; public services use their selected domains. MinIO installation and required catalog setup are more reliable.

部署、路由和监控修复

  • 明确选择另一个端口

    When a host port is occupied, deployment review can suggest a free alternative and let you confirm it. Existing ports do not change silently. Bare redeployments recognize their own previous release, and private service port access binds to localhost.

  • 保持路由状态一致

    Route repairs update the banner and route cards together, retain repair logs across refreshes and reconnect interrupted streams. Proxy overrides validate target capabilities before saving and preserve existing configuration when unsupported.

  • 在服务边缘验证 Cloud HTTPS

    Custom-domain checks validate the publicly served certificate, hostname and chain rather than relying only on provider metadata. Scheduled checks use bounded work and failure backoff; unavailable observations stay unknown instead of becoming successful results.

  • 区分连接丢失和请求失败

    An API request error no longer marks unrelated services offline. Monitoring retains meaningful last observations, reconnects dropped streams and offers retry for failed reads. Terminals remain usable when status reads fail.

  • 监控中的部署结果

    Projects show completed outcomes and failed deployments alongside application monitoring. Project cards, grids and backup history use more consistent spacing and responsive layouts.

  • 构建和运行时的正确性

    Preserve Dockerfile startup defaults, native service source precedence, case-sensitive manifest names and monorepo Docker build-context metadata. Compose projects keep service detection on redeploy. Exec cancellation reliably reaps watchdog timers, including BusyBox hosts. Cloud cleanup follows the saved keep-resources policy. Shared storage removal keeps Longhorn's bounded native retry for an uninstall startup cache race and waits for confirmed completion before cleanup.

诊断、CLI、SDK 和网络邮件

  • 结构化错误报告

    API boundaries, authorization failures, deployments, jobs, streams and dashboard errors share a classified, redacted event format with request references and bounded asynchronous delivery. Cloud stores sanitized events in its own database. Automatic collection and upload remain disabled for Desktop, self-hosted installations, native workers and CLI, including Desktop connected to Cloud; operational errors still have local logs.

  • 更广泛的自动化覆盖范围

    Native and remote SDK operations cover Actions, instance connections, managed server controls, migrations, mail and terminals. The CLI shares platform contracts, expands Cloud and remote operations, accepts /api 路径和位置环境配对,并在授权失败时引导用户登录。可以通过以下方式执行操作 openship api;此版本没有引入专用的 openship actions 指挥组。

  • 更新文档

    Actions setup, independent versus GitHub execution, runner access, Cloud funding, instance moves and API/SDK/CLI/MCP references cover the new flows, with live execution verification records.

  • 网络邮件改进

    Editable email signatures apply in the composer; replies include the original message body. Sign-in recovery and managed deployments are fixed. Cloud shows mail availability before loading unsupported server controls; Desktop and self-hosted mail remain available.

  • 其他兼容性修复

    Preserve cookie encoding in dashboard server requests, complete partially applied instance-controller migrations, filter invalid custom app templates, and add Farm.js configuration support and its square icon. Whole-instance recovery rebinds the imported local administrator atomically, preventing project reads from failing after a database wipe.

  • 发布验证

    Required gates cover real Linux and macOS Actions execution, instance moves, Docker deployment/rollback, scaling and shared storage, HTTPS, database upgrades and installed SDK packages. Failed release work can resume with verified successful checks and notarization checkpoints.

更新中

Desktop 0.8.2 用户可以使用内置更新程序。 仍在使用 0.8.0 或 0.8.1 的桌面用户必须下载 0.9.0安装程序 并手动安装一次。 退出 OpenShip 并替换应用程序;保留应用程序数据以保留项目、服务器和设置。服务器/CLI 更新路径不需要此桌面恢复步骤。 API和仪表板一起更新;实例移动需要两端兼容的版本。

10月6日2026v0.8.2特点修复3 更新

桌面更新恢复

  • 修复了桌面更新程序中的 GitHub 版本重定向,同时保留受信任的下载主机、SHA-256 检查和发布者签名验证。
  • 在现有的 CI 和发布测试门中添加了真正的 Electron 下载测试,涵盖安装程序和证明重定向、阻止的目的地、重定向循环、取消和不完整下载清理。
  • 此重定向错误会影响桌面安装程序更新程序。服务器/CLI 更新路径是独立的,不需要此手动恢复步骤。

0.8.0 或 0.8.1 上的桌面用户:请手动安装此更新一次。 这些版本中的内置更新程序可能会失败 “重定向已取消”。从以下位置下载适合您的操作系统的安装程序 0.8.2 发布,退出 OpenShip,然后替换已安装的应用程序。保留您的应用程序数据:保留您的本地项目、服务器和设置。后续桌面更新使用固定下载器。

10月6日2026v0.8.1特点修复安全性50 更新

OpenShip Cloud 现在在托管服务器上运行具有自己的每月计划的项目。跨应用程序共享服务器,在需要时添加另一个服务器,并通过桌面或自托管 OpenShip 管理您的云资源以及本地项目。此版本还添加了密钥、身份验证器 2FA 和私人支持收件箱,扩展了 CLI 自动化,并改进了计费、迁移和部署恢复。

托管云服务器

  • 一台服务器,多个项目

    Each managed server has its own subscription and shared CPU, RAM and disk. Builds, applications, Compose stacks and catalog services use the existing Docker and Bare deployment engines. Creating a project no longer allocates a separate VM or reserves another disk (#1036).

  • 选择 Docker 或直接执行

    Use Docker for containers and Compose, or run compatible source applications as supervised host processes with Direct. The shared destination picker can select an existing server or start a purchase for another. New eligible source apps default to Direct below 2 GiB RAM; saved projects and explicit runtime choices are preserved (#1064).

  • 使用您购买的容量

    A service can use the server's full available CPU and RAM, or use a custom container limit. Fractional CPU settings, including Micro, reach Docker correctly. Source builds use available server headroom and optional build caps; image-only installs do not start a source builder. Applications, builds and the operating system still share the host.

  • 与容量分开检查使用情况

    Server monitoring distinguishes the purchased disk size from measured usage. Project containers and volumes have a disk breakdown, with shared images, build cache and system data shown separately. Missing readings stay unknown, and undeployed drafts no longer inflate running-service counts (#1011).

  • 在需要时管理服务器

    Reuse server diagnostics, terminals, listening-port checks and resource views. Networking controls outbound internet access; the Activity tab holds provisioning and resize logs. Scheduled command jobs can target shared or separately subscribed managed servers.

  • 在不丢失邻近项目的情况下恢复运营

    Provisioning, resize and interrupted deployment work retain progress for retry. Resizing restores previously running services while leaving intentionally stopped ones stopped. Project deletion removes its own resources and preserves the shared server; server deletion checks remaining projects and subscription state.

桌面和自托管云帐户 OpenShip

  • 连接时会显示您现有的云资源

    Cloud projects, apps and managed servers join the local inventory. A server already linked to the installation appears once. Cloud-owned settings, deployment history and operations stay in Cloud rather than becoming local project copies (#1074).

  • 从同一仪表板购买和使用托管服务器

    Cloud subscriptions and provisioning remain in Cloud. Local projects can select an authorized managed server through the same destination picker as SSH servers, using an execution link for deployment, logs, terminals, jobs and backups.

  • 账户切换会清除之前账户的状态

    Inventories, project details, deployment history and billing responses follow the selected Cloud account and organization. Connections are revalidated for live operations; locally scoped automation credentials do not inherit the owner's Cloud account.

计费和计划

  • 每月服务器包括其全额付费期

    New monthly plans cover purchased CPU, RAM and storage without a second compute-credit allowance or a monthly build-time cap. New offers have no project or running-service count limit; workloads share the server's physical capacity. Optional managed proxy transfer and storage retained after coverage ends remain separate charges.

  • 修订计划和定制资源

    Hobby is $5/month for 1 vCPU, 4 GiB RAM and 25 GiB disk; Starter is $20 for 2 vCPU, 8 GiB and 32 GiB; Pro is $39 for 4 vCPU, 16 GiB and 128 GiB; Scale is $99 for 8 vCPU, 32 GiB and 256 GiB. Custom lets you choose CPU, RAM and disk and review a quote before checkout.

  • 计费按照所选服务器进行

    Switch servers without losing the page, inspect each subscription independently, or use 获取服务器 购买新产品。首次客户看到的是计划而不是空的使用屏幕。较小的升级比较保留紧凑的卡片和单独的当前计划摘要;付款方式和发票共享服务器的 Stripe 门户。

  • 在应用计划更改之前先审查它们

    Show the provider's prorated amount, effective date and affected projects. Capacity upgrades apply after confirmed payment; resource reductions and billing-mode changes wait until renewal. Pending changes remain visible, and a resize requires restart consent. Disks can grow but cannot shrink in place.

  • 结账有可见的恢复路径

    Payment confirmation, paid coverage and server readiness are separate steps. Setup failures expose progress and retry without asking for another purchase; the welcome dialog appears when setup completes. Unavailable offers show a dedicated dialog with retry and a support request for availability updates (#1062).

  • 恢复或取消未完成的付款

    待付款 列出每个服务器保存的报价并打开其原始结帐。通过提供商确认的取消,您可以选择其他计划或删除未使用的未付费服务器。云和连接的安装共享恢复流程,并且切换帐户会丢弃以前帐户的付款详细信息和响应(#1067)。

  • 预览预付费 PAYG 等级

    Compare three shared resource-pool tiers, configure server resources and select a credit package in one calculator. The estimate separates active vCPU-hours, reserved RAM and storage, with hourly costs and balance-duration scenarios. Enterprise contact is available in both purchase views. PAYG purchases remain disabled in this release (#1057).

帐户安全和 GitHub

  • 密钥和验证器 2FA

    Settings → Security supports passkey registration and removal, authenticator QR setup, and single-use recovery codes. Enabled 2FA also applies after social and passkey sign-in. These controls are available on Cloud and self-hosted installations with local accounts (#984).

  • 帐户保护在故障期间保持一致

    Credential changes commit together, concurrent requests cannot reuse a challenge or recovery code, and password resets do not disable 2FA. OAuth, invitation and MCP handoffs resume after verification. Security setup state clears when the account changes.

  • GitHub 存储库访问与登录无关

    One GitHub identity can authorize repositories for multiple Openship accounts without transferring login ownership. Reconnect existing installations from the shared connection flow, including direct installation links, and see completion or failure for each attempt (#992).

  • 个人令牌在整个存储库流程中工作

    Git settings remain reachable through the alternative connection option. A verified token can supply repository and owner listings and private-source access when no GitHub App connection is available. Account avatars and Git URL entry are clearer.

支持和入职

  • 私有云支持收件箱

    Submit deployment, billing, account or general tickets, search your history, reply and resolve or reopen a conversation. The same personal ticket history is available from Cloud-connected desktop and self-hosted installations. Team membership does not expose another user's tickets (#1073).

  • 支持和联系页面接受持久请求

    Submissions are saved before email delivery, with a receipt and notification to [email protected]。 API 重新启动后仍会重试交付,并且支持回复会显示在收件箱中并通过电子邮件发送给客户。重试提交会重复使用原始收据,而不是创建另一个票证 (#970)。

  • 更清晰的首次运行和帐户屏幕

    Refreshed Cloud plan prompts, purchase welcome dialogs, email-verification and password-reset completion screens. The home page omits empty system-status cards for new Cloud accounts, and already subscribed users do not keep seeing the first-purchase promotion.

应用程序和迁移

  • 应用程序有自己的位置

    A dedicated Apps sidebar entry and list keep catalog applications separate from source projects. Compact home rows, restored empty states and clickable app illustrations make discovery less cluttered.

  • 更一致的部署向导

    Share destination and server controls across Cloud and self-hosted modes, with Full/Custom power choices, filled inputs, compact Build/Start settings, readable deployment-step icons and clearer draft project details. App install forms support grouped and two-column layouts.

  • 应用程序安装解释了路由和资源选择

    Public dashboards start with domain routing and ask for confirmation before continuing without a recommended domain. Self-hosted app CPU/RAM recommendations are advisory; failed Cloud installs can be retried or cleaned up without treating an absent runtime as a teardown failure (#1009, #1016).

  • 将 Docker 个应用程序导入托管云服务器

    Reuse the existing migration engine for images, environment, volumes, bind data and routes. Cloud can connect an external SSH server as a migration-only source. Target preparation, saved progress, verification and explicit cutover support recovery; source data is preserved and source-container retirement requires consent.

  • 以卡片或拓扑形式查看导入

    Compact expandable service cards are the default, with a topology view, expand-all controls, repository linking and clearer Custom, Free and Internal-only routing choices.

构建、部署和恢复

  • 停止取消选定的构建器

    Cancellation reaches the worker's actual Docker or Bare runtime, including remote Git and archive preparation. The UI shows 停止… 直到清理完成,然后允许重新部署。取消构建会保留继承构建标签的已部署容器;不明确的服务所有权仍然会阻止激活(#1059)。

  • 构建输出保持可读

    Cloud Docker streams preserve raw bytes, partial lines, UTF-8 characters and terminal progress updates. Uploads finish correctly when stdin closes. Disk and inode exhaustion are explained separately from memory failures, and temporary BuildKit cache is reclaimed after builds (#1058, #1064).

  • 不变的 Compose 服务保持运行

    Folder uploads and snapshot syncs no longer mark unchanged image services dirty. Import metadata preserves concurrent configuration edits; inherited project resource changes still apply while respecting per-service overrides (#989).

  • 预部署备份在激活前完成

    Deployments wait for all configured pre-deploy backups and their cleanup, including when reusing a build. Failed backups offer retry, an explicit skip or stop. PostgreSQL dumps must succeed, and suspiciously small dumps are rejected against recent comparable backups before becoming restore points (#1060).

  • 远程构建和静态发布使用正确的路径

    Subfolder refreshes preserve root manifests and rescan at the project root. Static output resolves relative to that root, and retained artifacts are checked on their deployment destination for rollback. Directory-only .dockerignore 否定被尊重(#1010,#1041)。

  • 健康检查和关闭尊重运行时

    Configured single-app readiness probes run through the deployment server; unreachable SSH leaves a check unverified. Docker replacement honors stop signals and grace periods, probe watchdogs are reaped, and Bare services retain the correct user privileges and artifact ownership (#1043).

  • Farm.js检测

    Identify Farm.js applications and supply the framework's build and output defaults (#1037).

域、网络和监控

  • 免费域名遵循所选的托管服务器

    Availability and quota checks retain the destination through project creation, Compose synchronization and deployment. Route changes are validated before related settings are saved; editing an existing route at the limit does not count it as a new route (#1064).

  • 通过域设置连接 Cloudflare

    Add and verify a DNS credential without leaving the DNS panel, review proposed records, then apply them. Cloudflare TXT quoting and Cloud certificate-status handling are corrected, while certificate checks verify the domain's project binding (#977).

  • 更可靠的通配符 HTTPS 和边缘恢复

    DNS challenge hooks pass Certbot validation, Compose installations detect Edge correctly, and challenge route cleanup checks ownership. Whole-project rules handle a null path prefix correctly. Projects no longer have the unrelated 20-public-endpoint schema cap (#1054, #1003, #1017, #1045).

  • 在部署完成之前,源更新保持可见

    The project deployment tab indicates available updates; unchanged image services are not refreshed unnecessarily. Updates on the local Openship instance use the appropriate advisory flow, and resource reporting accepts current Docker runtime limits (#1006, #1047).

  • 连接和设置修复

    Recover Cloud Docker connections after credential rotation, report missing proxy/bridge failures clearly, correct registry TLS/WebSocket dependency compatibility, and handle Docker networks without subnets during cluster setup (#970, #1068, #961).

SDK、CLI 和平台修复

  • 通过 Ship SDK 和 CLI 进行更多管理

    Add commands for project resources, environments, storage and connections; credentials and DNS; monitoring, notifications and webhooks; workspace access and audit history. They use the shared platform operations and permission checks.

  • 更安全的命令定位和环境编辑

    Each CLI invocation keeps its selected endpoint, credential and organization. Directory links reject mismatched contexts. Partial service environment edits preserve other values and secret classification; full replacement is explicit. Deployment waits have deadlines and expose pending decisions, and request logs can be followed through the SDK's authorized Cloud stream.

  • 更清晰的 MCP 云工作流程

    Discover authorized managed destinations and deploy desktop folders through a connected server. Explicit promotion to Cloud can resume from its saved receipt after an interrupted response or cleanup, without importing the project again (#1056).

  • 网络邮件和仪表板修复

    Spam, Not spam and Archive move messages into the correct IMAP folders. Notification settings and icons recover from hydration races, Teams accepts current Microsoft webhook hosts, member-access settings avoid repeated refetches, and background project deletion preserves navigation (#981, #1004, #1008, #1035, #1024, #1066).

  • API 启动和批量操作验证

    Capacity previews pass the startup permission scan, and malformed bulk container requests are rejected instead of being interpreted as an empty request (#1033, #994).

  • 可选的云产品分析

    The hosted Cloud API can send configured PostHog events for signup, deployment and verified checkout/payment outcomes. Delivery is queued separately from those operations. Telemetry runs only on the hosted Cloud API; local operations, logs, secrets and session recordings are excluded.

数据传输和升级注意事项

  • 完整、便携式导出

    Instance and project archives include plaintext environment values, server keys and credentials by default, without an export password. Treat the archive as sensitive or explicitly omit secrets. Imports still accept older encrypted archives and encrypt credentials with the destination's key.

  • 导入保留范围和选定的数据

    Instance imports default to full replacement after confirmation. Project overwrite removes destination-only records in selected categories and applies cleared credentials atomically. Project analytics retain normalized hostnames, including www;在更改数据之前,不支持的存档字段将被拒绝。

  • 连接客户端之前升级云

    New inventory and support features require the matching Cloud API. Desktop-initiated cancellation fixes require an updated desktop controller. Existing per-project Cloud deployments need an explicit migration to managed servers; updating alone does not consolidate VMs or replace saved subscription terms.

  • 保持账户安全配置稳定

    Self-hosted passkeys require HTTPS and a stable dashboard hostname through OPENSHIP_PUBLIC_URL (支持 localhost 进行开发)。保留并备份 BETTER_AUTH_SECRET,它保护身份验证器秘密和恢复代码。

9月27日2026v0.8.0特点修复安全性62 更新

在您自己的服务器上扩展应用程序 PostgreSQL 和 Redis,通过专用网络连接这些服务器,并在应用程序实例之间共享文件。此版本还添加了 Node.js SDK,扩展了 MCP 自动化,刷新了仪表板和桌面体验,并带来了自 0.7.2 以来积累的部署、环境、路由、备份、邮件和安全修复。

服务器集群和专用网络

  • 跨提供商连接服务器

    Register and verify an existing private network or prepare an Openship-managed WireGuard network across your servers. Provider network groups retain their provider and network details; managed networking also supports custom infrastructure (#899, #900).

  • 网络和计算集群有不同的职责

    The Networking tab owns addresses, connectivity and network operations. The Clusters tab groups selected servers from a private network and manages the runtime used by their projects.

  • 选择哪些服务器可以互相访问

    Edit connections in the network topology, allow traffic in both directions or one direction, or remove a connection. Openship enforces the private-access policy on supported hosts and shows the provider firewall rules to apply before setup. Cluster setup checks that its selected servers have the bidirectional connectivity it requires.

  • 从拓扑测试网络

    On-demand checks verify allowed paths and confirm that denied directions reject new connections. Results include TCP/UDP reachability, MTU, round-trip latency, loss and jitter; a selected pair can run a bounded throughput test. Saved results remain available for diagnosis.

  • 准备、审查、重试和清理网络更改

    Missing prerequisites can be installed automatically, address allocation and firewall requirements are reviewed before apply, and reconnectable progress includes per-server steps and errors. Interrupted work exposes explicit retry or rollback. Failed members can be removed from setup, and removal reverts owned network changes.

  • 准备服务器以进行应用程序扩展

    Self-hosted and desktop controllers install k3s under the hood, join the selected SSH servers, and verify node readiness, pod traffic, service routing and internal DNS. Saved progress supports retry after failure or interruption; runtime removal checks dependent workloads and owned infrastructure first (#912).

应用扩展

  • 在您的服务器上运行应用程序或工作线程

    Select a prepared cluster, publish the application's image to a shared registry, and deploy through the normal project flow. Set 1–100 replicas; subsequent replica changes reuse the active immutable image without rebuilding. Openship Edge routes public requests to the application, and the topology shows observed instances, placement and readiness.

  • 更新、回滚和恢复正在运行的应用程序

    Cluster deployments retain image history for rollback, and failed or cancelled candidate releases preserve the active release. Kubernetes replaces failed instances within the prepared cluster and routes to surviving ready instances after detecting an unavailable worker. Revision checks reject stale changes to a running project.

  • 在应用程序实例中挂载共享文件

    Project-owned shared volumes can be attached at configured paths, including read-only mounts. Instances on different servers can read and write the same files; existing node-local mounts require a separate data migration.

数据库和共享存储

  • 选择独立或集群 PostgreSQL

    Managed databases have their own resources, progress, credentials and lifecycle. PostgreSQL clusters provide replicas, primary recovery, and private read/write and read-only endpoints. The database controller owns replication and failover independently of the application's replica count.

  • 独立或作为集群运行 Redis

    Redis clusters distribute data across shards with replicas. Grow or reduce the shard count after reviewing the change and taking a verified recent backup. Redis Cluster requires a cluster-aware client; resizing checks real cluster health and slot ownership.

  • 备份和恢复PostgreSQL和Redis

    Configure an eligible S3 destination for manual, hourly or daily backups. Restore a verified archive into a separate database, inspect it, then explicitly replace the application's saved connection and redeploy. Redis archives preserve values and expiry and are consistent per shard, rather than one transaction across all shards.

  • 导入现有数据库并进行 PostgreSQL 次升级

    Import eligible Docker PostgreSQL or Redis backups while the original application remains on Docker. PostgreSQL 17-to-18 upgrades create a separate logical copy for checking before connection replacement. Source data remains available; changes after the captured recovery point need a fresh capture before final cutover.

  • 通过独立磁盘副本共享文件

    Enable shared storage on at least two independent servers, choose two or three copies, and create project-owned volumes. Inspect attachment and copy health, grow a mounted volume, and rebuild a lost disk copy.

  • 从集群外部恢复文件

    Take manual or scheduled external backups and restore them into a new shared volume. Archives remain discoverable after deleting the original volume or removing empty shared storage; archive deletion is an explicit separate action.

  • 删除数据库时保留数据

    Removal can retain its data for later recovery or explicitly delete it. Application, volume, storage and runtime cleanup enforce dependencies and ownership, so an unfinished cleanup or retained database cannot silently lose the infrastructure it still needs.

SDK、CLI 和 MCP

  • CLI 旁边的 Node.js SDK

    该 openship 包现在提供 OpenshipClient 通过 openship/client 用于远程安装和 createShip 通过 openship/native 适用于没有单独 API 服务器的嵌入式引擎。 Both use shared platform operations, validation and authorization. Native instances have explicit start/close lifecycles and verified workspace scopes; Node.js 22 及更高版本支持 ESM 和 CommonJS (#887)。

  • MCP 涵盖更多的运营生命周期

    Networking, cluster setup, replica scaling, managed databases, shared files, backup/restore, migration, routing and diagnostics have documented tools and ordered workflow prompts. Discovery respects workspace permissions and instance mode; required arguments and DELETE bodies survive dispatch, and path arguments cannot redirect a call to another route. Generated API, CLI and MCP references describe the available operations and explicitly excluded HTTP-only routes (#953).

  • CLI 工作流程使用共享 SDK

    Native mode and remote clients share deployment and source handling, and Jobs now has commands for its existing management and execution flows. Re-login preserves custom context endpoints, folder uploads require explicit opt-in, project display names can be changed safely, and failed component installation returns a failure to the caller.

部署和构建

  • 激活前运行发布命令

    Configure releaseCommands 在构建设置中, openship.json 或项目 API/SDK。命令在构建后按顺序运行,使用候选版本的环境,具有流式日志和每个命令十分钟的预算。失败、超时或取消会停止激活。支持单应用 Docker 和裸部署;不支持的部署类型拒绝配置的命令。回滚会跳过它们,并且回滚应用程序代码不会撤消数据库更改(#592)。

  • 完成和经过的时间在重试和刷新后仍然有效

    Workers retry a failed database completion acknowledgement without repeating deployment work. Cancellation records its outcome and duration atomically; late worker results cannot replace them. Both build views use the same persisted timing, including queued starts, rejected retries and terminal events (#940).

  • 回滚保留有一个可预测的限制

    Project → Advanced → Rollback history defaults to five past deployments, with active and pinned deployments kept in addition. Cleanup runs after deployment and retention changes, retries failed removals, and preserves artifacts still referenced by another retained release. Older history remains browsable with pagination and accurate snapshot labels.

  • 更可靠的源构建

    Recursive Git submodules are fetched for build checkouts; Ruby builds respect declared versions and preserve Rails storage; PHP builds include EXIF and package assets needed by frontend builds. JavaScript PORT 检测到分配,拒绝无效的空 monorepo 创建,并且构建时服务 DNS 失败会收到可操作的解释。

  • 部署错误到达 UI

    Rejected submissions show the API's specific validation or configuration error. Build streams reconnect without replaying output, and successful deployments can show live service logs. Preview variable sets cannot be deployed onto a production project's runtime.

环境和撰写

  • 保存的服务变量保持可见

    The Environment tab reads effective values from Openship, including Compose values, shared project variables and explicit service overrides, with their sources. It remains usable when the server is offline. Saves update only edited rows, preserve untouched secrets, reject conflicting edits and remove an override by restoring inheritance where available (#926).

  • 撰写更新无需常规审批即可应用

    Repository changes merge automatically while explicit operator overrides remain. Saved environment values survive omitted source keys, unresolved expressions and legacy review resolution. Interpolation uses current configured values instead of stale scan results; legacy pending reviews reconcile on redeploy (#893, #916).

  • 有意恢复并应用环境更改

    Older or migrated services can recover missing variables from their running container for review and saving, without overwriting saved values. Apply compares against the running service and recreates supported Docker services from their existing image, retaining ports, networks, mounts and resource limits. Failed startup restores the previous container; unavailable comparisons remain unknown, and unsupported runtimes direct the operator to redeploy.

  • 环境下载及保密保护

    Download .env exports the listed values, including saved secrets, using quoting that round-trips through Upload .env. Inline service environment, build arguments and their saved deployment/Compose snapshots are now encrypted at rest; API presentation masks protected values and preserves them on round trips (#844).

迁移和可移植性

  • Compose 迁移包括域切换

    Discovery reports existing proxies and matches Traefik routes through private container addresses as well as published ports. The wizard saves service environment and selected routes, prepares Edge during migration, and requests confirmation before taking over an existing proxy. Selected sites attach to their migrated services, existing certificates are reused, and unresolved routing prevents automatic source container removal (#905, #908).

  • 跨项目重用服务

    Shared service connections retain the service's owner, data and connection settings instead of duplicating it. Existing Docker private links require separate migration when moving an application to a cluster.

  • 导出项目的配置、环境和凭据

    Project settings download a portable plaintext file without a passphrase. The export identifies its server and Cloud dependencies; import previews the contents and requires explicit target mappings. Runtime data stays on its original server, and Cloud projects require the same Openship Cloud account. Imported credentials are encrypted with the destination instance's key. Configuration transfer does not copy runtime volumes or perform a whole-instance server cutover.

域名和证书

  • 具有自动 DNS 或手动 TXT 验证的通配符 HTTPS

    Project and service domains such as *.example.com 现在打开内联证书设置。连接的 DNS 提供商自动进行验证;手动 TXT 订单在重新连接和控制器重新启动时保留其进度。 API、SDK 和 MCP 共享相同的启动、状态、检查和取消操作。现有证书在尝试失败后仍然有效,并且只有在其路由处于活动状态后,HTTPS 才会报告准备就绪。手动证书包括所有九种仪表板语言的续订指南(#954)。

  • 管理多个通配符域

    Configure wildcard domains in Settings and choose the domain to use during project setup (#819).

  • 路由重试协调保存状态和实时状态

    Retry routing checks Edge, reapplies project routes and synchronizes domains, with inline progress logs and refreshed results. Live ownership checks recover stale hostname/host-port reservations left by deleted or recreated projects. Repairs preserve complete routes and canonical endpoints when aliases are removed (#915, #922, #925).

  • 待定状态解释接下来会发生什么

    Domain details distinguish verification in progress, scheduled retry and failure, show the reason and next retry time, and offer a manual retry. Durable backoff prevents overlapping background sweeps from repeatedly retrying the same domain. An SSH observation failure no longer clears a working certificate or becomes a claim that HTTPS is absent (#911, #922).

  • 导入的证书和容器路由正确恢复

    Certificate lookup follows managed lineages and avoids collisions after import; recovery excludes ACME challenge ports from application upstreams. Static sites inside containers route through their owning service, and Edge serves an Openship error page for unavailable upstreams (#879, #913).

备份和恢复

  • 立即从项目、服务或卷面板备份

    Service shortcuts reuse an applicable policy and run only the selected service. Project policies skip stateless services and admit their eligible runs together. Progress shows saved phases, elapsed time and transferred bytes, reconnects across workers, and updates recent history even after the progress view is dismissed.

  • 可选增量备份

    Policies can reuse verified unchanged blocks, with a complete block index for each restore point. Retention preserves blocks still referenced by another snapshot, and storage totals count shared objects once. Full backups remain the default. Captures still scan the whole source and transfer through the Openship backup worker.

  • 保留和目的地保持一致

    Pruning runs after successful capture and through the scheduled sweep, preserving protected copies and backups used by active restores. Existing runs retain their original destination when a policy changes, and failed cleanup remains retryable without invalidating a successful backup. SFTP failures close streams and clean partial uploads instead of leaving the worker stuck (#817).

  • 替换数据之前恢复验证

    Preparation and confirmed apply share source/target checks, integrity verification and exclusive access to the project or mail server. Runtime/stop failures abort before destructive writes; partial-write failures are reported and do not automatically restart a service on incomplete volume data. Redis/Valkey restore validates persistence settings, and PostgreSQL restore uses a transaction for each supported artifact. Release tests now exercise backup, incremental reuse, retention and restore with real Docker volumes and databases (#892, #946).

GitHub 和访问权限

  • 云 GitHub 连接在仪表板中完成

    Installation completion refreshes repository access and the connection state instead of leaving the page loading after GitHub has finished. Device sign-in keeps its code and instructions visible until completion; transient and rate-limit failures no longer discard durable credentials (#920, #951).

  • 存储库选择保持同步

    Branches load on demand while keeping selection and keyboard focus, and changing the branch rescans deployment configuration. Partially successful push-webhook dispatches retry failed targets without redeploying targets that already completed (#847, #870).

  • 登录和邀请遵循配置的流程

    Clients can discover enabled login providers, and signed-out invitees can reach account creation and complete acceptance without the dashboard's prior navigation race.

仪表板和桌面

  • 共享图标和更一致的布局

    Dashboard and desktop use a theme-aware icon catalog with bundled local assets. Service headers, tabs, environment controls, volume forms, source settings and log controls have consistent spacing and typography; mobile navigation and crowded rows are improved (#942, #946).

  • 拓扑保留在项目内部

    The graph has an optional expanded view, improved loading placeholders and compact service nodes. Clicking a node opens its details directly; long runtime identifiers truncate with copy actions rather than widening the panel.

  • 部署页面将操作和日志放在第一位

    Open site and Open project remain prominent, multiple exposed domains can be selected, and preparation, service status and single-app steps share clearer progress indicators. Logs have bounded layout, search and copy controls; history filters survive returning from a deployment.

  • 备份页面显示保留的数据和实际运行状态

    Global and destination views share paginated history, restore actions and usage information. Successful retained copies, active attempts and physical storage totals are distinguished; history remains available after policy changes.

  • 桌面启动遵循应用程序主题

    A redesigned loading screen uses shared colors, clearer progress and service startup states (#952).

监控和运行时可靠性

  • 连接中断后监控恢复

    Desktop connectivity loss is distinguished from a confirmed remote runtime failure, with recheck and reconnection handling. Overlapping status requests no longer stop polling or replace newer results, and issue feeds remain available when a host adapter cannot start. Services show a checking state while runtime status is unknown (#927, #949, #951).

  • 流量视图使用相同的时间序列

    Overview and monitoring render timestamped request buckets with clear time ranges, area/column views and loading skeletons. Analytics failures stay within the affected view instead of appearing as empty traffic or replacing fresh data with stale responses.

  • 长期运行的资源受到限制并被释放

    Container log retention is bounded for newly created managed containers, session caches preserve active work at capacity, and closed log, terminal and IMAP streams release their subscriptions. Busy builds retain their SSH transport; abandoned terminal handshakes release their slots and resumed shells remain bound to the authorized target (#950, #951).

  • 服务器管理报告可操作的故障

    MacOS hosts expose system statistics, server responses match shared diagnostics contracts, and deletion refuses hosts with active deployments. SSH group refresh preserves active sessions after Docker installation.

云和API

  • 云计费遵循所选组织

    Plans, checkout, credit top-ups and renewal management use Oblien namespace entitlements. Purchased limits survive catalog changes, deployment/recovery checks enforce available capacity, and checkout completion verifies payment delivery rather than trusting the return URL. Billing portals remain scoped to the organization (#910).

  • 独立 API 限制未经身份验证的洪水

    A separate per-IP guard runs before authentication without consuming the route's own limit. Cloud mode or explicit OPENSHIP_TRUST_EDGE=true 将外部上限委托给上游代理,同时保留每条路由的限制(#123)。

邮件

  • 检查并更新邮件客户端实际使用的证书

    Mail settings show expiry and the certificates served by SMTP and IMAP, with actions to check and renew them. Successful renewal reloads Postfix and Dovecot and verifies the served certificates. Automatic renewal uses the shared scheduler; expiry, renewal failures and stale served certificates appear in Health and Monitoring. Scheduled renewal requires the Openship controller to remain running.

  • Webmail 刷新,无需重复订阅

    Inbox updates use a single owned SSE/IMAP IDLE connection with cleanup on disconnect. Replies fill recipients and subject correctly, Trash uses IMAP deletion, and mobile composer, accessibility and browser-cache failures are corrected (#897, #904, #921, #950).

  • 远程内容阻止还涵盖 CSS

    Disabling remote images prevents CSS imports and URL-based fetches from leaking a read receipt (#220).

  • 邮件设置、传送和警报更加可靠

    Setup distinguishes an unverified public SMTP probe from a stopped server; database port selection handles conflicts; mounted certificates and Amavis state recover on restart. Relay TLS and SES MAIL FROM checks are corrected, delivery health evaluates the full queue, and captured messages remain until notification delivery is durably queued. Job and backup notifications include their relevant target, outcome and log details (#834, #865, #867, #945, #951).

发布检查

  • 使用更新的代码继续未发布的版本

    Reuse successful whole checks only when their source and workflow inputs match, and rerun failed or affected checks. Artifact reuse verifies the original run and immutable artifact identity; concurrent tag changes and earlier publishing attempts prevent unsafe continuation.

  • 真实的应用程序、数据库和共享存储接受之旅

    Release checks exercise MCP dispatch, image publication, deployment, public routing, scaling, updates, rollback, worker recovery and project cleanup. Separate database tests verify real queries, replica/shard changes, backups, restores, imports and upgraded copies. Shared-storage tests use independent Linux VMs for SSH installation, cross-server writes, volume growth, disk-copy rebuilding and external backup recovery. These heavier journeys run in the release gate or on demand.

升级注意事项

  • 此版本中的扩展范围

    Cluster management is available from self-hosted and desktop controllers. Application scaling supports single apps and workers with project-owned shared files. Compose application scaling, CPU/traffic-driven autoscaling, automatic server provisioning and live cluster membership changes are not included.

  • 将数据库和加密密钥放在一起

    This release includes database migrations and converts legacy plaintext service configuration when the engine starts. Back up the database and retain the instance encryption key (BETTER_AUTH_SECRET 对于 API 安装)在升级之前。降级到此保护之前的版本需要其匹配的数据库备份。在具有不同密钥的实例之间移动配置时,使用包含机密的数据传输。

9月5日2026v0.7.2特点修复Breaking1更新

用于 Docker 构建可靠性的软维护补丁。没有重大 API 更改或数据库迁移。

构建

  • 诊断日志文本不再拒绝成功的 Docker 构建

    Fixes a regression present in 0.7.1 where successful workspace scripts reporting Exited with code 0 可能会导致部署失败 (#832)。对于经典构建器和 BuildKit 构建器,单映像和 Compose 构建现在可以区分应用程序输出中的 Docker 引擎错误。诊断提示丰富了真实的故障,而不会覆盖成功完成或隐藏 Docker 的错误; SSH 构建继续使用命令的退出状态。取消和不活动保障措施仍然有效。

9月4日2026v0.7.1特点修复安全性24 更新

此版本强化了整个部署生命周期,使 Compose 协调无损,完成远程服务器设置和 CLI 定位,修复外部邮件运行状况和管理,并交付自 0.6.9 以来积累的邀请、DNS、目录路由和更新体验工作。

源头控制

  • 自托管工作区可以拥有和管理多个 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 on openship.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)。

8月30日2026v0.6.9特点7 更新

此重要的部署安全修补程序使旧的 Docker Compose 所有权和路由无法关闭。现有的非托管堆栈不会再被误认为是 OpenShip 部署或静默复制,并且普通的同一服务器重新部署无法将路由服务移至不同的主机端口。

部署和路由

  • 现有的 Compose 堆栈永远不会被隐式采用

    Before changing containers or routes, a normal deployment checks the target for an untracked Docker Compose stack with the same project slug and service names. A collision now stops with FOREIGN_COMPOSE_STACK 并告诉操作员导入/采用、删除或重命名它。显式采用的容器和已由 OpenShip 跟踪的容器正常继续。

  • 同一服务器主机端口在重新部署期间保持锁定

    A routed service keeps its active host port on its current physical server. If that port cannot be reclaimed safely, deployment stops before routing changes instead of allocating a new port and leaving the public hostname pointed at the wrong workload. A real server migration may still allocate a new host port.

  • 重复容器警告需要所有权证据

    Normal projects no longer claim same-slug containers through Docker Compose labels alone. Native Openship labels, the canonical managed name, or the tracked container id establish ownership; Compose-label recovery remains available only for an explicit adoption.

撰写对账

  • 遗留解析器元数据不会产生错误的存储库漂移

    Adding environment/build-argument template provenance to an older service baseline is treated as a one-time metadata upgrade, not as a Compose edit. Real changes arriving with that metadata are still reported, and operator-edited live values remain intact while the baseline advances.

监控

  • 问题现在是监控工作区

    The dashboard adds a Health view for every tracked project service, with fleet counts and state charts for healthy, unhealthy, crash-looping, down, and unknown workloads. Rows show the serving server and last observation, and link back to the service that owns the container.

  • 健康读取重用现有的观察者

    The page reads an in-memory snapshot produced by the grouped health sweep and Docker-event accelerator; it does not create a poller per container or perform Docker I/O on page refresh. Per-service monitoring can be disabled before the workload enters the watch, inspection, event, or notification path.

  • 车队更新和重新扫描在后台继续进行

    Bulk component updates start together without holding a modal open, retain their durable sessions across navigation and refresh, and allow an operator to reattach to a specific log. The checker batch similarly exposes one shared progress session so multiple tabs cannot multiply Git, DNS, Docker, or version scans.

Upgrade priority: critical for legacy or externally created Compose > workloads. Fully tracked Openship deployments are not expected to hit the > collision path, but installations that previously deployed a same-slug stack > outside the current control-plane records should upgrade before redeploying it.

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

Compose 项目现在部署为它们声明的服务,其构建参数和动态环境从导入到回滚都完好无损。实例移动可以直接从一个自托管安装转移到另一个自托管安装,而无需复制加密密钥,并且文件工作流程会显示并过滤它将携带的内容。此版本还强化了跨 Linux 和 macOS 的自定义域所有权、主机端口分配、Git 凭据边界以及边缘恢复。

实例转移

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

    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).

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

邮件学会接收,第三方机密被泄露。 OpenShip 邮件现在可以捕获、过滤和读取入站邮件,到达的邮件可以发出通知。除此之外,单个组织范围的凭证存储取代了一次性 DNS 令牌表,并解锁了任何主机上的私有映像拉取。应用程序目录可端到端安装,审核日志从“设置”移至其自己的页面,并且上传在 1 MB 时停止失败。

安全性

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

    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 已经部署了重复数据删除。

8月11日2026v0.6.5特点修复安全性73 更新

硬化和伸展释放。报告的安全问题已得到修复(请参阅下面的安全性),容器→主机控制通道已进行端到端配置和诊断,而不是静静地失败,并且 OpenShip 现在可以安装在任何主流 Linux 上 - 以及您不以 root 身份登录的主机上。它还添加了 openship edge (来自终端的整个反向代理)、尊重您拥有的计算机的实际资源限制、具有拆分出站投递功能的 OpenShip 邮件产品 shell、重建为普通目录应用程序的网络邮件以及五个新的一键式应用程序。

安全性

  • 安全修复

    This release resolves a number of reported security issues, with regression tests added for each. Areas touched: authorization on instance-wide and GitHub operations, access-token minting, path handling, the mail engine, webmail's HTML sanitizer, the desktop shell, and redaction in stored build output. Details are published as advisories on the repository. 建议升级。

  • 硬化

    Host-control operations are pinned to the host channel rather than defaulting to the API process's own container, cloud builds can never run on the API host, and stored SSH key material is encrypted at rest and stripped from any cross-host export.

主机控制通道

  • openship up 提供容器→主机通道,并在无法提供时告诉您

    When Openship runs in Docker, a handful of operations are genuinely host-level (freeing a foreign proxy off :80/:443、主机系统配置、邮件引擎、编写目录应用程序生成的配置),并且它们通过内部网桥上的 SSH 到达主机。现在安装生成密钥,附加受限制的 from=- 固定 authorized_keys 行,检查 sshd 是否侦听容器可以到达的地址,在主机运行的任何防火墙中打开端口,并验证往返 - 而不是在几周后的第一次主机操作上报告成功和失败。

  • 它会探测每一层,因为故障看起来没什么

    This address is host-local, so it traverses filter/INPUT 其中默认拒绝 ufw 生活;已发布的容器端口经过 DNAT 处理并跳过它,这正是为什么堆栈的其余部分看起来很健康,而这个通道挂起的原因。防火墙、sshd 监听地址、密钥和可达性均被单独探测和报告。

  • 一种解释,五个表面

    The CLI preflight, the API's boot banner, openship doctor、仪表板的服务器横幅以及主机操作死掉的部署日志已经转移到不同的故事中。他们现在从一个共享的词汇中读取内容,因为每一行要么是“你的安装没问题,这个功能不行”,要么是“你的安装坏了”——读错了的操作员要么拆掉一个正在工作的盒子,要么忽略一个失效的功能几个月。

  • openship update 修复未配置的通道

    An install from before this work, or a raw docker compose 安装,可以通过更新修复到位,而不是重新运行 up 并冒着环境风险。需要通道的部署在每次部署之前在扇出之前发出一次通知,而不是每个服务一次。

  • 该频道必须是root,并这么说

    An operation that needs a root-owned path fails with the actual cause instead of mkdir: cannot create directory '/root': Permission denied.

  • 记录了手动安装

    .env.example 详细说明所有五个步骤(密钥、受限授权密钥行、sshd 侦听地址、防火墙规则、重新创建 api,因为 env_file: 在容器创建时读取),以及一个新的 故障排除页面 步行修复。

任何 Linux 以及非 root 的主机

  • OpenShip 安装在它一直声称的发行版上

    Docker installation was curl get.docker.com | sh 在每个 Linux 上,都有一个硬拒绝 Amazon Linux、AlmaLinux、Oracle Linux 和 Alpine 的脚本。每个调用站点都有自己的包管理器表(有五个,但他们不同意),自己的 systemd 测试,以及自己对“我的白名单之外的主机”的解读 - 总是“无事可做”。主机事实现在来自一个检测器,作用于它们的命令位于一个模块中,添加发行版是一种编译错误,而不是静默的无操作。

  • 工作中的 Docker 引擎永远不会被隐式替换

    Only an explicit reinstall overrides an engine that's already running, and an installer that skips an already-working component says so instead of leaving the one actionable line nowhere at all.

  • 以非 root 用户身份进行部署是可行的

    Three layers answered "may I do root-owned work here?" differently: component installs gated properly, toolchain installs never gated at all, and the server state store assumed the login was root. There's now one privilege resolver, and it elevates the write rather than the verify (so a sudo shell 永远不会解析不同的 $HOME)。无法报告 uid 的强制命令主机不再被告知“以 root 身份连接”,这与其修复相反。

  • 语言工具链按主机安装,而不是按假设安装

    The toolchain catalog and installer were rewritten onto the same host profile, so a bare-metal build on a non-Debian box gets its runtime installed instead of a not found 在构建时。

`openship edge`

  • 整个反向代理,从终端

    A new top-level command: edge up 代理站起来并提供服务 :80/:443, edge migrate 接管现有的 nginx/Apache/Caddy 并导入其站点, edge takeover 和 edge free 声称拥有港口, edge sites 列出可以导入的内容,以及 edge repair 诊断它不服务的原因(--fix 解决端口冲突)。

  • 无需打开仪表板即可了解域、规则和流量

    edge domains add app.example.com --port 8080 针对端口注册主机名并颁发证书; edge rules 管理每条路线的速率限制、禁令和地理/CIDR 访问;和 edge traffic, edge analytics 和 edge logs 读取代理已经记录的内容。主机操作仅限于 Linux;控制平面部分可以在任何机器(包括桌面)上运行,无论上下文处于活动状态。

  • 记录为参考和演练

    A new 边缘 任务指南和完整的 命令参考.

资源限制

  • 自托管容器默认无限制

    A self-hosted project silently inherited the cloud free tier (0.5 vCPU · 512 MB) and OOM-killed memory-hungry images. On your own box the container's real ceiling is the machine, so 0 (无限制)现在是默认设置,每个消费者在应用上限之前都会测试限制。

  • 定制上限以实际机器为准

    Caps were validated against hardcoded constants (4 cores / 8192 MB), so a 64 GB box could not be told to give a container more than 8 GB. The ceiling is read from the Docker daemon's own /info (NCPU, MemTotal) — 对于本地套接字和池化 SSH 桥上的远程守护程序来说是相同的 — 当无法访问 Docker 时回退到操作系统。云没有变化:计量工作区的大小仍然根据层表确定。

  • 预检部署目标容量

    A cap larger than the host can allocate is rejected before any build work starts, with the machine's real numbers in the message.

OpenShip 邮件

  • 将实例作为邮件产品运行

    An instance can present itself as Openship Mail (OPENSHIP_PRODUCT,或设置中的切换):左栏成为邮件控制平面 - 十个管理选项卡提升为跨三个标题的导航条目,加上操作员仍然需要的主机和设置行 - 并且平台导航被隐藏。这只是演示,绝不是授权边界:Webmail 仍然通过普通项目管道进行部署,因此平台端点保持活动状态。云始终是完整的平台。

  • 在邮件服务器之间切换

    The mail surfaces are scoped to a selected server rather than assuming one, with a switcher in the shell and the scope carried through the admin tabs.

  • 出站中继提供商是真实身份

    The relay code carried a "ses" | "custom" 联合,因此 SendGrid、Mailgun 和 Postmark 在保存时就失去了身份:不包括 SPF,UI 中没有往返,添加提供程序意味着编辑 if 在服务中,DNS 构建器和扫描器。每个提供商的事实现在是所有三个都读取的数据,并且拆分交付(在这里接收,通过其他人发送)是一流的设置。

  • “邮件真的是从这个盒子里发出来的吗?”

    The daemon sweep reports that nine processes are running, which says nothing about whether Postfix can hand a message to the next hop. One wrong character in a relay password gave nine green daemons, green DNS, a Test-tab email that reported success (our Postfix accepts and queues before the relay hop), and mail that quietly deferred forever. Outbound delivery is now probed and surfaced on its own, with a reworked Health tab and a summary that names the failing hop.

  • 邮件控制台

    Live engine output in the dashboard, so a setup that stalls can be read rather than guessed at.

  • 您可以安排的备份

    The mail admin Backup tab gains a real schedule and retention plan, wired to the same pruning the rest of Openship uses.

  • 设置更早、更清晰地失败

    A preflight checks the things that used to surface mid-stream (password shape, firewall step, DNS), and setup errors render in a banner instead of vanishing into the stream.

网络邮件

  • Webmail 现在是一个普通的目录应用程序

    It installs through the same generic installer, image, volume and routing pipeline as every other app, and installs from /apps just as well as from /emails. The mail-specific part is the only part that stayed: which IMAP/SMTP backend it belongs to — one of your Openship mail servers, or an external provider.

  • 链接被存储,而不是从 slug 中解析出来

    The old lookup read webmail-<serverId> 从项目 slug 中退出,通用安装程序永远不会生成该项目,并且错误链接了某人碰巧命名为“Webmail Prod”的任何项目。现在,它是一个真正的外键,当删除 Webmail 项目时,它会被清空(不是孤立),并带有一个遗留的 slug 回退功能,该回退功能会在第一次解析预先存在的安装时对该列进行标记。

  • 它自己的图像和数据库引导程序

    A dedicated webmail Dockerfile and a bootstrap script, so first boot provisions its schema instead of depending on the mail engine's.

应用目录

  • 五个新的一键式应用程序

    Meilisearch, Redis, PostHog, Umami and Neon (Postgres), each declaring its internal connection so it can be linked into a project over the internal network.

  • 徽章告诉您正在安装什么

    Verified, unverified and hosting-mode badges with explanatory tooltips, so a community template isn't visually indistinguishable from one Openship has booted and checked.

  • 目录架构更新

    The published app.schema.json 获取上述后面的字段,并围绕它们重写了参考文档和“添加应用程序”指南。

路由和域

  • 部署会停止擦除您的 vercel.json 路由

    registerRoute 替换整个虚拟主机,因此省略了调用者 cleanUrls / redirects / headers 它没有留下它们,而是删除了它们。这些字段是在两个地方内联构建的,因此简单的部署既不会应用它们也不会保留它们,并且不相关的重新部署会默默地删除“重试路由”安装的任何内容。现在,它们在每个路线注册站点都带有的纯模块中编译一次。

  • 关于边缘拨号的一项决定

    A single resolver owns the proxy_pass 目标:默认情况下固定的环回主机端口(重新启动后稳定,从不面向互联网),容器的桥接 IP 作为高级选项,以及透明回退到不发布主机端口的内部 Compose 服务的容器 IP。每个实例均可选择,其中 auto 作为默认值。

  • 域重定向在证书颁发后仍然存在

    The redirect installed for a hostname is no longer reverted the moment certbot succeeds, and it no longer re-fires on internal rewrites.

  • 边缘的真实客户端 IP

    The real-IP configuration is derived in one place for every scope, so free subdomains and custom domains agree on what the visitor's address is.

  • 路由规则具有端到端套件

    Per-route rate limits, bans and access rules are covered by an e2e test that drives the real proxy.

DNS

  • Cloudflare DNS,有线连接

    Connect a Cloudflare token and Openship writes the records a domain needs itself (#37), issues wildcard certificates over the DNS-01 challenge, and can route a domain through a tunnel instead of an open port.

  • 我们只触及我们创建的记录

    The provider claims a record it wrote and leaves everything else in the zone alone, and it refuses to write a hostname it hasn't claimed. Deleting a domain in Openship therefore cannot remove a record that was already there.

服务器

  • 一种添加服务器表单

    The page and the modal were two 400-line forks that had drifted; they're now one component with a variant, so a field added in one place exists in both.

  • 粘贴或上传 SSH 私钥

    ssh_key_path 指向 API 主机上的文件,该文件在您的密钥位于您自己的笔记本电脑上的远程或 VPS 实例上毫无用处。现在可以从任何浏览器粘贴或上传密钥,静态加密存储,永远不会序列化回客户端,并且在存在时优先于磁盘路径。

  • 服务器页面的连接横幅本身就说明了一切

    Reachability, host channel state, and what each one does or doesn't affect, rather than a single red dot.

  • 部署默认值无法设置为派生值

    The instance default target is a server or cloud; "this machine" is derived (on a server-host box it is already in the server list), so it's no longer an option that means two different things.

项目和部署

  • 从项目标题重命名项目

    A rename modal, plus copy-id and pause/resume, on the heading where the name actually is. The slug stays immutable (it's infrastructure identity); the display name is free.

  • 容器操作通过一根管道

    Pause, restart and logs run through the same deployment-runtime path as everything else, so they can't disagree with the platform about which host or runtime a service lives on.

  • 协调和拆卸更加稳定

    Record-only deletes, orphan GC scheduling, pending actions and port checks were tightened around the same runtime path.

  • 项目的源代码、构建和运行时是三个独立的东西

    Two boolean flags (hasBuild, hasServer)每个都代表两个不同的问题,因此部署可以被接受,然后在一个阶段后失败。现在,项目由三个正交轴描述 - 代码来自何处(git、预构建图像或上传)、构建方式(Docker文件、构建包、静态或无需构建)以及随后运行的内容(Web、worker 或静态) - 在每个阶段读取的一个位置进行解析。现有项目的分类与以前完全相同。

  • 私人存储库 Docker 文件应用再次克隆

    A Dockerfile build runs no buildpack step, so it naturally carried hasBuild=false,而决定是否获取克隆令牌的一个门则关闭了该标志 - 删除令牌并使私有存储库上的克隆失败,即使 Docker 文件需要存储库作为其构建上下文。现在是否获取代码仅取决于它来自哪里,而不取决于它是如何构建的。

  • Worker 是一流的部署类型

    A long-running process with no port (a queue consumer, a bot, a cron loop) had nowhere to go: called a server it failed preflight for a missing port, called static it was routed through file-serving and failed for a missing docroot. worker 现在是它自己的工作负载——像任何其他应用程序一样构建,作为一个始终重新启动的容器运行,没有端口和路由,并检查启动命令而不是端口。从项目的 Server / Worker / Static 开关中选择它,或设置 workload: worker 在 openship.json.

编写并安装

  • up 保留你的 .env

    A variable you set by hand is kept and marked as yours, instead of being regenerated out of a fixed key list.

  • 秘密永远不会从正在运行的安装中轮换出来

    up 检测到它会铸造现有安装已经拥有的秘密(这将使加密的环境无法解密),并拒绝而不是默默地替换它。被替换的 .env 被保留以供恢复。

  • 可以固定图像版本

    An explicit --image-version 对于版本在其映像到达注册表之前到达 npm 的情况,胜过环境和 CLI 自己的版本。

  • 外部 Postgres 数据目录被拒绝,未采用

    The volume's contents are probed before a cluster is started on top of them.

  • openship doctor 和 repair 覆盖更多

    The host channel, an unprovisioned install, and port conflicts, in the same run.

  • 采用 Compose 堆栈不再重新发布其主机端口

    A migrated 5432:5432 将绑定主机 5432 在下一次部署时与已持有的任何物体发生碰撞(通常是 OpenShip 自己的 Postgres),从而中止部署。采用仅保留集装箱港口;该服务通过项目网络上的名称进行访问,并从“域”选项卡中重新公开。该警告区分了一个在机外发布的端口 — Docker 的发布规则路由经过主机防火墙,因此可以真正从 Internet 访问它 — 从仅环回的端口,这样您就知道是否实际上放弃了任何外部访问。

  • stop_signal 和 stop_grace_period 因重新部署而感到荣幸

    A service that asks for a longer shutdown window now gets a graceful stop, with its own signal and grace period, before it's replaced or torn down, instead of being SIGKILL在写入过程中通过立即强制删除进行编辑。不选择加入的容器仍然会快速停止,因此不会增加重新部署延迟。

代理和访问控制

  • 为自动化授予一个资源(而不是整个组织)的 shell

    The only way to let something run a command was a custom-command job, whose grant reaches every server in the org and can't be narrowed. Command execution now hangs off each resource's own permission: a grant on one server (server:admin)是仅限于该框的主机 shell,以及项目的赠款(project:service:write)在该项目的服务容器内运行命令 - 没有更广泛的内容。每次运行都会使用其命令、工作目录和结果进行审核,并且在无法隔离它的运行时上拒绝容器执行。

  • AI 代理通过 MCP 执行

    Two new MCP tools expose host and in-container execution, each requiring the matching per-resource grant, with a hard timeout and an output cap (the agent's call blocks on the reply and the whole body lands in its context). Tools that only work on a self-hosted box are now hidden on the hosted platform, instead of being advertised there and returning 404.

  • 一个访问编辑器和一个实时代理可以重新确定范围

    The MCP consent screen, personal-access-token scoping and member grants were three separate editors and are now one. A connected agent's access can be edited in place from Settings — narrowed, or widened (widening to unscoped asks first) — and applies on its next request, with no disconnect-and-reconsent.

  • 您始终可以强制执行的范围现在可以授予

    Several platform areas (jobs, notifications, analytics, settings, updates, cloud) could be checked for but never handed out, so there was no middle ground between "deploy only" and "the whole account"; they're grantable now, with billing and audit marked sensitive. Listing a collection honors a wildcard grant too — a token allowed to read a server by id no longer 404s when it tries to enumerate them.

桌面

  • 本地部署受到明确的“即将推出”的限制

    Desktop mode is built to control remote servers; running the workload on the desktop itself isn't enabled yet, and the UI now says that once, in one place, instead of offering a target that fails later.

  • 外壳强化和更安全的更新程序

    See Security above.

文档和网站

  • 新的和重写的页面

    "The edge" guide, the openship edge 命令参考、主机通道故障排除、重写的“添加应用程序”指南和应用程序目录参考,以及有关安装、更新和日志/监控的说明。

  • 文档获取社交预览

    Generated OG images per page.

  • 更好的变更日志页面

    Entries collapse to headlines and expand to detail, with controls to expand or filter, driven by this file.

修复

  • 零身份验证登录不会永远反弹远程浏览器

    An instance with no sign-in form grants its session only to a browser on the same machine, so bouncing a remote one was guaranteed to fail, leaving a spinner and then either a connection error for a host that isn't yours or an endless redirect. The page now names the cause.

  • 邮件保留修剪尊重邮件备份

    Pruning no longer considers a mail engine backup an ordinary project artifact.

  • 迁移的容器加入其路由所在的网络

    A same-server migration attached a container that was never published, leaving it unreachable behind a verified domain.

  • 取消构建会停止每个构建路径

    Cancellation reached some paths and not others, so a cancelled build could still be deployed: remote Docker builds kept running, and the static extract went on to publish the output of a build you had already stopped. A cancelled deployment is now terminal.

  • 无操作组合重新部署不会接管活动版本

    A redeploy where every service was carried forward unchanged settled without advancing, so it no longer displaces the release that is actually running.

  • 存储的健康检查在设置表单中仍然存在

    Editing project settings preserved the healthcheck test rather than dropping it, and a NONE 测试数组读取为禁用而不是命令。

  • 完成的转储不再悬挂

    Exec-stream sinks close on EOF, and the upload stall bound matches the producer's idle budget, so a completed backup can't wait forever on a stream that already ended.

  • Docker文件项目不需要命令

    Projects that rely on the image's own entrypoint deploy without one.

  • 每个新字符串都会被翻译

    The release's new copy landed across all shipped languages, with the parity test extended to the new namespaces.

8月7日2026v0.6.1特点修复Breaking52 更新

一个大的发布。它添加了完整的服务到服务网络平面、全天候容器运行状况监控以及对访问者地理和使用历史记录的实时分析,以及独立的容器化邮件引擎、具有一键更新的整个车队范围的基础设施视图、可以过滤和归因的审核日志、Telegram 警报以及可消除最后一个 Bun 崩溃类的基于节点的安装程序。

服务到服务网络

  • 现在任何项目都可以通过内部网络连接到另一个项目

    Every project (a plain single-app, a raw Compose stack, a monorepo, or an imported one) now shows a Connection card with its internal address (http://<alias>:<port>)并可以选择作为“在项目中使用”源。以前,只有具有声明的连接块或多服务 Compose 堆栈的目录应用程序可以在内部访问;单个应用程序项目根本没有内部地址。相同边界的可达性是自动的,并且跨越边界保持明确——只有当您将消费者链接到网络上时,别名才变得可达。仅自托管,并跳过静态站点(无侦听端口)和云托管应用程序(而是通过公共链接)。

  • 为服务提供自定义内部主机名

    A service can carry a custom east-west DNS alias that resolves alongside its default name, set from the service's Settings tab and available to single-app, Compose, and monorepo services alike. Openship normalizes it to a valid hostname and rejects one that collides with another service on the same project network, and the internal-address card shows the alias its containers actually answer to. Self-hosted only.

  • 更清晰的服务设置编辑器

    The service Settings tab groups fields into labelled sections and swaps free-text boxes for structured editors: ports and volumes are entered as chips (with per-item limits enforced as you type) and depends-on is a picker of the project's other services. The image and build-from-source fields are shown together — fill either, and a build context wins over a stale image — instead of an image/build mode toggle.

容器健康和事件

  • OpenShip 全天候监控您的容器,而不仅仅是在部署时监控

    Until now a container was health-checked exactly once, during the ~15s window right after a deploy, and then never looked at again unless a human was staring at the project page. A new health watch polls every server's Docker daemon once a minute (and reacts within about 10 seconds when Docker itself reports a container dying or restarting), so an app that falls over or drops into a crash loop at 3am raises an alert through your existing notification channels instead of waiting for a user to complain. Self-hosted only.

  • Broken containers page you once, not every minute

    A container stuck in a restart loop is broken on every poll, so a naive watcher would fire 60 alerts an hour about one fault. Instead each fault becomes a single incident: one message when it opens, one more only if it gets strictly worse (unhealthy → crash looping → down), and one all-clear that tells you how long it was down. A fault must be observed twice before it notifies, and an in-flight deploy, an operator's own docker stop,或者禁用的项目永远不会触发误报。

  • 无法访问的服务器是一个警报,而不是每个应用程序都有一个警报

    When a box's Docker daemon stops answering, Openship opens a single server-level incident that names how many projects it can no longer monitor, and freezes those projects' health rather than falsely marking them recovered. The record is durable, so a box that has been down for days does not re-page every time the control plane restarts.

  • 每个项目都有一个“运行状况”选项卡,包含 30 天的事件历史记录

    Each project gets a Health tab listing its currently open incidents plus a rolling 30-day history of resolved ones with downtime durations. It also states whether monitoring is actually switched on (an operator toggle in the Jobs module) and surfaces the server's own outage when a box is unreachable, so an empty tab is never misread as "all good." Self-hosted only.

分析和资源使用

  • 查看您的访客来自哪里

    The Monitoring tab draws a per-country choropleth of visitors alongside a ranked list, and animates real-time request ripples fed by the same stream the Logs tab tails, so you can watch where requests are landing right now. It works the same way self-hosted and on Cloud, and it can tell "no visitors yet" apart from "geo lookups aren't set up on this box," which used to render identically as an empty map. On a multi-domain project the whole view scopes to a chosen domain.

  • 访客数量现在是真实数字,而不是请求数量

    The dashboard's visitor figure was a request count relabelled "unique IPs," so five page views from one browser counted as five people. It's now a genuine count of distinct visitors, deduplicated at the edge with a per-day salted hash that never stores an address or a per-visitor row — the number is honest while still collecting no behavioural data on your end users.

  • 背后有真实数据的热门路径和响应代码

    The Top Paths table was hardcoded empty and error rate couldn't be answered from anything saved. Both are real now: the daily rollup records normalized request paths (query strings stripped, ids collapsed, so tokens never become keys) and the full status-code mix, and a new card expands each 2xx/3xx/4xx/5xx class to the exact codes beneath it. On self-hosted, per-path aggregation is opt-in per project (a toggle, default off, including on existing projects) because it adds measurable work to every request the edge handles; on Cloud paths are aggregated automatically. Every other analytics dimension is unchanged.

  • 保留使用历史记录,以便您可以查看导致崩溃的原因

    CPU, memory and network usage used to exist only as a live stream that vanished when you closed the tab, so "was memory climbing before it got OOM-killed at 3am" had no answer. Usage is now sampled on a schedule into 5-minute buckets and charted over time, per service. A Compose project reports its whole stack with a per-service breakdown and an All/service scope picker instead of just the one container the primary service owned; a static site (nothing to measure) now says so plainly instead of showing four zeroed metrics. Self-hosted Docker deployments; bare non-Docker deployments report zero network, since per-process accounting isn't available there.

  • 繁忙的域保留其分析

    A domain pushing more than about 2 GB in a single minute (roughly 286 Mbps — routine for video or large downloads) used to overflow a 32-bit byte counter and kill the analytics scrape for that entire domain, so the busiest sites were precisely the ones with no analytics. The bandwidth counters are now 64-bit and collection keeps up. Self-hosted edge.

  • 当无人查看时,分析不再悄然消失

    Traffic analytics live in the edge's memory under a TTL and were only flushed to the database when someone opened a project's Analytics tab, so a project nobody viewed for a day lost its per-minute data. A background scrape job now persists every server's analytics on a schedule whether or not anyone is watching, collecting a whole server in one pass instead of a separate memory scan per domain.

  • 每个主题中的图表工具提示都可读

    Tooltips were effectively transparent in the dark themes (plot lines showed straight through the text) and on light cards the hover marker rendered as a stray white block below the tooltip. Both are fixed with a shared tooltip style reused across the monitoring and billing charts.

边缘和反向代理

  • 调整每个项目的反向代理

    A project's Routing settings now expose a full set of proxy tunables instead of a handful: raise or entirely remove the upload size limit, set connect/read/send/keepalive timeouts, control response buffering and gzip level, turn on HTTP/2, tighten request-header limits, and verify TLS to the upstream — each value validated before it reaches the generated nginx config and labelled with its own directive name. On self-hosted it also reads back what the edge is actually serving next to what you saved, flags any drift in colour, and offers a one-click adopt, so a hand-edited vhost or a value the sanitizer dropped can't quietly disagree with your settings. Self-hosted only.

  • 每个国家/地区的分析和国家/地区规则适用于容器化边缘

    The containerized edge shipped without the MaxMind geo library or its country database, so every lookup returned nothing: no per-country analytics were recorded, and country-based route rules failed closed (a single-country ban silently blocked all traffic). The library and a GeoLite2 database — parsed and validated before shipping — are now baked into the edge image, so geo works from a box's first install with no runtime download.

  • Cloudflare 或负载均衡器背后的正确访问者身份

    Behind a proxy the edge treated the proxy as the client, which broke four things at once: visitor country resolved to the PoP, distinct-visitor counts collapsed, per-IP rate limits put the whole planet in one bucket, and IP bans banned a PoP instead of a visitor. The edge now recovers the real client address from CF-Connecting-IP,仅信任 Cloudflare 的已发布范围作为连接对等点。

  • 即使不在 API 环回上,每条路由的规则也会到达边缘

    Pushing a project's route rules to a local edge now goes through the same resolved edge-management path as the rest of Openship instead of assuming the edge lives on the API host's own loopback. On setups where it doesn't — such as the containerized edge — rate-limit, ban, and country rules now actually take effect.

  • “Edge Ready”药丸与服务器的真实状态相匹配

    Edge readiness is now read from whether Openship's edge container is actually running, the same fact the Infrastructure tab and System Health use. Before, a leftover bare-host OpenResty install could make the pill claim "ready" while the server tab reported the edge as down.

自定义和免费域名

  • 免费 .opsh.io 域仅路由到您已证明其控制权的服务器

    Openship Cloud's shared edge now forwards a free subdomain to your server only after that server answers a challenge proving it owns the target, a proof that lasts 90 days and that Cloud re-checks about a week before it lapses. Openship prepares the box to answer the moment you set up its edge, so a free domain added later works without a redeploy, and a background sweep re-asserts, reads back over the server's own public address, and re-verifies anything expired — so a box left undeployed for months no longer silently loses its free URLs. A slug can't be pointed at someone else's box, and a server that can't yet answer is told why. Requires Openship Cloud.

  • 免费和自定义域现在可以在静态网站上使用

    Adding a free .opsh.io 域名指向一个静态项目,用于在边缘注册任何内容,因此 URL 会变成通配符,后面没有来源;编辑静态项目的域在下次重新部署之前不会写入任何虚拟主机。现在,两者都会在您保存时发出真实的路线,为项目的构建文件提供服务 - 代理应用程序已经具有相同的行为。

  • 已颁发但随后遇到障碍的证书不再丢失

    If an ACME order completed but a later step failed (the vhost rewrite, the reload, or the read-back), the domain stayed stuck in "provisioning" with no expiry recorded, which made it invisible to the renewal sweep — a valid certificate then sat on the edge and expired ~90 days later. Openship now re-reads the edge after a failed issuance and records a certificate that's actually present, so renewal stays scheduled.

  • 无效的自定义域被拒之门外

    Setting a custom domain to something that isn't a public hostname (localhost、裸 IP、单个标签或带有路径/端口/方案的值)用于返回成功、创建死的挂起域行,甚至写入 server_name localhost; vhost 到共享边缘。写入路径现在验证自定义主机名并拒绝错误的主机名,同时仍然允许已经拥有错误值的项目编辑并将其删除。

  • 编辑免费域不再显示错误的“需要操作”

    A single edit could sync the same free subdomain to Cloud twice, and the two racing challenges reset each other's token, so the route worked but the project reported "Action Required" anyway. Callers that run their own managed-edge sync now suppress the duplicate, so each edit issues one challenge and the status reflects reality.

  • 重定向和上传限制在保存时生效

    Raising a route's upload limit or adjusting its timeouts now applies as soon as you save instead of waiting for the next redeploy, and a domain redirect is applied live to static-site domains too, not only to proxied apps.

电子邮件

  • 邮件作为独立引擎运行,而不是接管您的服务器

    Setting up mail no longer installs iRedMail's daemons directly onto the host or reboots the box. Postfix, Dovecot, spam and virus filtering, and DKIM now run inside a single openship-mail 容器及其 vmail 数据库位于 Postgres sidecar 中,主机联网,因此邮件仍然可以看到真实的客户端 IP,并且边缘不处于邮件数据路径之外。设置减少到八个步骤,唯一的先决条件是 Docker 和 openship 边缘,并且每个邮件状态(队列、maildirs、DKIM 密钥、配置)都位于主机绑定安装上,因此升级是一种保留数据的拉取和重新创建过程。仅自托管。

  • 邮件使用与其他所有内容相同的边缘和 TLS

    Mail setup no longer stands up its own host OpenResty and certbot on the side. The certificate for mail.<domain> 通过共享的 openship 边缘发布,与其他域的 TLS 所采用的路径相同,并且现在像任何其他域一样记录续订 — 容器化边缘上的邮件证书(无主机 certbot 计时器)用于在安装后约 90 天悄然过期;续订失败现在会发出通知。

  • 容器化之前设置的邮件服务器继续运行

    The move to containers is topology-aware, so a server whose mail was installed the old way (system daemons, database on the host) still reports accurate component health and stays fully manageable: SQL queries, outbound SES/SMTP relay config, and daemon restarts all target the right engine. When the engine genuinely is stopped or was never installed, admin actions now return a clear message telling you to restart it or re-run setup instead of a bare 500 leaking a Docker "No such container" error.

远程基础设施

  • 在一个地方查看每个托管边缘和邮件容器

    A new Infrastructure view lists each server's edge and mail container with the image version it's running against the version this release pins (for example edge 0.4.0 → 0.5.0), and flags which are behind, stopped, or missing. An attention rollup surfaces the ones that genuinely need hands — an edge that's down, or absent on a box that hosts projects — separately from the ones that merely have an update available. Self-hosted only.

  • 在不接触 shell 的情况下更新、修复或安装容器

    Update swaps a behind container onto the pinned image (rollback-guarded), Fix restarts a stopped one in place, and a server with no edge gets a one-click Install that runs the first- install path with 80/443 takeover consent. Each apply streams its pull/recreate/ verify progress and survives a dropped connection, and a fleet-wide Update all / Restart stopped does the same across every server at once. Self-hosted only.

  • 升级时自动更新您的远程基础设施

    A new instance-wide toggle lets the control plane update every remote edge and mail container automatically when you upgrade Openship (its APP_VERSION 向前移动),因此您的舰队的基础设施可以跟踪您正在运行的版本,而无需手动扫描。它是服务器端的,因此它也可以在桌面上运行,与桌面应用程序自己的自动更新不同,并且默认情况下处于关闭状态。仅自托管。

  • 漂移检测本身保持最新状态

    With auto-scan on (the default), opening the Infrastructure tab or the home page quietly runs one detect-only scan when the cached state is stale, throttled to about every 30 minutes per browser, so the attention dot reflects reality without pressing Scan. It only refreshes what's shown — it never applies an update, which stays the separate auto-update toggle. Self-hosted only.

  • 旧版盒子不再被标记为损坏

    A server converted to the containerized edge kept listing its leftover host OpenResty as a component with an Update button for a config nothing loads; those superseded host modules are now dropped from the view. And a legacy host-native mail engine (systemd Postfix/Dovecot) that was quietly delivering mail used to show up as "Stopped, container missing" — it's now labelled as not containerized rather than inventing a version. Self-hosted only.

Docker迁移

  • 迁移后的网站保留其运行时的上传限制和超时

    When you move or take over a Docker stack, the reverse-proxy tunables the source vhost declared (upload size limit, upstream read timeouts) are now carried onto the migrated project before the new edge vhost is rendered. Previously the site silently reverted to nginx's 1 MB / 60 s defaults at cutover, so the first large upload after a move failed with a 413 and nothing tied it back to the migration. Adoption is additive: a limit you set by hand always outranks a value inferred from the old box. Self-hosted only.

  • 采用堆栈不再重新发布内部端口

    A compose service that published a container port on a random host port (a single-part ports: 条目,例如数据库的 5432(源从未真正暴露)现在在采用过程中保持不暴露,而不是在目标上重新发布,因此迁移不会不必要地暴露内部服务或与已拥有主机端口的任何内容发生冲突。该端口仍然显示在向导中,以便您可以路由到该端口,并且服务到服务的流量通过共享网络继续按名称进行解析。仅自托管。

  • 向导会告诉您哪些环境变量没有被继承

    When adopting a foreign stack, environment variables that exactly match the image's baked-in defaults are dropped rather than imported as explicit config (the image still supplies them at runtime). The wizard now lists exactly which keys were skipped and why — common with Coolify/Nixpacks images that bake config as ENV layers — so you know what to re-enter if you later change the image.

  • 导入向导中不再出现虚拟主机名

    The wizard used to invent a hostname from the project name whenever a step had no route chosen, labelling port fields, previewing monorepo sub-app hosts, and even wiring the "Visit Site" button to a host that would never exist. It now shows only hosts your config actually names, and hides "Visit Site" entirely when the deployment has no public domain.

审核日志

  • 准确查看您的 AI 助手发生了什么变化

    Every audit entry now records where the action came in from (the dashboard, an MCP client, the CLI, the API, a webhook, or the system itself), and you can filter the log down to a single source. Isolating MCP-driven activity finally answers "what did the AI assistant do," which was impossible before because an MCP write and a CLI write produced identical rows. Entries written before this release show as an honest "unknown" rather than being mislabelled.

  • 关闭审核并控制其保留时间

    Each organization can switch audit recording on or off and pick a retention window (7, 30, 90, 180 or 365 days). Turning recording off stops new entries but never touches the ones already written, and the act of disabling is itself logged first, so the trail always explains why it went quiet. The switch is per-organization, so on a shared cloud instance one tenant can't disable everyone's audit log.

  • 日志上的真实过滤栏

    You can narrow by category, actor, date range and free-text search, with a live count on every category tab. Search resolves project, server and domain names, so typing a name like "api-gateway" turns up entries that only ever stored an opaque id, and rows now display the human name of the affected resource, resolved server-side in one batched lookup per page.

  • 分页日志不再跳过或重复行

    Entries that share a timestamp are now ordered by a stable tiebreaker, so scrolling through pages no longer reshuffles them; two entries created in the same instant could previously appear twice or vanish between pages.

通知

  • 向 Telegram 发送警报

    Telegram joins email, Slack, Discord, and Teams as a notification channel: point a BotFather bot at a chat, group, or forum topic and Openship delivers your deploy, health, and job alerts there. The bot token is stored encrypted, and the channel list shows which bot does the sending.

  • 自托管通知设置删除了永远无法触发的开关

    On a self-hosted box the billing notification categories are fed by the SaaS billing system, so they were switches that could never send anything. They no longer appear, and the remaining categories are organized into tabbed groups in Settings.

安装及包装

  • OpenShip 现在在 Node 上安装和更新,而不是全局 Bun

    该 curl | sh PowerShell 安装程序会下载一个在 Node 下运行的独立的、经过 sha256 验证的 CLI 有效负载:如果您有 Node 22+ 系统,它们会使用您的系统,否则会从 nodejs.org 向您提供官方 Node 22 ~/.openship,并且它们会悄悄地将您从以前的任何全局 Bun 安装中迁移出来,而无需触及您自己的 Bun。 openship update 采用相同的路径 - 重新下载经过验证的有效负载,首先刷新运行时 - 因此提升节点底层的升级会自行修复而不是破坏。这将淘汰可能会导致远程 SSH 操作的 Bun-vs-ssh2 崩溃类。

  • 邮件服务器作为官方镜像提供

    Openship's official multi-arch (amd64 + arm64) image set, built and published to GHCR and Docker Hub each release, now includes openship-mail 与 API、仪表板和边缘图像一起,因此不再需要从源代码构建自托管邮件引擎。

  • openship up 现在可以在无根 Docker 下工作,而不是神秘地失败

    Bringing up the compose stack on a rootless daemon used to abort the install with Docker's opaque "error while creating mount source path … permission denied," because a rootless daemon can't create the edge's bind-mount directories under root-owned paths. The CLI now creates those directories itself and, when it can't, prints the exact one-time sudo mkdir/chown 运行命令(#372)。

部署和编写

  • 工作部署永远不会被记录为失败

    Build output that carried a raw NUL byte or a broken Unicode character (as a failed docker exec 当它溢出其多路复用流、帧头和所有内容时,会导致日志写入失败,并且 OpenShip 误读拒绝写入,因为部署本身失败:实时运行的部署被标记为失败,其容器被拆除,而部署视图仍停留在“正在部署”。存储的构建日志现在已进行清理并限制大小,结果写入会丢弃任何日志或错误 blob Postgres 拒绝的内容,而不是丢失状态,并且始终会触发关闭实时流的终端事件。

  • 您的访问 URL 和自定义域端口在重新部署后仍然存在

    A project's deploy target is now stored durably on the project itself (a new server_id 列),而不是仅存在于最新部署的易失性元数据中。以前,新的或部分快照可能会丢失该绑定,悄悄地将项目回归到本地部署,从其自定义域中剥离端口(502),并将访问 URL 重置为 localhost:3000;现有的服务器托管项目已回填,因此在下次重新部署时不会影响它们。即使部署的端点集省略了经过验证的自定义域,也会保留它,而不是删除或清空它。仅自托管。

  • 自由域安装现在有一个部署目标

    A box set up with a free .opsh.io 域可以在没有列出任何服务器且没有任何可部署到的情况下完成加入,因为注册本地“此服务器”行会挂起路径永远不会运行的引导步骤。现在,当首次列出服务器、连接到 OpenShip Cloud 以及管理员重置时,该框会具体化其自己的部署目标行。附上免费的 .opsh.io 稍后项目的域不再需要首先重新部署,因为现在每次部署都会启动框以回答所有权检查。仅自托管。

  • 服务域尊重您的上传限制和代理设置

    A compose service's own domain ignored the project's reverse-proxy tuning, so the main app would accept a 50 MB upload while the same project's service domain rejected it at nginx's 1 MB default with a 413. Those settings now apply to every domain a project writes — per-service, static, single-domain composites, path fan-out, and single-app native deploys. Self-hosted only.

  • 目录应用程序服务 URL 按端口进行解析并且绝不为空

    Apps that route one container port to a domain and leave another port-only (Convex, for one) used to get an empty or self-referential origin injected (CONVEX_SITE_ORIGIN="",或一个 127.0.0.1 容器内的那个指向容器本身)。现在每个端口都可以独立解析,仅端口服务会回退到盒子的真实可达状态 http://host:port,和一个 {{publicUrl:…}} 仍然无法解析的令牌未设置 - 因此应用图像自己的默认值 - 部署日志中会发出响亮的警告,而不是无声的空白。

  • 路由警告会告诉您边缘何时出现问题

    When a deploy succeeds but its domains aren't being served, the post-deploy warning now checks why: if the edge container itself is down it tells you to bring the edge back up, instead of sending you off to your DNS provider to debug routes that are actually fine. Self-hosted only.

升级说明:此版本改进了固定边缘和邮件图像版本。在自托管上,打开新的基础设施视图,将每个服务器的边缘和邮件容器更新到固定映像上,或者打开实例范围的自动更新,让控制平面在每次升级时执行此操作。

7月31日2026v0.5.0特点修复25 更新

回滚被重建,因此它实际上恢复了一个版本,以及跨 MCP 集成和自定义域的一轮修复。

回滚

  • 回滚每个项目的任何版本

    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 同一操作中的证书,不受保护:a www 尚未指向服务器但失败 之后 顶点已经成功,但据报告顶点已损坏。在打开开关的情况下添加域也只会显示顶点的 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.

7月28日2026v0.4.7特点修复7 更新

CLI 自托管故事已最终确定,远程 Docker 迁移变得可靠,并且在控制平面上进行了一批修复以实现更稳定的版本。

命令行界面

  • 安装完成后将打开控制面板,而不是安装向导

    Bare openship (以及来自源 openship-dev) 现在可以识别 Docker Compose 安装(Linux 上的默认安装)。设置后重新运行可以管理正在运行的堆栈,而不是再次从头开始引导您浏览名称/电子邮件/域。

  • 控制面板启动/停止/重新启动驱动实际堆栈

    On a compose install these now run docker compose up -d / restart / down 并读取堆栈的真实状态,而不是针对从未安装的 systemd 单元(报告健康堆栈“已停止”)。

迁移和远程 Docker

  • SSH → Docker 网桥不再挂起或使运行状况良好的服务器出现错误故障

    Migrating from another platform (Coolify/Dokploy/Dokku) or adopting a running Docker host could stall the reachability check — or drop the request outright — under the Bun-hosted API, even against a perfectly healthy daemon. The bridge now starts reading the request socket immediately and verifies each forwarded channel actually carries data, falling back to docker system dial-stdio 当通道打开死机时建立新连接。由@jbermudez00 (#271) 贡献。

邮件

  • 邮件服务器设置可通过桌面应用程序进行

    The iRedMail engine is now shipped inside the packaged desktop app (and the CLI bundle) and located by an explicit path, fixing the Transfer iRedMail Engine … tar: could not chdir 安装失败。

修复

  • 自托管 GitHub 连接采用令牌优先

    A remote (VPS) instance pastes an access token inline in the Library, with no gh auth login 提示; gh CLI 路径现在仅适用于桌面,这是它所属的位置。

  • 部署向导直接进入配置

    The deploy-target picker no longer flashes on entry. A sensible target is applied silently and stays one click away in the summary bar at the top.

  • 控制平面停止列出幻影服务

    The self-managed "Openship" project no longer shows a bogus public openship 服务(及其杂散 openship-openship.opsh.io 路线)与任何容器都不匹配,并永远显示“已停止”。

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.

7月22日2026v0.3.0特点修复安全性13 更新

原生 Apple Silicon 构建、与其他平台部署配置的直接兼容性,以及一批自托管和可靠性修复。

下载

  • 原生 Apple Silicon (arm64) 桌面应用程序

    MacOS now ships separate ARM64 和英特尔 x64 dmgs(均在 CI 中构建并进行 SHA-256 校验和),因此 Apple Silicon Mac 可以在本机运行,而不是在 Rosetta 下运行。 Windows (x64) 和 Linux (AppImage) 保持不变。

部署·堆栈检测

  • 按原样部署已为另一个平台配置的存储库

    The stack detector now reads railway.toml/railway.json 和 vercel.json (构建/安装/启动/输出命令、框架和路由)并将它们折叠到自己的检测上。已告知 Railway 或 Vercel 如何构建的存储库在此处以相同的方式进行部署,无需重新配置。每个配置源都通过一个共享解析器注册表运行(没有每个源的特殊情况)。

  • openship.json

    An optional repo-root config to declare build, routing, env, and domains up front; it's authoritative over auto-detection and rides the same engine, for the repo root and each monorepo sub-app.

自托管

  • 默认部署到自己的服务器

    A self-hosted instance targets the server it runs on, never Openship Cloud, unless you explicitly choose cloud.

  • 当控制平面容器化时,健康检查起作用

    The post-deploy probe reaches your app through the host gateway, so a containerized self-host no longer fail-reverts an otherwise-healthy deploy.

  • OpenResty 安装在较新的发行版上

    The edge install no longer pins the APT repo to a codename that doesn't exist yet (e.g. Ubuntu 26.04), and self-heals a box already broken by the old pin.

命令行界面

  • openship stop 实际上停止了

    The service and its children are reaped by process group and any ports it held are swept, so a restart can't strand the old process on a new port.

可靠性和修复

  • 现在返回格式错误的 JSON 请求正文 400,不是 500。
  • 云静态输出路径受限

    The Pages output path resolves through one shared, sandboxed resolver so a build can't escape its output dir.

  • 邮件 DNS 扫描 检测重复的 DMARC 记录.
  • OAuth 发现元数据已正确提供 在公共 URL 后面.
  • SSH 执行流 超时时干净地关闭 而不是泄漏。
  • 推动 Laravel 部署 测试治具 摆脱弱势群体 laravel/framework (CRLF email advisory)

    A fixture only, never a shipped dependency.

7月22日2026v0.2.2特点修复12 更新

应用和作业不断发展,自托管服务器现在可以自行与 GitHub 通信,备份有了真正的归宿,并且修复了一批删除/登录/数据库可靠性问题。

应用程序

  • 第 2 天应用程序设置

    Installed apps now expose a curated settings surface (schema-driven) so you can change an app's real config after install without digging through raw env. Edits go through a safe env-merge and tell you whether a full redeploy (vs a quick restart-apply) is needed.

  • 清理每个应用程序安装向导

    Clicking a catalog app opens a focused, business-only setup that creates the project on confirm; the technical deploy wizard is now the "Advanced" path (no more orphaned draft projects from a half-finished install).

  • OpenShip Mail 是一款一流的应用

    It appears in the catalog alongside Convex and n8n and hands off to the mail wizard. The rest of the catalog shows as 即将推出 (变暗,不可安装)对于此版本。

工作机会

  • 自动备份显示在“作业”中

    (Read-only) — backup schedules run on the same job runner as everything else (zero duplication), so their next/last run sits right next to your system and custom jobs.

服务器·GitHub

  • 连接服务器上的 GitHub

    Each self-hosted server now authenticates to GitHub on its own, from a dedicated GitHub 选项卡:使用设备代码登录(例如 gh),粘贴令牌,生成 SSH 密钥以添加到您的帐户,或使用自动注册的只读每个存储库 部署密钥。凭据以加密方式存储,并且在部署流程中重复使用完全相同的连接面板,因此只需单击一下即可在部署中修复丢失的凭据。私人存储库克隆现在无需桌面在线即可工作。

备份

  • 重新设计的备份

    Per-destination storage stats, a sticky status rail, and clickable rows that open a per-destination detail page showing exactly which projects and services back up there.

云

  • 每用户项目上限

    Openship Cloud enforces a hard cap on projects per user (env CLOUD_MAX_PROJECTS_PER_USER,默认 2),在创建和文件夹上传/确保时。自托管不计量。

可靠性和抛光

  • 删除永远不会卡住

    Project deletion shows a real 正在删除 状态,当源拆卸无法完成时,您会得到一个干净的 “从存储中删除” 立即删除记录的选项(剩余资源稍后由 GC 回收)。原子的、全有或全无的删除保持默认状态。

  • 桌面登录修复

    The login redirect now lands on the same loopback host the session cookie was minted on (localhost ⇄ 127.0.0.1),因此仪表板不再打开 cookieless 并将您弹回到 /login.

  • 嵌入式数据库启动

    No more false "locked by a different machine" on your own box when the machine-id probe is momentarily flaky; the cross-machine guard now only fires on a genuinely different, stable machine id.

  • 更平静、一致的主题

    Status colors (success / warning / danger / info) are unified semantic tokens across the whole dashboard, and the dim theme's greens and reds are tuned for comfortable contrast.

  • Servers empty state refreshed

    Clearer illustration, a 查看文档 操作,以及每个“配置内容”磁贴的不同图标。

7月20日2026v0.2.0特点修复11 更新

跨部署流程、应用程序目录、路由、服务器、作业和构建工具链的大型功能+强化版本。

部署

  • 重新设计 “你想部署到哪里?” step

    Unified page-style header with the 继续 与配置列对齐的操作,以及 折叠的、可搜索的服务器选择器 (带有内联“添加您自己的服务器”)。

  • 包管理器工具链修复

    Pnpm/yarn are now enabled via corepack 跨每个构建路径(云、生成的 Docker 文件、裸主机、monorepo 工作区准备、云本地构建)。修复 pnpm: not found 部署时。

应用程序

  • 可搜索、类别选项卡式一键式应用程序目录

    , Expanded to 15 production-ready self-hosted apps: Convex, n8n, Ghost, Directus, NocoDB, Metabase, Grafana, Gitea, code-server, Uptime Kuma, Vaultwarden, FreshRSS, Stirling PDF, IT-Tools, Excalidraw.

  • 首页“应用”卡片刷新;目录卡显示真实的品牌徽标。

路由和域(单一事实来源)

  • 自定义域开启 基于服务的项目 now flow through the same verify → DNS-records → SSL pipe as single-app domains

    A verifiable pending row is minted on add/create/edit, one canonical hostname normalizer is shared across storage/routing/domain-service, lookups are cross-tenant-safe, and certbot is gated on verification (no wasted Let's Encrypt attempts).

服务器

  • 重新设计的服务器页面(选项卡、实时可达性、国家标志)。
  • 每服务器 git auth tab (token / SSH key / deploy keys) with a comfortable full-width card

    Connect-on-server credentials honored in preflight.

工作机会

  • 职位页面收益 搜索 + 概览 状态过滤器侧边栏 (正在运行/失败/已计划/已禁用),一旦存在自定义作业就会显示。

团队和工作空间

  • 邀请会员

    Is only offered where it works (team orgs on a multi-user instance); single-user/personal instances are guided to migrate or create a team org instead of hitting a dead end.

添加服务

  • 该 OpenShip Cloud 当实例未链接时,图像选项卡会显示“连接到 OpenShip Cloud”CTA,并且源切换器具有更清晰的对比度。

其他

  • Docker 迁移流程、每个项目/服务备份、统一连接检查、阿拉伯语 (RTL) 本地化、营销路线图页面和桌面窗口美化(macOS 红绿灯插图)。