← 変更履歴

v0.9.6

Recommended update for database recovery, reliable builds and migrations, GitHub Actions scheduling, and managed infrastructure updates.

1 リリース
11月1日2026v0.9.6特長セキュリティ34 件の更新情報
  • コンテナクラッシュ後に PGlite を回復する

    Hold a Linux kernel file lock so reused PIDs cannot strand the database or admit an owner in another container. Preserve conservative checks for older locks and other operating systems (#1524).

  • Docker 個のビルド失敗を読み取り可能な状態に保つ

    Surface the cause before long generated commands, preserve the full output in build logs, and retain Cloud recovery guidance after reload. Exit 137 is reported as a killed process with possible memory pressure, without claiming a confirmed out-of-memory event.

  • Monorepo ランタイム イメージを各サービスに合わせて維持する

    Use the service's framework and selected builder for its runtime instead of inheriting an unrelated parent image. Fill missing builders from the stack registry, preserve explicit runtime selections for unchanged apps, and use the same resolution when checking whether runtime images can be refreshed.

  • スコープ付き Kubernetes マニフェスト基盤を追加します

    Admit supported resources into a project's namespace with ownership checks on objects, pod/job templates and selectors. Validate the full change against Kubernetes before writing, reject changed Job definitions, and preserve conflict checks when updating or pruning. Exercise apply, update and cleanup against K3s in CI and the release gate. This foundation does not yet expose a manifest upload UI or deployment route (#1039).

  • ライブ Docker ログを保存します

    Decode stdout and stderr independently across split frames and UTF-8 characters, keep TTY logs intact, and report malformed or truncated streams so the existing reconnect flow can recover (#1482).

  • 検証済みセルフホステッド OIDC サインインのサポート

    Discover a configured identity provider and verify signed ID tokens, issuer, audience, expiry and sign-in nonce before creating sessions. Preserve invitation and two-factor checks, require matching UserInfo subjects, and refuse insecure or redirected provider endpoints. Require verified email, scope accounts to the issuer and exact subject, and keep instance OIDC disabled on Openship Cloud and outside local-account auth mode (#1489).

  • BuildKit セッションを維持する

    Answer Docker’s session health checks so builds can use optional secret mounts after long install/build steps. Close sessions on completion, cancellation, and transport errors (#1488).

  • ダイジェスト参照画像をサーバー間で移動する

    Use the reference restored by Docker load for migration's one-time deployment handover. Direct and relayed transfers no longer try to create a Docker tag containing a digest (#1526).

  • ステートレスな単一アプリ プロジェクトをサーバー間で移動する

    Deploy a project-owned app with no service rows through its single-app pipeline using the transferred image. Reject unsafe empty service scopes before copying data or stopping the source; reused containers stay outside the deployment scope. Single apps with mounted data remain unsupported and are refused before data movement (#1525).

  • キューに入れられた GitHub 個のジョブを移動し続けます

    Replace a registration that GitHub assigned to another job, and only count spare registrations whose runners remain admitted and capable for the waiting workflow. Excluded runners, stale approvals and incompatible hosts no longer block dispatch (#1505, #1509, #1541).

  • レプリカの起動中にクラウド診断を利用できるようにする

    Allow bounded schema initialization to wait for another replica, while preserving the short write deadlines and local-log fallback used during normal operation.

  • サービスコンテナの交換後に健全性を回復する

    Refresh only the stale service binding when the continuous watcher verifies a healthy successor under the same active deployment. Preserve native and Compose service identity through managed edge updates and rollback; leave unrelated services and deployment history intact (#1496).

  • サーバー認証情報を使用してプライベート リポジトリをスキャンする

    Repository preparation, monorepo folder selection and branch rescans use the shared GitHub credential chain, including the selected self-hosted server's saved token. Without a selection, only the active organization's local server is eligible. Borrowing requires repository access and server write permission; SSH provisioning, GitHub mutations and Cloud authentication remain unchanged (#1500).

  • Laravel ワーカーの提案を本番環境の依存関係に一致させる

    Suggest the standard queue worker when Horizon is only in require-dev、デフォルトの Composer と一致します --no-dev インストールします。明示的なロールの選択は引き続き利用可能です (#1171)。

  • 接続されているサービスを削除した後もランタイム ロールを利用可能な状態に保つ

    A single source app retains its existing deployment and role configuration flow after the last attached service is removed or disabled, preserving its service and routing identity (#1308).

  • デプロイ後に誤って古いロールの警告が表示されるのを防ぐ

    Background image cleanup updates storage measurements without changing the project's configuration revision. Real configuration edits still invalidate previously reviewed changes.

  • OpenShip を獲得

    Explain the Cloud affiliate program at /affiliates、インタラクティブなコミッション分割、月次および年次の報酬タイミング、支払いガイダンス、専用のソーシャル プレビューを備えています。ダッシュボードのアフィリエイト エントリに、左側のサイドバーのギフトボックス アイコンで「獲得」というラベルを付けます。

  • CockroachDB サービスを正しく開始する

    Pass the required single-node command to the official image, generate an application password, and persist TLS certificates alongside the existing data volume. New services keep TLS and password authentication enabled; container replacement preserves both data and certificates. Include recovery steps for saved services missing the command (#1484).

  • 遅いビルドキャッシュスキャンからストレージを回復する

    When free disk space or inodes already block deployment, allow up to two minutes to measure unused, owned build caches before reclaiming them. Healthy hosts retain the short best-effort scan; defer timed-out SSH measurements during automatic retention without blocking unrelated builds. Explicit cleanup still reports measurement failures; active builders and application volumes remain protected (#1527).

  • 中断された最初の展開からイメージを再利用する

    Include projects that have never reached a running release in managed image collection. Resolve the last attempt through the existing tenant checks and retain the same rollback, retry, pin and in-use protections, so failed builds cannot fill the server with orphaned images.

  • クラウド アフィリエイト プログラム

    Create and revoke referral links with optional customer discounts, follow verified payments, renewals and expiry, and request reviewed cash payouts. Staff can review pending requests in a private operator queue and reconcile transfers, including after an account is deleted. Oblien owns the ledger and atomically reserves payout funds. The default minimum is $50, with trusted per-user overrides. Eligible monthly and annual Cloud compute starts at $10 per month equivalent; Manage, PAYG and top-ups are excluded. Program guidance lives beside the referral lists, with illustrated empty states, a two-step discount and plan picker, monthly/yearly eligibility enforced at checkout, encrypted manual payout accounts with immutable request destinations, payment-method guidance and a screenshot walkthrough in the docs. The program remains off until the provider and its explicit policy grant are configured.

  • 共有環境の編集を確認する

    Preview which services inherit an edited project variable, then save shared values and service overrides together. Stale reviews are rejected inside the write transaction; project write access is required, and saving alone does not restart applications.

  • 紹介チェックアウトと収益を明確にする

    Retain unavailable referral codes through sign-in until the customer removes them, and show commission per confirmed payment with renewals limited to the program's reward period.

  • イメージの更新が中断された後にマネージド サービスを復元する

    Attempt to restore the previous edge or mail image when replacement startup throws, including a lost SSH command channel after removal. Report unsuccessful recovery instead of treating a connection failure as proof of an outage (#1540).

  • 起動時に権限リソース名を検証する

    Reject unknown permission leaf types during route registration using the shared authorization validator, so misspelled tags cannot reach request-time resource resolution (#1521).

  • 選択したアプリのソース環境をロードします

    Use the app folder's openship.json 存在する場合はリポジトリのルートにフォールバックし、存在しない場合はセットアップ中に表示される構成と一致します (#1480)。

  • 選択した GitHub トークンを使用してプライベート サブモジュールを認証します

    Support relative, HTTPS, SSH and recursive private dependencies through the shared deployment credential helper, while preserving repository and namespace scope and keeping credentials out of saved remote URLs (#1522).

  • Docker 回の再起動試行とポート マッピングを保持します

    Retain configured on-failure 再試行制限とコンテナ作成中のすべての公開バインディング。

  • 最初の展開前にエッジ ルートを使用可能な状態に保つ

    Resolve domains through the project's saved server binding, preserve the origin of password-form submissions, and forward the visitor country to upstream applications. Document the scope of edge password protection and direct-port access (#1498, #1515, #1506).

  • デプロイメントソースのアイデンティティをそのまま維持する

    Expose the selected revision as OPENSHIP_COMMIT_SHA、伝送された Compose イメージ ダイジェストを保持し、設定された展開パスを一貫して適用します (#1499、#1475、#1472)。

  • 適切なダッシュボードのフィードバックを表示する

    Use custom apps' own logos, keep open card menus above adjacent controls, and clarify expiring-domain notifications (#1508, #1518, #1512).

  • 更新勧告の範囲を維持する

    Keep installation-specific notices scoped in Monitoring and recheck deployment eligibility before presenting update actions (#1467).

  • クラウドの価格を請求期間に合わせて調整する

    Present management plans and recurring compute charges using their actual billing periods (#1466).

  • デスクトップ リリース ビルドを利用可能な状態に保つ

    Build and notarize macOS installers on the supported macOS 15 runner.