← 变更日志

v0.9.1

This patch adds a public app catalog, Russian dashboard support and runtime image controls. It fixes workflow saves and Cloud recovery, updates webmail live, and improves routing, build capacity and image handling during redeployments. These notes cover all changes since 0.9.0.

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

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

  • 安装前浏览应用程序

    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.