← 変更履歴

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.

  • 既存の Web メール アプリを復元する

    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.