← 变更日志

v0.8.1

Openship Cloud now runs projects on managed servers with their own monthly plans. Share a server across applications, add another when you need it, and manage your Cloud resources alongside local projects from desktop or self-hosted Openship. This release also adds passkeys, authenticator 2FA and a private support inbox, expands CLI automation, and improves billing, migration and deployment recovery.

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

托管云服务器

  • 一台服务器,多个项目

    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,它保护身份验证器秘密和恢复代码。