← 変更履歴

v0.9.3

This release improves Cloud monitoring and build-cache reliability, adds deployment automation and isolated pull-request previews, and makes workers and schedulers easier to configure, observe and recover. These notes cover all merged changes since 0.9.2.

1 リリース
10月17日2026v0.9.3特長修正25 件の更新情報

導入の自動化とプレビュー

  • コマンド変数を環境に移動する

    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.

  • i ノード合計が固定されていないファイルシステムを受け入れる

    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.