12 Eki2026v0.9.0ÖzelliklerDüzeltmeler40 güncellemeBağlantıyı kopyala
OpenShip İşlem
CI'yı GitHub İşlemden bağımsız olarak çalıştırın
Workflows in
.openship/workflows/GitHub tarzı YAML'yi kullanın ve seçilen hedeflerde OpenShip üzerinden çalıştırın. Bunları manuel olarak, depo itme veya çekme istekleriyle, programlara göre, kimlik doğrulamalı gönderim yoluyla veya Jobs'tan tetikleyin. GitHub, iş akışının kendisini çalıştırmadan kaynak, olaylar ve taahhüt kontrolleri sağlayabilir.OpenShip koşucuyla mevcut GitHub iş akışını kullanın
Workflows in
.github/workflows/GitHub adlı kişinin orkestrasyonunu, sırlarını, ortamlarını ve Kontrollerini saklayın. OpenShip destinasyona resmi koşucuları kaydedin ve onların kendi kendine barındırılan etiketlerini hedefleyin. GitHub tarafından barındırılan etiketleri hedefleyen işler hâlâ GitHub üzerinde çalışıyor; bir iş akışının içe aktarılması, yürütme platformunu sessizce değiştirmez.Tek iş akışı düzenleyicisi
Import multiple workflow files from a repository or create a standalone workflow. Topology, list and YAML views share the same draft. Connected job and step nodes, inline step editing, per-file trigger rules, branch controls and repository-change review keep setup in one flow. Repository sync can apply updates automatically or wait for confirmation.
Yeniden kullanılabilir iş akışları ve gelişmiş işler
Local and authorized remote reusable workflows support nested calls, typed inputs, secret forwarding and outputs. Dependencies, matrices, expressions and job permissions use the pinned execution engine rather than a second shell-only workflow implementation. Unsupported constructs return explicit errors instead of being silently skipped.
Doğrulanmış yeteneklere göre koşucuları seçin
Destinations report operating system, architecture and available tools. Linux runners support container images and explicit QEMU setup for supported cross-architecture execution; macOS runners use native tools. Runner labels and job images are separate settings. Create a runner from the shared server picker without leaving workflow setup.
Yürütmeden önce erişimi gözden geçirin
Workflow access can be limited to your account or selected repository users, with approval required for each attempt. Approvals bind the actor, commit, attempt and destinations. Fork code is blocked by default; explicitly approved fork execution uses disposable Cloud runners without privileged secrets or write credentials. Work never falls back to an unselected control-plane host.
Yerinizi kaybetmeden koşuları takip edin
Expandable jobs and steps sit beside masked logs, with a topology view and a separate approvals tab. Waiting work has visible progress; selection and log position survive refreshes. Independent runs stream logs in Openship. GitHub-coordinated runs link to live GitHub logs and import completed logs.
Yapılar, önbellekler ve OIDC
Independent workflows support artifact/cache actions through scoped storage access and configured backup destinations. Jobs with
id-token: writebir HTTPS örneğinden kısa ömürlü OpenShip OIDC belirteci isteyebilir. Kimlik sağlayıcıların OpenShip veren kuruluşa açıkça güvenmesi gerekir; bunlar GitHub tarafından verilen jetonlar değil. İmzalama anahtarları örnek hareketlerle seyahat eder.Sınırları bilin
Independent execution does not implement GitHub protected environments or attestations. Windows runners and GitHub Enterprise Server are not supported. A fresh independent run does not resume or replace a failed GitHub run. Native runners and runners with a host Docker socket execute trusted code with that server user's access; use disposable VMs for stronger separation.
Cloud Actions hedefleri ve finansmanı
Bir sunucuyu yeniden kullanın veya ekleyin
Actions can use an existing authorized Cloud server pool or a dedicated managed server purchased through the normal catalog. These use the server's existing capacity and billing.
İş başına geçici koşucular
Prepaid Actions profiles provide Linux VMs with 2 vCPU / 4 GiB RAM / 40 GiB disk, 4 / 8 / 80, or 8 / 16 / 160. Executable jobs provision a temporary VM and remove it after cleanup; queued work allocates no VM. Temporary runners use a separate prepaid balance covering provider compute and transfer charges, rather than an application's monthly server allowance.
Finansman ve kurtarma
$5, $20, $50 And $100 top-ups use hosted checkout. Provider-confirmed payment funds the runner budget; duplicate receipts cannot grant credits twice, and background recovery continues if the browser closes. Setup failures retain paid credit for retry. Pricing and estimated minutes use the provider's current tariff, not guaranteed fixed minutes.
Bulut operatörü kurulumu
Temporary-runner purchases require enabled Cloud billing, provider credentials and live pricing. Regular-server PAYG purchases remain disabled. Verify a real paid Actions top-up before enabling the purchase flow for customers; automated payment recovery tests and live VM execution do not replace that checkout test.
GitHub Kontroller ve bildirimler
Dağıtım Kontrolleri varsayılan olarak etkindir
Repository-backed deployments can publish project/environment results and individual service Checks, including deployment failures. Configure the selected Checks and their names or disable reporting from project settings and the project wizard, in self-hosted and Cloud installations.
Kurulumun gerçek erişimi gösterip göstermediğini kontrol eder
Workflow setup displays the connected GitHub account, repository and access status, with inline connect, review and retry actions. Independent reporting requires a GitHub App with Checks write access; a personal token or CLI source connection alone does not grant it.
Bildirim kanallarını satır içi ekleyin
Create a channel using the shared Settings form, send a test, then select it without leaving the workflow. Unverified channels remain unselected until verification succeeds. Completion notifications cover selected outcomes with durable delivery and retry.
Bir bildirim düzenleyicisi
Instance defaults and project overrides use the same channel controls. Failed preference reads show an error and retry rather than editable empty defaults; account switches discard stale settings.
Masaüstü bağlantıları ve örnek taşıma
Kontrolü bir sunucuya taşıyın
Settings → Instance can deploy an API-only instance for Desktop access or an API and dashboard for browser access. Select a connected or managed Cloud server, configure its address and review the move. Projects, users, server connections, credentials, history and settings transfer together while application workloads remain on their existing servers.
En son verileri kullanarak geri dönün
A connected Desktop can receive the current remote instance, including changes made on the server. Existing hosted instances can also move to Desktop. Both ends verify compatible versions; interrupted transfers retain a journal and recovery snapshot and can resume without activating two controllers or reverting to stale local data.
Verileri taşımadan bağlanın
Enter an existing instance URL and sign in, or use a short-lived connection code from your signed-in account. Desktop connects to that instance with your permissions; returning to the local instance resumes its separate data.
Davetiyeler Masaüstünde açık
Team invitations offer email delivery through the configured mail service or a copyable, recipient-bound link. Links open Desktop when available, with a manual URL fallback. Recipients sign in and review the instance, workspace, inviter and role before accepting. Team and webhook settings link to the same hosted-instance setup when a public control plane is required.
Yönetilen Bulut sunucuları, derlemeleri ve barındırma
Sunucu erişimini tek yerden yönetin
Managed server tabs expose settings, boot logs, SSH access, temporary credentials, Runtime API token reveal/rotation and manually managed workloads. Outbound internet and hostname allowlists use revision checks and preserve unrelated ingress, routes and private networking.
Dayanıklı yapı kabulü
Explicitly submitted builds queue against their selected server's saved offer and available resources. Different projects can build concurrently when capacity allows; the same project's builds remain serialized. Queue position, waiting reasons and upgrade actions are visible. Image-only deployments do not reserve a source-build slot.
Kaydedilen plan ödenekleri
New Hobby, Starter, Pro and Scale offers enforce project/app, running-service and build-admission ceilings. Existing purchases retain their saved terms. Physical CPU, free memory and host headroom can admit fewer builds than the plan ceiling; explicit resource requests are not silently reduced. These Cloud quota gates do not apply to self-hosted servers.
Kesintiye uğrayan yapıları güvenli bir şekilde kurtarın
Durable activity ownership coordinates builds, backups and server maintenance across controllers. Capacity is released after tracked commands and Docker-owned BuildKit workers are confirmed stopped. Crash recovery settles interrupted deployment state before acknowledging its execution, preserves live releases and retries failed recovery writes.
Statik siteler varsayılan olarak Cloud Pages'i kullanır
Build on the selected managed server and publish the static output without retaining an application container. Choose Managed server hosting when an nginx container is preferred. Each release saves its hosting choice for rollback; failed publication preserves the previous site. Backend applications keep their server runtime even when static assets exist.
Daha güvenilir uygulama başlatma
Generated Node images respect declared Node requirements and explicit image pins. Managed public Node listeners can adapt loopback bindings without exposing private listeners. Cloud verifies startup before reporting container deployments ready and surfaces crash details.
Tutarlı paket yöneticileri
Generated npm, pnpm, Yarn and Bun builds honor explicit versions, supported lockfiles and monorepo parent settings, then verify the executable actually used. Private catalog services retain private access; public services use their selected domains. MinIO installation and required catalog setup are more reliable.
Dağıtım, yönlendirme ve izleme düzeltmeleri
Açıkça başka bir bağlantı noktası seçin
When a host port is occupied, deployment review can suggest a free alternative and let you confirm it. Existing ports do not change silently. Bare redeployments recognize their own previous release, and private service port access binds to localhost.
Yönlendirme durumunu tutarlı tutun
Route repairs update the banner and route cards together, retain repair logs across refreshes and reconnect interrupted streams. Proxy overrides validate target capabilities before saving and preserve existing configuration when unsupported.
Sunulan uçta Cloud HTTPS'yi doğrulayın
Custom-domain checks validate the publicly served certificate, hostname and chain rather than relying only on provider metadata. Scheduled checks use bounded work and failure backoff; unavailable observations stay unknown instead of becoming successful results.
Bağlantı kaybını istek hatalarından ayırt edin
An API request error no longer marks unrelated services offline. Monitoring retains meaningful last observations, reconnects dropped streams and offers retry for failed reads. Terminals remain usable when status reads fail.
İzlemede dağıtım sonuçları
Projects show completed outcomes and failed deployments alongside application monitoring. Project cards, grids and backup history use more consistent spacing and responsive layouts.
Derleme ve çalıştırma zamanı doğruluğu
Preserve Dockerfile startup defaults, native service source precedence, case-sensitive manifest names and monorepo Docker build-context metadata. Compose projects keep service detection on redeploy. Exec cancellation reliably reaps watchdog timers, including BusyBox hosts. Cloud cleanup follows the saved keep-resources policy. Shared storage removal keeps Longhorn's bounded native retry for an uninstall startup cache race and waits for confirmed completion before cleanup.
Teşhis, CLI, SDK ve web postası
Yapılandırılmış hata raporlama
API boundaries, authorization failures, deployments, jobs, streams and dashboard errors share a classified, redacted event format with request references and bounded asynchronous delivery. Cloud stores sanitized events in its own database. Automatic collection and upload remain disabled for Desktop, self-hosted installations, native workers and CLI, including Desktop connected to Cloud; operational errors still have local logs.
Daha geniş otomasyon kapsamı
Native and remote SDK operations cover Actions, instance connections, managed server controls, migrations, mail and terminals. The CLI shares platform contracts, expands Cloud and remote operations, accepts
/apiyolları ve konumsal ortam çiftlerini oluşturur ve kullanıcıları yetkilendirme hatalarında oturum açmaya yönlendirir. Eylemler aracılığıyla kullanılabiliropenship api; bu sürüm özel bir özellik sunmuyoropenship actionskomuta grubu.Güncellenmiş belgeler
Actions setup, independent versus GitHub execution, runner access, Cloud funding, instance moves and API/SDK/CLI/MCP references cover the new flows, with live execution verification records.
Web posta iyileştirmeleri
Editable email signatures apply in the composer; replies include the original message body. Sign-in recovery and managed deployments are fixed. Cloud shows mail availability before loading unsupported server controls; Desktop and self-hosted mail remain available.
Ek uyumluluk düzeltmeleri
Preserve cookie encoding in dashboard server requests, complete partially applied instance-controller migrations, filter invalid custom app templates, and add Farm.js configuration support and its square icon. Whole-instance recovery rebinds the imported local administrator atomically, preventing project reads from failing after a database wipe.
Sürüm doğrulaması
Required gates cover real Linux and macOS Actions execution, instance moves, Docker deployment/rollback, scaling and shared storage, HTTPS, database upgrades and installed SDK packages. Failed release work can resume with verified successful checks and notarization checkpoints.
Güncelleniyor
Desktop 0.8.2 kullanıcıları yerleşik güncelleyiciyi kullanabilir. Hala 0.8.0 veya 0.8.1 sürümünü kullanan masaüstü kullanıcıları, 0.9.0 yükleyici ve manuel olarak bir kez yükleyin. OpenShip uygulamasından çıkın ve uygulamayı değiştirin; Projeleri, sunucuları ve ayarları korumak için uygulama verilerini saklayın. Sunucu/CLI güncelleme yolu bu masaüstü kurtarma adımını gerektirmez. API'yi ve kontrol panelini birlikte güncelleyin; örnek hareketleri her iki uçta da uyumlu sürümler gerektirir.