← 変更履歴

v0.9.9

Critical security update covering authentication, Cloud connection approvals, server isolation and encrypted email delivery. Includes all changes merged into main since 0.9.8, plus deployment, billing, assistant and dashboard improvements.

1 リリース
11月3日2026v0.9.9特長修正セキュリティ27 件の更新情報

セキュリティ

  • 認証の依存関係

    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.

  • アーチファミリーのホスト

    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) Better Auth 1.6 からアップグレードする前に、アカウントのペアを確認してください。

  • 作成されたものを置き換える container: 名前空間参照 service:<name> 同じスタック内のサービスの場合。ホスト バインド マウントはデフォルトでは無効になっています。信頼できる自己ホスト型インスタンスのオペレーターは、明示的に有効にすることができます。 OPENSHIP_ALLOW_HOST_BIND_MOUNTS=true;クラウド ホストのマウントは制限されたままです。
  • 認証された SMTP は、検証された TLS/STARTTLS をサポートする必要があります。以前のエンドポイントが平文配信のみを受け入れた場合は、TLS 対応の送信エンドポイントを構成します。