Registro de alterações

O que há de novo

Recursos, correções e melhorias enviados em OpenShip.

31 lançamentos
18 de nov.2026v1.0.1RecursosCorreções13 atualizações

Recommended update for self-hosted startup, application image updates, and private GitHub repository access. This patch also fixes postmaster password rotation metadata and preserves referral attribution through Cloud deploy links.

Deployments and connections

  • Application updates

    Accept requests with an empty body when the action takes no options. Continue validating malformed JSON and required payloads (#1817).

  • Container image refresh

    Pull the current image when refreshing a mutable tag, and keep verified local images available for redeploys. Report failed refreshes before replacing a running service (#1816, #1819).

  • Registry credential checks

    Record confirmed login rejections and preserve the previous credential status when the registry response is inconclusive (#1816, #1819).

  • Private GitHub repositories

    Restore the connected-server token fallback for authorized self-hosted repository reads on GitHub.com. A local server without credentials no longer prevents selecting an eligible connected server (#1821, #1822).

  • Custom PHP base images

    Run build-time dependency and setup steps as root when the base image defaults to a non-root user. Keep the app running as www-data (#1810).

  • Swarm network setup

    Wait for Docker to allocate a new overlay network before checking its driver and encryption settings.

CLI and mail

  • macOS service reinstall

    Wait for launchd to unload the previous service and verify the replacement is running before reporting success (#1808).

  • CLI shutdown during startup

    Stop the API process when the foreground supervisor receives a stop signal, releasing the port and local database lock (#1809).

  • Postmaster password rotation

    Record the password change timestamp together with the new hash when rotating through the CLI or API (#1825).

Cloud and website

  • Cloud deploy referrals

    Retain the referral code through the deploy link and Cloud plan selection (#1806).

  • Social previews

    Use page-specific share cards across the website and documentation (#1824).

Notas de atualização

  • Component updates

    Update the API, dashboard, Desktop and CLI for your installation. This patch adds no control-plane database migrations.

  • Image refreshes

    Use Refresh images when you want a new image for a mutable tag. A normal redeploy can reuse the local image.

16 de nov.2026v1.0.0RecursosSegurança42 atualizações

OpenShip 1.0 brings a refreshed dashboard, edge maintenance and custom pages, deploy links, and scheduled mail workflows. Includes every change since 0.9.12, with more reliable builds, imports, billing and recovery.

Recommended update: administrators should update all OpenShip components. This release closes an authorization flaw that allowed ordinary organization members to invoke administrative operations, including host command execution.

Security and access

  • Administrative authorization

    Require administrative authority across HTTP, SDK, native and MCP access. Scoped tokens remain bounded by their owner's current organization role, including after demotion. Preserve explicitly delegated, resource-scoped administration (#1783, #1784).

  • Hostname sign-in

    Choose a sign-in page or the browser's native authentication prompt for self-hosted hostnames. Customize sign-in HTML and session duration, revoke sessions, and see enabled protection directly on domain cards.

  • Actions tracing

    Update the Actions worker to OpenTelemetry 1.47.0, fixing bypassed attribute-length limits in its tracing dependency.

  • Release build isolation

    Keep generated local mail credentials and runtime caches out of image build contexts. Bundle the shared assistant client and its dependency patch so release builds do not depend on a sibling checkout or baked development URLs.

  • Website image verification

    Include the website's client-message generator in its Docker build, and verify the production website image and its public pages before release.

Edge pages and routing

  • Edge maintenance

    Serve maintenance HTML directly from the edge while the application keeps running. Restore normal routing when maintenance is disabled.

  • Custom error pages

    Upload HTML pages and assign error statuses, with server defaults and project or hostname overrides. Customize unmatched-host and direct-IP pages.

  • Authentication header limits

    Accept larger authentication response headers and returning cookies at the edge, with bounded defaults and preserved custom buffer settings (#1763).

  • Domains & Routes

    Organize Domains & Routes into routing, access, proxy, and page controls, with inline protection settings, HTML previews, and visible loading and retry states.

  • CLI domain targeting

    Target the correct project service and port when adding domains from the CLI. Keep primary domains, aliases and www redirects consistent when editing routes.

Deployments, imports and recovery

  • Shareable deploy links

    Add shareable deploy links and openship launch, carrying the selected repository and deployment intent through sign-in and installation.

  • Independent service copies

    Copy selected services to the same server or another server as independent projects. Validate dependencies and port bindings, preserve separate volumes, and improve restoration and rollback if a transfer fails. Keep application instance scaling distinct from independent copies.

  • Compose change review

    Review Compose changes in a shared before/after dialog and apply the exact reviewed revision without repeating setup. Preserve deployment options and saved overrides, mask credentials, and require a new review if source changes (#1796).

  • Private registry guidance

    Explain private-image pull failures with the affected image and a direct link to registry connections. Preserve public-image recovery and distinguish registry credentials from GitHub repository access (#1798).

  • Compose environment values

    Reveal and hide service environment values through the shared Compose editor while retaining the existing permission checks (#1771).

  • Multi-repository Railway imports

    Import Railway projects with multiple repositories as native services and project connections, preserving source ownership and private service wiring.

  • Compose web ports

    Show container ports declared with Compose expose, explain how to publish a TCP port for a web domain, and handle protocol suffixes and port ranges.

  • Folder deployments

    Improve folder deployment names, scan errors and streamed uploads. Resolve template placeholders consistently in service ports, and explain recovery when duplicate containers block deployment.

  • BuildKit cache retention

    Retain warm BuildKit caches and reduce remote cleanup overhead without dropping build ownership, cancellation or capacity checks.

  • Empty-volume backups

    Back up verified empty Docker volumes and bind directories alongside populated sources. Refuse missing sources and preserve errors for unavailable storage.

  • Redis Sentinel readiness

    Verify every Redis Sentinel has discovered the writable primary, its replicas and the full voting group before reporting replicated databases ready.

  • Controller relocation

    Fence event-stream admission while relocating the controller, restore access when it resumes, and link server preparation to its deployment progress.

  • Mail engine updates

    Preserve the mail host's configured ignored IP addresses when updating its engine.

Mail and agents

  • Scheduled mail and snoozing

    Schedule messages, cancel queued mail with Undo Send, and snooze conversations. Recover interrupted or temporarily failed wake-ups, including messages moved or deleted before their wake-up time.

  • Mailbox agents and MCP

    Connect mailbox-scoped agents and MCP clients with encrypted state, isolated runtimes, scoped permissions and explicit approval for sending mail.

  • Assistant workspace

    Improve the agent workspace, shared conversation rendering, connection setup, and empty and error states. Add the OpenShip plugin directory submission metadata.

Cloud, billing and CLI

  • Oblien provider API

    Move the Oblien integration to SDK 3.2.0 and the provider's native versioned VM API. Preserve saved VM identities, customer metadata and purchased offers; validate scoped credentials against the selected VM.

  • Cloud checkout recovery

    Recover unfinished Cloud purchases instead of creating duplicate unpaid spaces. Open checkout after its payment URL is ready and retain a fallback action.

  • Renewals and pricing

    Keep billing accessible during pending renewals and show payment warnings in Plans & billing. Align monthly and yearly pricing across the website and dashboard.

  • Cloud setup recovery

    Recover repeated signup attempts during Cloud linking and improve first-admin recovery and Compose managed-edge setup.

  • CLI install and sign-in

    Keep the installed service's existing ports when openship up runs again. Support CLI login through public instance URLs and use Node.js for the container-to-host connectivity probe.

  • Cloud update notices

    Limit the managed Cloud update banner to verified workload-security notices.

Dashboard and website

  • Dashboard refresh

    Refresh billing, monitoring, jobs, backups, connections, server and agent screens with shared illustrations, compact controls and theme-aware surfaces.

  • Service controls

    Improve service inspectors and copy/scale flows, put actions before runtime details, and replace native disclosure markers with shared icon controls.

  • Avatar and project icons

    Add avatar and project icon URL settings, with inline editing, previews and reset.

  • Marketing site and docs

    Refresh landing, Cloud, mail, download, migration and app-catalog pages; improve Arabic headlines, language navigation and documentation navigation.

  • Comparisons and Cloud information

    Expand product comparisons, feature pages and search discovery, and publish Cloud SLA, support and privacy information.

Notas de atualização

  • Component updates

    Update the API and all its replicas, dashboard, Desktop, CLI and mail components together. This release includes database migrations; retain a current instance and database backup before updating.

  • Organization roles

    Ordinary organization members no longer have implicit administrative access. Review membership roles and scoped grants for integrations that perform admin actions.

  • Oblien provider rollout

    Cloud operators must coordinate this release with the matching Oblien /v1 API, database, gateway and scoped-credential rollout. Review old unversioned OBLIEN_API_URL and gateway overrides, and verify existing-VM access before directing customers to the upgraded provider.

  • Edge requirements

    Maintenance, custom edge pages and hostname protection require the updated self-hosted edge. These controls do not protect direct application ports or hostnames outside their configured scope.

  • Service copies and database scaling

    Independent service copies are separate deployments. Managed database replicas and failover use their existing database scaling flows.

12 de nov.2026v0.9.12RecursosCorreçõesSegurança46 atualizações

Critical update for build-secret protection, database upgrade repairs and backup/restore reliability. Includes all changes since 0.9.11, with reviewed source-image update PRs, platform imports, mail improvements and a translated website.

Crie segurança

  • Passe ambientes de compilação Docker gerados por meio de segredos temporários do BuildKit em vez de incorporar valores em Dockerarquivos ou histórico de imagens. Mascare valores configurados em logs transmitidos, resumos de erros e notificações de falhas, incluindo saída dividida e multilinha. Preserve os limites do trabalhador na nuvem, a criação de servidores paralelos e a limpeza após o cancelamento.
  • Attribute REST audit events to the personal access token used, and audit token reads through the existing authorization path.
  • Preserve private edge-vhost permissions and verify access with unprivileged workers. Keep tunnel hostnames out of unsupported password-protection flows.

Runtime and source updates

  • Mantenha os serviços de imagem com resumos de implantação ausentes visíveis como não verificados. Inspecione a imagem em execução por meio do tempo de execução de implantação existente para detectar tags movidas, com leituras limitadas e sem gravações de linha de implantação. Mostrar status de atualização indisponível sem um selo de atualização.
  • Propose Dockerfile and Compose image changes through reviewed GitHub pull requests. Check repository access first and guide users to reconnect or update their GitHub installation when the required permissions are missing.
  • Apply security fixes to managed runtime versions instead of repeatedly refreshing an unchanged image. Distinguish a runtime that is absent from a failed probe.

Deployments and infrastructure

  • Allow webhook and CLI deployments to approve reviewed Compose source changes through the shared approval flow.
  • Keep branch and Compose-path controls available after an unsuccessful first scan, reject blank required build commands, and offer Static Site for folder uploads.
  • Keep token-authenticated repository clones on HTTPS even when a server's global Git configuration rewrites GitHub URLs to SSH.
  • Recover orphaned builds through shared worker ownership, preserve application runtime/log access when adding services, and scope shared image-export paths.
  • Scale managed build-cache budgets with available disk and expose server cache settings. Improve local image exports without sharing another build's output.
  • Let edge upgrades finish safely after an SSH disconnect. Preserve owned mounts in imported Cloud workloads and explain host paths that cannot be imported safely.
  • Support hosted Jobs on Manage-connected SSH servers. Match BullMQ repeatable jobs by name so changing a cron schedule removes the previous schedule.
  • Accept bounded YAML aliases in imported GitHub workflows, show the latest run for every workflow, and avoid duplicate GitHub-owned workflow webhook payloads.
  • Recover failed installed-CLI updates and verify release installation and updates on disposable VPS instances before publishing images and packages.

Domínios

  • Configure static HTML, JSON or text responses on a domain through its normal route editor, including maintenance and verification responses without an app container.
  • Evite reescrever arquivos de rota de borda inalterados e repetir leituras remotas durante um registro. Preserve o conteúdo e as permissões exatos dos arquivos, mantendo a validação de rotas, recargas, ativação de certificados e reversão transacional.
  • DigitalOcean DNS

    Connect a DigitalOcean token in Settings → Connections to preview and apply a custom domain's records and issue DNS-verified HTTPS automatically, as with Cloudflare. Each record OpenShip creates is paired with an _openship-owner Marcador TXT, portanto, a remoção de um domínio exclui apenas os próprios registros de OpenShip.

Imports, backups and database upgrades

  • Improve platform imports, including Railway and Vercel setup, source and destination review, progress reporting and cancellation.
  • Keep migration environment fields visible while entering missing secrets, with a plain section heading instead of a nested disclosure that collapses during editing.
  • Preserve source project boundaries during platform imports

    One project contains its native services, private DNS, encrypted service environments and separate volumes. Keep service environment values scoped correctly during source builds too.

  • Carry imported custom domains and aliases through the existing migration routing flow, pending normal verification. Show DNS cutover guidance and replacement notices for Railway and Vercel URLs in review and saved migration progress.
  • Restore portable instance exports with their server credentials and workspace ownership. Normalize restored data for the destination schema and keep the instance import and server selection views consistent.
  • Repair missing workspace and security-advisory fields on upgrades, including databases whose earlier migrations were already marked as applied.
  • Serialize backup execution per destination to prevent connection exhaustion. Recover orphaned Cloud backup activities through the existing ownership checks.
  • Complete local mail backups and portable restores through the shared backup orchestration, including target-server mail configuration and real mail round trips.
  • Prevent browser autofill of backup destination credentials and keep destination menus visible outside their cards.

Correio

  • Preserve mail logs and Fail2ban ban history across engine updates, and remove Dovecot's stale PID file before startup.
  • List all signed-in mailboxes and keep account menus usable when they overflow.
  • Correct webmail message colors in light/dark themes and when printing, and refresh security dependencies.
  • Protect support intake and add mailbox sender blocking.

Assistants

  • Reuse managed agent setup for custom API connections and report the actual runtime setup state.
  • Find agent CLIs installed outside the macOS GUI PATH, restore public BuildKit pulls, and correct scoped Claude startup.
  • Allow reviewed repository patches to delete regular files through the existing review and validation flow.
  • Add OpenShip plugins for Codex and Claude Code.

Dashboard, billing and website

  • Keep the shared destination dropdown available with one server or Cloud plan, with Add server in its menu across deployment and migration flows.
  • Refresh deployment state after navigation and browser resume. Unify project settings and shared environment controls with the existing service views.
  • Keep plan overview, usage and payments together under Plans & billing, align Cloud plan presentation across the website and dashboard, and retain payment recovery for expired renewals.
  • Improve deployment, verification and cancellation emails, and standardize the Referral experience.
  • Translate website content into the existing supported languages, with localized URLs, navigation and product screenshots. Correct Arabic layout and preserve English framework names. Documentation remains in English.
  • Add migration guidance for teams moving an existing app, group website navigation, and provide a direct Start on Cloud action.
  • Use the BytesMap SDK for unified Cloud telemetry and remove PostHog.

Notas de atualização

  • Update the API (including all replicas), dashboard and Desktop app together. This release includes control-plane database migrations

    Keep a current instance/database backup before upgrading.

  • Build-secret protection applies to new builds. Rebuild older application images to use the updated build flow

    Upgrading does not rewrite existing images.

  • Dockerfile and Compose image pins remain controlled by the repository. Review and merge a source-update PR when the fix requires a source change, then deploy that revision. Refreshing an unchanged pin does not change its runtime version.
  • Update the mail engine as well to receive mail startup, log persistence and restore fixes.
6 de nov.2026v0.9.11RecursosCorreçõesSegurança31 atualizações

Atualização recomendada para recuperação de login do Desktop, conexões de assistente, verificações de repositório e confiabilidade de implantação. Inclui todas as alterações mescladas no main desde 0.9.10, com melhorias na administração de correio e atualizações de segurança de tempo de execução mais claras.

Assistentes e área de trabalho

  • Login do Codex em instâncias hospedadas

    Use device-code sign-in on Cloud, VPS and remote assistant hosts, while keeping browser sign-in on the local Desktop host. Explain the available method in AI connections, use the shared ChatGPT mark, and update the Mindwire runtime and SDK to 0.1.61.

  • Recuperação de conta de desktop

    Preserve verified sign-ins during refresh and startup, and remember the administrator selected through Desktop's authenticated sign-in. Missing or stale Local User cookies recover to that saved identity without selecting an unrelated user's session or changing account permissions.

  • Código Claude em macOS

    Make the system keychain available inside the isolated assistant home so sign-in can complete.

  • Investigações e perguntas

    Start an explicitly requested deployment investigation when the assistant is ready. Answer agent questions above the composer while retaining drafts, separate answer state and retry behavior. Keep expanded questions focused and the latest-messages control readable.

  • Configuração do espaço de trabalho do assistente

    Keep connection setup inline and use the shared drawer for agents and automations. Preserve unfinished configuration and the underlying chat, recover access to changed specialists, and refresh activation reviews when saved settings change.

Implantações, roteamento e segurança

  • Compor atualizações de comando

    Resolve authored command expressions against the current service environment during deployment and Apply environment. Preserve referenced file defaults and explicit command edits without exposing internal source metadata as environment values.

  • Falhas na aplicação do ambiente

    Show structured startup, health, restart and OOM evidence while retaining the existing replacement and rollback flow. Keep credentials and unrestricted provider error text out of responses, monitoring, notification failures and backup diagnostics.

  • Mudanças de ambiente estático

    Offer Rebuild and redeploy for static sites and single-app Cloud deployments whose variables cannot be applied through a runtime-only refresh. Open the new build's progress and retain retry controls.

  • Comportamento estático 404

    Add an explicit SPA fallback setting to shared routing controls, the API and openship.json. Mantenha o substituto do SPA ativado por padrão; desativá-lo retorna respostas 404 reais e usa 404.html quando disponível.

  • Compor inventário de borda

    Inspect loopback upstream ports through the edge's own connection, including mounted Docker sockets without host SSH. Quarantine existing routes before allocating ports and continue refusing unreadable or ambiguous inventory.

  • Varreduras de repositório privado

    Allow the only eligible connected server's stored token when an organization has no local server. Ask for an explicit server when several qualify, retain the choice across scan retries, and keep public reads anonymous when no credential is needed.

  • Docker importações estacionadas

    Offer an explicit finish-without-restart decision for imports awaiting cutover. Keep originals untouched and provide actionable guidance when a parked migration prevents project deletion.

  • Limites do host na nuvem

    Enforce shared safeguards against local workload execution on the SaaS API host while retaining authorized managed-server and SSH execution. Keep command availability probes separate from execution.

  • Avaliações de segurança condicional

    Distinguish PHP's conditional session upload-progress review from confirmed runtime vulnerabilities. Share advisory guidance while retaining each service's confidence, progress and actions; offer saved configuration and an editable, scoped Fix with AI request without automatic submission. High and Critical warnings retain their priority.

  • Conflitos de remoção de banco de dados

    Reread controller state after explicit Kubernetes version conflicts during database cleanup. Retain object identity, ownership, generation and operation fences while tolerating status-only updates.

Catálogo de correio e aplicativos

  • Gerenciamento Fail2ban

    On self-hosted mail installations, inspect jail counters and banned addresses from Health, the API, SDK and MCP. Review the exact address and jail before banning or unbanning; stale observations disable changes until refreshed.

  • Remetentes de alias diretos

    Allow active direct aliases to authorize their owning mailbox consistently across mail sender checks. Disabled aliases, external forwards, catch-alls and alias chains grant no sender identity. Clarify the distinction between incoming forwarding and direct-alias sending in the UI.

  • Configuração de gravação de aplicativo

    Deduplicate generated credential writes and verify owner bootstrap before reporting success. Exclude the optional Geo service while its upstream PHP runtime remains affected, and document the geolocation limitation.

  • Verificação de atualização de segurança

    Reject unchanged-image refreshes, track manual remediation through deployment and runtime inspection, and show progress or a verified failure instead of silently repeating an ineffective update. Validate Compose hostname availability against scoped Cloud ownership receipts.

  • Imagens da Supabase

    Update the catalog's Storage, Meta and Studio image pins for the bundled Node.js/Brotli security fixes.

  • Preparação para RabbitMQ

    Run probes as the image's RabbitMQ user and wait for the management listener, avoiding the startup Erlang-cookie ownership race.

Dashboard, faturamento e documentação

  • Restauração de tema

    Render the saved base theme and background on the server through a validated cookie. Preserve custom theme caching, System mode and unsaved previews without flashing Light on refresh.

  • Devoluções de check-out

    Retain the purchasing organization, server and payment receipt through hosted checkout and authorized organization switching. Keep checkout retries tied to their original payment contract.

  • Falhas de gateway

    Request JSON from the API and explain upstream proxy errors with recovery guidance instead of showing an opaque status or HTML page.

  • Análise de primeira implantação

    Wait for an active deployment before reading traffic for a reserved domain. Start reads when deployment activates and retain existing traffic during redeploys; genuine provider failures remain errors.

  • Redação de início rápido

    Remove an abrupt line break in the setup description.

Notas de atualização

  • Atualize a API (incluindo todas as réplicas), o painel e o aplicativo Desktop juntos. Este patch não adiciona nenhuma nova migração de banco de dados do plano de controle.
  • Se uma instalação mais antiga do Desktop já mostrar apenas o usuário local e não tiver nenhuma identidade autenticada salva, use Voltar à configuração, continuar com a nuvem e faça login uma vez. Isso preserva os dados existentes e registra o proprietário para recuperação futura.
  • Aplique alterações na política do remetente de alias direto atualizando a imagem do mecanismo de email gerenciado, bem como o plano de controle. SQL personalizado e políticas de email nativas do host permanecem gerenciadas pelo operador.
  • Reimplante um contêiner de site estático gerado existente após alterar sua configuração de fallback do SPA. Os sites existentes mantêm o comportamento do SPA até serem explicitamente alterados.
  • Runtime security refreshes verify the deployed result

    An image that still contains the affected runtime requires a corrected image configuration rather than repeated redeployment. Appwrite's optional Geo service remains excluded.

4 de nov.2026v0.9.10RecursosCorreções17 atualizações

Patch recomendado para falhas de inicialização, recuperação e consentimento do Cloud Assistant na versão 0.9.9. Também corrige implantações, roteamento e restaurações, e inclui todas as alterações mescladas no principal desde 0.9.9, com aplicativos de catálogo adicionais e sincronização opcional de calendário/contatos.

Nuvem, agentes e GitHub ações

  • Recuperação do assistente de nuvem

    Preserve executable launcher permissions during workspace uploads and recover dead assistant endpoints after checking health inside the guest. Keep reachable busy daemons and existing profiles intact.

  • Retornos de chamada de consentimento

    Let the consent form own OAuth continuation so automatic navigation cannot consume the same callback twice.

  • Remetentes de e-mail do cliente

    Use the SMTP transport's authorized sender by default. Optional SMTP_SUPPORT_FROM e SMTP_BILLING_FROM os aliases exigem permissão de envio nessa conta SMTP; aliases ficam fora do Cloud Relay.

  • Preço de referência

    Show referral discounts consistently in plan cards for monthly and annual billing, using the existing shared pricing calculation.

  • Ações de solicitação pull

    Verify the executed merge against the captured base and head, and publish Checks on the pull request head. Preserve trusted workflow selection, fork restrictions and per-attempt Check identity.

Implantações, domínios e backups

  • Compor reconfiguração

    Retain existing DNS setup when redeploying to the same destination; request setup only for new hostnames. Normalize saved endpoint ports before submitting the deployment so source-review redeploys no longer fail with Expected string.

  • Implantações de imagens armazenadas

    Retain stored image-only Compose services and their environment when a containerized controller cannot read the original local directory. Source-built services still require their build inputs.

  • Serviço www redireciona

    Share the apex/www controls across the wizard and Add domain form, and support editing existing service redirects. Preserve portless redirect intent, reject missing targets and loops before service writes, and commit domain API changes with their service endpoint atomically.

  • Regras de rota curinga

    Enforce the configured wildcard virtual host's policies when no exact-host policy exists, while preserving exact-host overrides.

  • Segurança de restauração de volume

    Finish and validate the incoming archive before clearing destination contents. Failed, truncated or timed-out uploads preserve existing data; temporary staging files are cleaned up on completion or failure.

Catálogo, correio e painel

  • Catálogo de aplicativos

    Add Appwrite, Prometheus, Alertmanager, VictoriaMetrics, Loki, OpenTelemetry Collector, Beszel, Listmonk and pgAdmin4, with setup guidance, service icons and runtime smoke coverage.

  • Roteamento de porta de catálogo

    Publish Listmonk and pgAdmin4 on their own host ports instead of accidentally reusing another service's port.

  • Calendário e contatos

    Add an optional Radicale template and setup guidance for calendar/contact sync alongside the existing mail installation.

  • Detalhes do erro

    Add a copy action to error toasts for sharing diagnostics.

Notas de atualização

  • Atualize a API, o painel e todas as réplicas da API juntos. Este patch não adiciona nenhuma nova migração de banco de dados. Ao atualizar de uma versão anterior à versão 0.9.9, siga também as notas de autenticação, conexão e atualização SMTP dessa versão abaixo.
  • As restaurações de volume agora exigem espaço em disco temporário suficiente para preparar o arquivo de entrada antes da extração. A extração após validação não é transacional.
  • A verificação de versão retém o modelo 0.9.9 Compose publicado para que o portão de atualização teste a instalação anterior real, incluindo dados armazenados e rotas.
3 de nov.2026v0.9.9RecursosCorreçõesSegurança27 atualizações

Atualização crítica de segurança que abrange autenticação, aprovações de conexão em nuvem, isolamento de servidor e entrega de e-mail criptografado. Inclui todas as alterações mescladas no main desde 0.9.8, além de melhorias de implantação, faturamento, assistente e painel.

Segurança

  • Dependências de autenticação

    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.

  • Compatibilidade com OAuth e login

    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.

  • Aprovação de conexão em nuvem

    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.

  • Identidade e limites do cliente

    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.

  • Isolamento do servidor

    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 criptografado

    Require TLS for authenticated mail delivery, including verified STARTTLS on submission ports. Refuse a plaintext fallback when the server cannot provide the required encryption.

  • Catálogo Umami

    Update the PostgreSQL image to 2.20.2 and verify the catalog's configuration remains compatible.

Avisos de segurança e manutenção de host

  • Patches de host revisados

    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.

  • Manutenção observável

    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.

  • Preferências consultivas

    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.

Implantações e suporte de host

  • Compor revisão da fonte

    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.

  • Compilações Git fixadas

    Fetch a requested commit even when it is outside the cloned branch. Improve submodule preparation and credential handling across local and remote build paths.

  • Recuperação de borda

    Preserve unreadable virtual-host configurations during cleanup, and avoid identifying similarly named application containers as the OpenShip edge.

  • Anfitriões da arquifamília

    Use pacman for Arch/Manjaro package preparation and component version checks instead of Debian commands.

  • Dados GeoIP recentes

    Refresh and validate the country database before creating release tags, with a scheduled refresh workflow for ongoing updates.

  • Verificação de liberação

    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.

Nuvem, faturamento e e-mail

  • Recuperação de check-out

    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.

  • Escalonamento de provisionamento

    Send exhausted provisioning failures to support once, retaining the recovery context without duplicate escalation.

  • E-mails de clientes

    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.

  • Orientação sobre plano de nuvem

    Update the public plan descriptions and Hobby plan guidance, and make plan-selection hints more compact in the dashboard.

Assistentes e painel

  • Descoberta de modelo conectado

    List models through the connected assistant runtime and MCP, keeping connection setup and agent selection consistent.

  • Agentes em servidores Cloud pagos

    Prepare and run agents on an existing paid instance while preserving host access checks, profiles and sign-ins.

  • Atividade de ferramenta compacta

    Keep routine assistant lookups inline, with detailed previews available when useful instead of expanding every tool result into a card.

  • Domínios e referências

    Simplify domain actions and plan guidance. Use consistent referral wording across the dashboard and website, and place referral code entry below the plan controls.

Notas de atualização

  • 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) pares de contas antes de atualizar do Better Auth 1.6.

  • Substituir de autoria container: referências de namespace com service:<name> para um serviço na mesma pilha. As montagens de ligação de host estão desabilitadas por padrão. Operadores de instâncias auto-hospedadas confiáveis podem ativar explicitamente OPENSHIP_ALLOW_HOST_BIND_MOUNTS=true; As montagens de host em nuvem permanecem restritas.
  • O SMTP autenticado deve suportar TLS/STARTTLS verificado. Configure um endpoint de envio compatível com TLS se o endpoint anterior aceitasse apenas entrega de texto simples.
2 de nov.2026v0.9.8Recursos2 atualizações

Patch recomendado para restaurar a criação de agente com escopo definido e automações apoiadas por agente introduzidas na versão 0.9.7.

  • Tempo de execução do assistente compatível

    Update all Mindwire dependencies to 0.1.60, which supports the required bot protocol 9 and application-managed tools. OpenShip provisions the matching runtime on local and remote assistant hosts while preserving existing profiles and sign-ins.

  • Verificação de liberação

    Create, edit and reopen scoped Codex and Claude profiles against the actual released daemon, and verify scoped agent creation and reuse over SSH before publishing. Keep the protocol and permission checks.

1 de nov.2026v0.9.7RecursosCorreçõesSegurança18 atualizações

Atualização recomendada apresentando agentes de IA com escopo definido, automações revisadas e integrações de aplicativos de bate-papo. Inclui atualizações de segurança de dependências e todas as correções 0.9.6.

  • Personagens do agente

    Choose from 16 original flat bots with distinct silhouettes, gazes and expressions. Give default specialists a stable individual look across the switcher, automation setup and tool results, and preserve the chosen character when saving a new agent. Keep the chat header to the agent's name and role.

  • Monitorando atalhos de IA

    Prepare scoped repairs from the shorter Fix with AI action on app issues and a read-only workspace health report from the Monitoring header. Keep status labels in a dedicated column and move actions below details when the list is narrow.

  • Transferências de ação do assistente

    Offer a compact inline review when enabling saved automations, approve the exact revisions together, and continue the task in the same chat. Recheck existing permissions and reject stale batches atomically. Clarify that authorized MCP actions should be executed and verified, not handed back as manual instructions. Simplify the chat header and float the composer above the transcript without reducing its scrolling area.

  • Espaço de trabalho dos Agentes de IA

    Switch between the general assistant, specialists and automations in a collapsible 340px right column. Resume each agent's last valid chat, browse conversations from the header’s history drawer, and inspect automation runs with their existing investigation chats. Use a right drawer on mobile and keep agent configuration in the shared drawer. Simplify the conversation header and preserve scoped navigation, fresh requests and paused flow controls.

  • Edição de automação

    Show Trigger, Investigate, Respond and Notify as compact connected settings rows, with fields expanding in place and full-width hover/focus. Keep saved summaries visible while fields load, and use matching skeletons across the agents workspace, conversations and editors. Edit a selected automation inline in AI Agents using the same forms, permissions and save checks as the dedicated editor. Use one app/status line and Save/Cancel toolbar, and return to run history after editing. Reuse the row summary in expanded chat previews. Chat-created flows stay paused until reviewed.

  • Investigue com IA

    Open a prepared assistant request from failed deployment headers, failed app setup pages and active app issues. Keep the original app and deployment context through setup, use existing permissions, and scope the handoff to its originating account and workspace. Logs and errors stay out of shortcut URLs.

  • Agentes assistentes com escopo definido

    Create specialists with saved instructions, an AI connection and named resource permissions. Assign tasks or select a specialist in an automation. Each task uses one inspectable conversation, including live follow-ups, through the existing Assistant and MCP execution path. Add agent and automation tools to the normal API, inline task links, and paused flow drafts for user review. Bound each task to its original authority; recheck scope changes, deduplicate requests, and revoke temporary execution tokens on completion or agent edits. Manage agents in an animated drawer, expand creation and editing across the screen, choose a flat character avatar, and open scoped chats in the main assistant workspace. The chat header identifies the active assistant or specialist and the current conversation. Keep connection management in the overflow menu and Assistant settings.

  • Introdução aos agentes de IA

    Show what agents can do through selectable deployment, investigation and automation examples. Keep one enable action, a compact host choice and original Codex/Claude Code marks. Put setup first on mobile and show a permissions-shaped skeleton while access setup loads.

  • Identidade de arnês nativo

    Show Codex and Claude Code with their native marks across the composer, connections, history and agent settings. Preserve the harness’s original authentication prompts, including ChatGPT sign-in for Codex.

  • Assistente de bate-papo ao vivo e compositor

    Smooth incoming text and scrolling, expand live thinking, and show animated tool activity with reduced-motion support. Attach, paste or drop images with removable previews, and switch models between replies in the same conversation. Images use Mindwire's conversation-bound uploads on the selected agent host; size/type validation and existing workspace permissions apply. Show immediate send progress and keep activity visible between replies and tool steps; use a solid stop icon. Clear the composer on send and reset conversation input to a medium-height, two-line field; restore failed submissions with their original attachments for retry.

  • Redução do Assistente

    Render streaming replies with Streamdown, syntax-highlighted code, readable tables and nested lists across light, dim and dark themes. Keep copy controls tied to completed text and retain safe links without loading model-supplied images or executing raw HTML.

  • Acesso ao assistente e resultados da ferramenta

    Stop offering instance-only diagnostics to workspace-scoped MCP connections. Keep the shared instance authorization gate for direct calls, and refresh completed chats after permission edits. Retire stale access requests and carry the last request into a new chat as an unsent draft. Add expandable tool activity, per-call request/result inspection, and inline app, server, deployment, service and repository cards using the existing view/import flows.

  • Assistente em aplicativos de bate-papo

    Talk to your own Claude Code or Codex agent from Slack, Discord, Telegram and Teams through the existing Assistant runtime and MCP grant. Workspace allowance and personal opt-in start off. Conversations are isolated by sender and chat; history, resume, new and stop reuse native conversations. Continue chat-origin conversations in the dashboard with the same approved access. Choose dedicated Assistant, deployment-command or combined bots. Durable replies read the exact native turn, including after dashboard continuation, and survive delivery retries without replaying turns. Access changes stop further execution. Add settings and per-provider setup guidance; preserve private command replies and assistant threads in the shared chat transport.

  • Automações assistentes

    Add Assistant settings and an opt-in flow editor for failed deployments and confirmed service incidents. Investigate and notify, request approval, or explicitly choose app recovery and repository permissions. Support custom API endpoints and models, code fixes on new branches and draft PRs. Each flow stays within existing Assistant consent; exact patches are reviewed before approval and published through shared GitHub operations. Results appear in the agent conversation, with optional existing notification channels. Reuses MCP, deployment, jobs and notification paths, with private investigations, fresh health verification, run history, cooldowns and daily limits. Duplicate incidents and action retries cannot execute twice; changing access or pausing invalidates pending work. Cloud agents remain on the chosen customer server.

  • Comandos do aplicativo de bate-papo

    Connect Slack, Discord, Telegram or Microsoft Teams in Settings to list projects, check deployments, open private logs, and confirm redeploys or restarts. Each sender links their own account through the existing permission flow. Commands are opt-in, use the normal deployment path without AI, and deduplicate provider retries. Slack Socket Mode, Discord Gateway and Telegram polling work from Desktop or private servers without a public URL. Connections report their status, reconnect and recover durable cursors; Teams retains its public HTTPS webhook requirement. Bot connectivity runs directly in OpenShip with encrypted credentials and a durable inbox, without installing or requiring Mindwire. Only the optional assistant uses its agent runtime. Add separate account-link instructions and URL messages, localized replies following each user’s OpenShip language, and Telegram welcome, project and confirmation buttons. Share project command syntax between CLI and chat through @repo/commands; preserve verificações de permissão e rastreie mensagens de resposta individuais por meio de novas tentativas.

  • Assistente de aceitação

    Use Claude Code or Codex through Mindwire in the Assistant tab, with streaming conversations, structured questions, tool results, agent connections and private history. Inline permission review reuses the existing MCP consent form; operations use the normal MCP permissions, deployment flows and audit rules. Native tools are restricted, retries reuse request receipts, and changing access requires a new conversation. Disabled by default; available on macOS and Linux hosts. Cloud uses a private Mindwire profile on the chosen customer server; Desktop can reuse local sign-in, while self-hosted and Cloud keep separate agent credentials. Tenant checks, durable consent and renewable turn leases protect conversations across API replicas. Agents can request additional access in the conversation; users review it in the shared permission editor. Requests grant nothing, retain current permissions until saved, and never retry a task automatically. Remote assistant hosts tolerate slow startup and retain their private connection record so a retry can reconnect to the same daemon.

  • Liberar endurecimento

    Include the shared commands package in self-hosted source distributions, keep repository changes explicitly classified as source writes, report safe background failure summaries without logging native credentials, and refresh the generated API and MCP references. Update compatible dependencies for published security fixes while retaining the existing OAuth/MCP data model. Implicit OAuth account linking now requires a verified local account as well as a provider-verified email, preventing pre-registered account hijacking. Migrate authenticator confirmation and lockout fields while preserving existing active factors and unfinished enrollments, including older instance backups. Preserve failed authenticator and recovery-code counters across denied requests, so challenge attempt limits and account lockouts cannot be reset by transaction rollback. Include the assistant type dependency in the public SDK and catalog new audit events.

  • Correções de implantação

    Redact long clone tokens from stored errors and skip the workspace dependency crawl when checking changes for Compose projects (#1546, #1547).

1 de nov.2026v0.9.6RecursosSegurança34 atualizações

Atualização recomendada para recuperação de banco de dados, construções e migrações confiáveis, GitHub agendamento de ações e atualizações de infraestrutura gerenciada.

  • Recupere o PGlite após uma falha no contêiner

    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).

  • Mantenha Docker falhas de compilação legíveis

    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.

  • Mantenha as imagens de tempo de execução monorepo alinhadas com cada serviço

    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.

  • Adicionar uma base de manifesto com escopo 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).

  • Preservar registros ativos de 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).

  • Suporta login OIDC auto-hospedado verificado

    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).

  • Mantenha as sessões do BuildKit ativas

    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).

  • Mover imagens referenciadas por resumo entre servidores

    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).

  • Mova projetos de aplicativo único sem estado entre servidores

    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).

  • Manter GitHub trabalhos na fila em movimento

    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).

  • Mantenha os diagnósticos da nuvem disponíveis durante a inicialização da réplica

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

  • Recuperar a integridade após a substituição de um contêiner de serviço

    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).

  • Digitalize repositórios privados com credenciais de servidor

    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).

  • Combine sugestões de trabalhadores do Laravel com dependências de produção

    Suggest the standard queue worker when Horizon is only in require-dev, correspondendo ao Composer padrão --no-dev instalar. As opções de funções explícitas permanecem disponíveis (#1171).

  • Mantenha as funções de tempo de execução disponíveis após remover os serviços anexados

    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).

  • Evite falsos avisos de função obsoleta após implantações

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

  • OpenShip Ganhe

    Explain the Cloud affiliate program at /affiliates, com uma divisão de comissão interativa, cronograma de recompensa mensal e anual, orientação de pagamento e uma visualização social dedicada. Rotule a entrada de afiliado do painel Ganhe com um ícone de caixa de presente na barra lateral esquerda.

  • Inicie os serviços CockroachDB corretamente

    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).

  • Recuperar armazenamento de verificações lentas de cache de compilação

    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).

  • Recuperar imagens de primeiras implantações interrompidas

    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.

  • Programa de afiliados na nuvem

    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.

  • Revise as edições do ambiente compartilhado

    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.

  • Esclareça a verificação e os ganhos das referências

    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.

  • Restaurar serviços gerenciados após uma atualização de imagem interrompida

    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).

  • Validar nomes de recursos de permissão na inicialização

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

  • Carregue o ambiente de origem do aplicativo selecionado

    Use the app folder's openship.json quando presente e retornar à raiz do repositório, caso contrário, correspondendo à configuração mostrada durante a configuração (#1480).

  • Autenticar submódulos privados com o token GitHub selecionado

    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).

  • Preservar Docker tentativas de reinicialização e mapeamentos de portas

    Retain configured on-failure limites de novas tentativas e todas as vinculações publicadas durante a criação do contêiner.

  • Mantenha as rotas de borda utilizáveis antes da primeira implantação

    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).

  • Mantenha a identidade da origem de implantação intacta

    Expose the selected revision as OPENSHIP_COMMIT_SHA, reter resumos de imagens do Compose transportados e aplicar caminhos de implantação configurados de forma consistente (#1499, #1475, #1472).

  • Mostre o feedback correto do painel

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

  • Manter o escopo do aviso de atualização

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

  • Alinhe os preços da nuvem com os períodos de cobrança

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

  • Mantenha as compilações de versão para desktop disponíveis

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

24 de out.2026v0.9.5RecursosCorreçõesSegurança4 atualizações

Esse hotfix restaura a inicialização do Compose auto-hospedado após a atualização 0.9.4.

  • Restaure a prontidão do painel e a inicialização na borda

    Bind the dashboard's Next.js server to 0.0.0.0 dentro de seu contêiner para que a verificação de integridade do loopback possa alcançá-lo. Aplique a mesma configuração de vinculação nos ambientes do Compose gerados pela CLI, auto-hospedados de referência e de origem. As portas de host publicadas mantêm seus padrões de loopback existentes (#1461).

  • Teste a atualização completa do cliente

    Gate image publication on upgrades from 0.9.3 and the previous release using their published API, dashboard and edge images and CLI templates. Verify populated PostgreSQL and Redis storage, custom ports, preserved secrets, admin credentials and signed sessions, saved edge routing, dashboard-to-API access, cold restart and fresh installation. Probe both dashboard image architectures before publication; an API-only migration check no longer stands in for a stack upgrade.

  • Explicar os pré-requisitos de reconstrução de origem antes de uma atualização de segurança

    Global and project advisory views use the same runtime-update preflight as the deployment action. Replayed or revisionless source images show their prerequisite and an Reimplantação de código aberto ação em vez de oferecer uma atualização que falhará. A Reimplantação ainda usa os controles de implantação do projeto existentes; a origem da fonte, os pins de imagem e a autorização do locatário permanecem aplicados (#1462).

  • Incluir a correção da imagem do trabalhador empacotado

    Source builds of managed workers require Git checkout metadata. Bundled Dockerfiles in the released API no longer trigger a development worker build.

Recuperação de 0.9.4

Corre openship update após 0.9.5 ser publicado. A atualização recria a API, o painel e a borda por meio do pipeline normal e preserva o banco de dados existente, Redis e o armazenamento do aplicativo. Para uma recuperação temporária em 0.9.4, defina HOSTNAME: "0.0.0.0" no Compose do serviço de painel environment e correr docker compose up -d com o arquivo Compose existente e o nome do projeto dessa instalação. Uma execução CLI posterior regenera esse arquivo; atualize para 0.9.5 para a correção permanente.

24 de out.2026v0.9.4RecursosCorreçõesSegurançaBreaking80 atualizações

Esta versão adiciona implantação em Docker clusters Swarm existentes, replicação de banco de dados revisada, faturamento anual na nuvem, OpenShip gerenciamento de planos de suporte, avisos de segurança em tempo de execução, seleção explícita de aplicativos monorepo e proteção de senha de borda. Recuperação de implantação, armazenamento persistente, operações em nuvem e webmail recebem correções de confiabilidade e segurança. Estas notas cobrem mudanças desde 0.9.3.

Projetos, repositórios e ambiente

  • Escolha quais aplicativos monorepo implantar

    New imports ask for an explicit app selection instead of enabling every detected package or port. Add more apps, browse or enter repository folders, and retain saved selections, manually added roots, custom commands and private access when rescanning or reopening a project.

  • Mantenha grandes listas de domínios gerenciáveis

    The wizard groups routes by their owning app, shows a total and the first three rows, and offers View all. Apps using the same port keep separate domain ownership; changing deployment mode preserves the selected app's routes and privacy settings.

  • Crie serviços adicionais a partir do repositório

    Services and Topology share a From repository form with folder, build-context and Dockerfile selection. Save the service, then deploy it through the normal pipeline. Manual paths and retry remain available when browsing fails. Catalog selection gains compact source tabs, search and category filtering while retaining generated credentials.

  • Preservar a topologia do Compose durante a detecção

    A root Dockerfile alongside a Compose file retains the declared services and volumes even when framework detection also matches. Development-only Compose files beside ordinary framework projects remain opt-in; explicitly selected configuration retains precedence.

  • Ignorar pushs de espaço de trabalho não relacionados

    Single-app subfolder projects consider transitive workspace dependencies, shared build inputs and lockfiles before automatic deployment. The update banner uses the same decision. Configure autoDeployPaths.include e exclude para regras explícitas; a análise incerta mantém a implantação em vez de ignorar alterações silenciosamente.

  • Leia a revisão original solicitada de forma consistente

    Retries and explicit-commit deployments read Compose files and openship.json os padrões desse commit, em vez de misturar um checkout mais antigo com a configuração mais recente do branch.

  • Use uma visão de ambiente eficaz

    The Compose wizard and service editor resolve defaults and interpolation consistently while preserving the original templates and masked secrets. Save persists intentional service edits; existing projects also offer Cancel without writing changes. Revealed values and late lookup responses no longer restore an old value after saving.

  • Esclareça como salvar e aplicar alterações de ambiente

    Save and Apply & restart describe their separate effects. Runtime-only values appear in a compact disclosure, unchanged image defaults no longer produce recovery warnings, and Apply can resolve an owned live legacy service without a populated per-service deployment record. Missing containers lead to the existing deployment action.

  • Conclua GitHub conexões e clones privados

    Hosted App setup, installation selection and attempt polling use the owning Cloud connection consistently. Self-hosted App creation sends a valid manifest redirect URL. Authorized same-owner private submodules receive scoped, short-lived credentials without persisting tokens in clone URLs or Git configuration.

  • Mostrar onde as compilações realmente são executadas

    Remote Docker deployments no longer offer an unsupported local-image build or label a remote build as local. Genuine local bare builds and independent clone-location choices remain available.

Implantações, armazenamento e recuperação

  • Extrair imagens de trabalhadores gerenciados de instalações empacotadas

    Bundled workspace files no longer make a release installation look like a development checkout. Automatic source builds require Git checkout metadata; explicit administrator build contexts still work for source archives. Remote builds use the published protected worker matching the release.

  • Faça backup do armazenamento de aplicativos independentes

    Project backup policies now capture a single app's persistent volumes even when it has no service rows. Manual, scheduled and pre-deploy runs share the existing backup and restore flow, including integrity verification, confirmation and retention. App restore points remain distinct from deleted-service history (#1444).

  • Use comandos e funções de liberação com infraestrutura anexada

    Supported self-hosted/Desktop Docker projects can keep one primary source app on the normal release-command, worker and scheduler pipeline while preparing attached private image services first. Infrastructure health gates app activation; retries, cancellation and rollback preserve confirmed databases and volumes. General Compose, multiple source apps, Cloud and cluster targets retain their existing role/release-command restrictions.

  • Explicar configurações de funções não suportadas

    Refusals describe which saved release command or role must change instead of recommending the Docker runtime already in use. Eligible older projects without a persisted runtime mode can configure roles through the same runtime resolver as deployment.

  • Verifique as variáveis obrigatórias do Compose antes de compilar

    Validate the effective enabled service cohort before image builds, registry pulls or cutover. Errors list missing keys by service without exposing values; frozen rollback settings and explicit service scopes retain their existing precedence.

  • Tentar novamente uma versão Docker concluída

    Retry deployment can reuse a retained, ownership-verified image after activation fails. It preserves the source revision and destination, with no rebuild or replacement pull. Missing artifacts fail clearly; unsupported bare/static and source-bind attempts do not offer an image-only retry.

  • Atualizar imagens de tempo de execução deliberadamente

    The wizard exposes runtime versions, build images and production images. On-demand checks compare available image digests, and Refresh images & redeploy uses the normal readiness and rollback pipeline. Configured version tags, digest pins and deployment scope stay intact; unavailable comparisons remain unknown and pins never advance automatically.

  • Preservar o titular por meio de substituições qualificadas do Compose

    Supported self-hosted Docker deployments can prepare an overlapping candidate when saved limits, measured headroom, port provenance and storage compatibility permit it. The old service remains until routing and the successful release are committed. Other targets keep normal replacement order; concurrent writable storage needs an explicit opt-in for the exact mount.

  • Resolva a recuperação do roteamento interrompido antes de admitir uma nova tentativa

    A timed-out Compose recovery requests cancellation and waits for its in-flight route pass to finish before releasing deployment ownership. Uncertain recovery retains the containers needed for recovery instead of allowing a late route write to overwrite a newer deployment.

  • Mantenha os dados declarados de imagem nas reimplantações

    Self-hosted and Desktop-managed Docker replacements reuse stable project-owned volumes for image VOLUME declarações. O armazenamento legado é recuperado do contêiner de saída exato e verificado; a propriedade ausente ou conflitante interrompe a implantação em vez de anexar um órfão não relacionado ou começar com dados vazios. As montagens explícitas têm precedência e os volumes de propriedade retidos aparecem nas visualizações de exclusão.

  • Exigir persistência de trabalho para implantações simples

    Provision writable build, shared-data, process metadata and log directories through the deployment login. Persistence failures stop activation instead of silently leaving data inside a replaceable release directory. Hosts needing one-time permission setup receive actionable guidance.

  • Inicie um serviço com armazenamento vazio sem apagar seus dados antigos

    Writable named volumes offer Start with empty storage, with service-name confirmation and a preview of the new and retained volume names. The existing service deployment applies the change; failed admission can retry the same saved volume selection. Other mounts, backups and the previous volume remain available for recovery.

  • Adapte a retenção de artefatos à capacidade do disco

    Automatic retention can reclaim eligible older Docker release artifacts under measured storage pressure while protecting active releases, pins, shared references and ongoing work. Reclamation requires a verified rebuild or immutable-image recovery path. Managed idle-cache budgets scale with filesystem size; application containers and volumes are excluded from pressure cleanup.

  • Relatar falhas úteis de restauração

    When a Docker restore helper exits without delivering its diagnostic output, collect a bounded tail of its logs. Stalled or unavailable log reads cannot hide the original failure or indefinitely delay cancellation and helper cleanup. Restore ordering and the separate attach-input issue are unchanged.

  • Aplique atualizações do plano de controle do Compose de maneira confiável

    Explicit updates recreate API, dashboard and edge services even when an earlier image prefetch already changed the environment. Updates wait for application readiness and report failures; PostgreSQL and Redis are not targets of forced recreation.

  • Expor o controle de troca por serviço

    Opt into resources.swapDisabled para serviços Docker suportados com limite de memória positivo e contabilidade de troca verificada. A validação compartilhada preserva o limite necessário nas edições de configuração. Isso altera o serviço selecionado, sem alterar a troca em todo o host ou impor novos limites de construção.

  • Mantenha os tempos de implantação precisos

    Build measurements survive terminal outcome writes, service timings include image preparation, and measurements freeze before cleanup. Unknown durations remain unknown, skipped builds display 0s, e os serviços intocados não adquirem medidas inventadas.

Clusters, escalonamento e topologia

  • Implantar em um Swarm Docker existente

    Desktop and self-hosted controllers can inspect an existing Linux manager, connect its cluster, and deploy new application or Compose workloads through the shared deployment, routing, scaling and rollback flow. Nodes pull immutable image digests and use release-scoped secrets. Existing Swarm tasks and routing-mesh ports stay protected from standalone adoption and edge takeover. Moving a previously deployed project requires an explicit migration.

  • Revise o dimensionamento e a replicação do banco de dados

    Topology Scale reviews application changes before applying them. Self-hosted Kubernetes can manage PostgreSQL readers and authenticated Redis/Sentinel replication through the existing operators, with verified backups and explicit writer/reader connection changes. Reader removal checks dependent consumers; unsafe Redis reductions use a verified smaller copy that preserves the original until the connection switch is approved. Swarm application scaling remains supported; synchronized database replication requires Kubernetes and is separate from copying a database.

  • Veja os membros do banco de dados na visão geral

    Primary and replica cards show their observed roles, health, servers and replication links. Larger graphs can switch to a compact view; Redis Sentinel voters remain distinct from data replicas. Missing observations do not invent a primary or a running member.

  • Torne a configuração e recuperação do K3s mais claras

    Require cgroup v2 before installation, prefer This Server for the initial gateway/control roles, and correct private kubelet connectivity. Retries can migrate an unchanged Openship-owned legacy configuration and finish its required restart; edited or unverified configurations stop with bounded, credential-redacted diagnostics.

Domínios, entrada e certificados

  • Rotas auto-hospedadas protegidas por senha e visualizações nativas

    Configure a shared password at the OpenResty edge. Authenticated requests verify a signed browser cookie locally, without an API, database or Redis lookup per request. Public routes keep their existing path. Password changes and revocation invalidate sessions; protected responses disable caching.

  • Conclua o roteamento de serviço e HTTPS juntos

    Project and service domain saves share the existing routing preparation and certificate checks. First-route setup uses an inline progress viewer, retains explicit edge/DNS-01 consent, and refreshes canonical status after success or partial failure. A ready proxy no longer masks a failed or disconnected HTTPS check.

  • Publique domínios somente de redirecionamento sem uma porta de destino

    Compose www/apex redirects can reach the edge even when the domain has no upstream service port.

  • Deixe as cargas de trabalho sem rotas e independentes da borda

    Private deployments without hostname routes skip unnecessary edge takeover, challenge and vhost preparation. Fixed-port services retain their explicit bindings; automatic allocations still require verified inventory and durable port claims.

  • Abra o pgAdmin sem um domínio personalizado

    PostgreSQL + pgAdmin supports an explicit Port only option while PostgreSQL stays internal. New catalog services also generate required PostgreSQL, MySQL, MariaDB, MongoDB and Typesense credentials instead of leaving their bootstrap secrets empty.

  • Mantenha as imagens do catálogo disponíveis

    Convex uses its new official registry namespace with the existing version pin. The retired Mindwire Console/runtime template is hidden and disabled for new installs; existing project data stays unchanged.

  • Reutilizar certificados curinga pai válidos

    Immediate subdomains can inherit a validated parent wildcard certificate when an exact certificate is absent. Exact certificates retain precedence; read failures preserve the working route rather than initiating replacement issuance or copying private keys.

  • Substitua certificados manuais sem interromper o estado de renovação

    Remove only the selected hostname's obsolete Certbot renewal record after validation. Failed installation restores the prior certificate, key or archive links and renewal configuration before any reload; unrelated lineages remain intact.

  • Melhore a recuperação e o diagnóstico de roteamento

    Control-plane setup can reclaim its own quarantined dashboard port without taking another workload's claim. ACME 502/504 errors describe challenge forwarding and the temporary listener; safe Cloud routing errors retain their actionable cause instead of blaming a healthy server connection.

  • Mantenha o gerenciamento de túneis no menu de rotas

    Cloudflare Tunnel settings move into the existing context menu, retaining per-domain Access settings, retry and readiness behavior without a persistent management row on every card.

Nuvem, faturamento, monitoramento e ações

  • Gerencie a infraestrutura de propriedade do cliente na nuvem

    Openship Manage Basic costs $5/month per organization with email support; Priority costs $20/month with priority support. Both include two connected servers, plus $3/month per extra server. Paid Cloud includes the Basic allowance once per organization; Priority retains its support fee. Expiration ends management access after the paid period while applications and data remain on the customer's hosts. Self-hosted control planes remain free.

  • Escolha o faturamento mensal ou anual na nuvem

    Hobby, Starter, Pro and Scale cost $12, $24, $47 and $119 per month, or $120, $240, $468 and $1,188 billed annually. The purchase view defaults to Yearly when supported by the provider, shows the monthly equivalent and full annual charge, and retains an explicit Monthly switch. Custom resources use the selected interval through quote, checkout and plan changes. Existing subscriptions retain their saved prices and allowances.

  • Atualizar a capacidade básica da nuvem

    New Hobby purchases include 1 vCPU, 4 GB RAM, 50 GB storage and email support. New Scale offers allow 50 projects. These catalog changes do not rewrite existing paid contracts.

  • Simplifique a seleção do plano e a recuperação de pagamentos

    Cloud plans, Prepaid PAYG and Manage your server share the purchase view. Manage plans are also available directly when connecting a server. Pending purchases appear under Payments & invoices with a count, and Manage checkout keeps the server allowance and total beside the selected support plan.

  • Mantenha o faturamento e o acesso de gerenciamento coordenados

    Durable checkout intent and receipt validation protect purchase retries. Paid Cloud organizations receive their included management allowance once, and allowance changes coordinate with server connections. Increasing recurring charges after Cloud coverage ends requires explicit consent.

  • Recuperar conflitos de checkout pendentes

    Explain when a purchase must be completed or cancelled, and open the existing payment recovery dialog. Checkout limits, pending resource changes, verification failures and cancellation in progress receive specific guidance instead of a generic retry message.

  • Reconectar fluxos de uso da nuvem

    Interrupted read-only subscriptions recover from retryable disconnects with bounded backoff. Authentication failures, malformed data and stalled subscriptions still fail clearly; cancellation releases readers, requests and timers.

  • Recupere terminais Cloud órfãos com precisão

    Refresh expiring namespace credentials for dispatch and teardown, then recover only the marked commands belonging to the interrupted operation. Ownership is cleared only after confirmed process exit; live controllers and another installation's claims remain protected.

  • Reutilize as credenciais do provedor com escopo definido e mantenha as orientações de limitação

    Concurrent Cloud lookups share short-lived namespace tokens after ownership checks. Rejected token generations are invalidated without evicting newer credentials or replaying mutations. HTTP 429/503 and bounded Retry-After guidance survive the transport.

  • Explicar falhas de implantação relacionadas a recursos

    Supported OOM, heap-limit and storage evidence produces a saved diagnosis and Review capacity action for the affected Cloud space. The explanation survives reloads and compacted logs. Long builds receive optional advice rather than an invented capacity failure; upgrades and retries remain explicit.

  • Refletir incidentes de tempo de execução no status do projeto

    Known incidents on the active self-hosted workload show Action Required and link to Monitoring & Logs. Status clears after observed recovery; intentional stops, retired workloads and monitoring opt-outs do not create stale attention.

  • Calcular médias de resposta de solicitações

    Overview and CLI traffic metrics divide total request duration by total request count, with consistent millisecond conversion for Cloud and self-hosted data. Uneven traffic and live/archive refreshes no longer inflate the reported average. Edge collection is unchanged.

  • Preservar executores de ações ativos por meio de falhas temporárias de API

    Retry transient provider, GitHub and App-token renewal failures without cancelling the worker, releasing its capacity or silently falling back to broader user credentials. Persist supervisor completion before external cleanup and retain verified infrastructure errors when GitHub synchronization finishes.

  • Mesclar o histórico de ações de maneira confiável

    Local timestamps and Cloud date strings sort together without crashing the Actions page. Failed Cloud augmentation preserves the local run list. Service connection/unlink messages also reflect the existing automatic deployment attempt instead of asking users to trigger it twice.

  • Mantenha um espaço de trabalho pessoal ativo durante alterações de conta

    Deleting or leaving the selected team workspace restores the stored session owner's personal workspace instead of failing while clearing the active organization.

Segurança e credenciais

  • Corrigir o ambiente de teste DOM

    Dashboard and webmail tests use Happy DOM 21.0.4, which fixes the module import alias code-execution vulnerability (GHSA-834v-8h66-3h79).

  • Combine avisos de segurança em tempo de execução com cargas de trabalho implantadas

    Verify a public, signed advisory feed and match affected image digests or observed runtime versions. New runtime rules, deployment changes and Check again refresh bounded container observations; ordinary polling reuses one current observation per project. Findings appear in the existing global critical/update banner with a shared affected-app review; no project visit is needed. The banner reads cached, workspace-authorized evidence without probing containers. Missing evidence stays unknown. Initial notices cover Node.js/Bun Brotli fixes and PHP's October security guidance, including a separate manual configuration warning that an image update alone cannot clear.

  • Aplicar patches revisados por meio do pipeline de implantação

    Refresh images & redeploy can pull a replacement behind the same tag, or rebuild the deployed Git revision with refreshed base images. Automatic refresh is off by default and requires explicit consent, a signed affected/fixed digest pair, an eligible image service and unchanged configuration. It pins the approved replacement, uses the normal refresh and environment-resolution flow, preserves persistent volumes, and verifies the deployed result. Late environment changes stop an automatic update for review. Concurrent requests admit one automatic attempt; rollback clears the one-time approval. Explicit digest pins remain fixed.

  • Entregue avisos de segurança por meio dos canais de notificação existentes

    Verified, enabled channels receive matching alerts by default, with a per-channel opt-out and durable delivery deduplication. Feed checks share authentication-aware polling, conditional requests and backoff with release updates: five minutes when authenticated, one hour without authentication. Advisory metadata cannot supply executable commands.

  • Fixar tempos de execução corrigidos e ferramentas de compilação

    Use Node 22.23.4 and Bun 1.4.4 across the affected control-plane, website, webmail and worker image stages, with verified image digests. Desktop moves to supported Electron 44.9.2; Actions distributions use Go 1.26.9 and updated Git, archive, SSH/HTTP and telemetry dependencies.

  • Mantenha regressões de tempo de execução nas verificações de lançamento

    Exercise the upstream Brotli decoder rejection case, streaming input, private-CA HTTPS, hostname verification and authenticated asynchronous WebSockets. TLS SNI is sent only for DNS names, and package-manager bootstrapping works when node é um apelido para Bun.

  • Preservar a autoridade além dos limites do locatário e do terminal

    Service, server and proxied Cloud terminals retain the caller's credential restrictions and recheck expiry, revocation and current administrative access. SaaS-managed customer hosts use verified public destinations, SSH host-key pins and encrypted uploaded credentials; operator identities and private certificate-provider settings remain outside tenant-controlled host configuration.

  • Escopo de conexões de backup no momento do uso

    Cloud S3/SFTP destinations pass the shared public-network checks before connecting to the validated address. Server SSH identity and existing host-key pins remain enforced for SFTP; self-hosted private backup storage stays supported.

  • Conceda recursos de token mais restritos

    Personal access tokens and MCP clients can receive project-scoped domain read/write/delete and deployment read/trigger permissions. Minting checks the creator's authority, and cancellation, rollback and deployment deletion retain their administrative requirement.

  • Proteja compilações remotas Docker de destinos de metadados

    Rootful Linux SSH and Cloud builds use the project-owned BuildKit worker's IPv4/IPv6 metadata and credential-endpoint policy, including after restart. Missing required executor or policy support fails before repository commands; local Engine API, bare and Kubernetes builds remain outside this policy's scope.

  • Verifique a publicação do trabalhador antes de liberar pacotes dependentes

    Publish and anonymously verify the protected worker for both supported Linux architectures before dependent image and bundled-release publication. Release receipts must match the tag and source commit; missing or private images stop publication.

  • Mantenha os serviços de visualização desativados isolados

    Disabled service copies retain their disabled state while host bind mounts and external host/container namespace references are removed. Named/anonymous volumes and sibling service references stay usable; production configuration is unchanged.

  • Cotas de endpoint de webhook separadas por trás de endereços compartilhados

    Unrelated hooks no longer exhaust one another's source-IP bucket. Endpoint quotas share the existing limiter with a separate aggregate IP ceiling; authentication, signatures and credential redaction remain enforced.

Desktop, webmail, site e documentação

  • Crie Windows instaladores com ambientes de execução corrigidos

    Stage SSH and Docker dependencies from a package manifest so version ranges do not pass through Windows command shims. The packaged dependency load check remains required.

  • Restaurar inicialização offline visível da área de trabalho

    Embed the shared generated theme palette in the native loading page so its text and artwork remain visible before the dashboard loads.

  • Reparar mapeamentos de host de webmail gerenciados mais antigos

    Backfill the missing host-gateway alias for the explicitly linked webmail service on its own self-hosted mail server. The repair preserves credentials and volumes and takes effect through the next normal deployment.

  • Visualize anexos do Office com renderização limitada

    XLSX, DOCX and CSV files gain readable, sandboxed previews with limits on parsing and rendered content. Unsupported, encrypted, corrupt or truncated content retains a download option. Active HTML/SVG/XML and unknown attachment types download instead of executing in the signed-in webmail origin.

  • Atualize as dependências de correio e editor de forma consistente

    Align the patched editor dependency graph across direct and nested imports, update Nodemailer and Mailparser, and preserve reviewed runtime overrides in Docker and tarball packages. Existing SMTP modes and credential repair remain supported.

  • Mantenha intactas as visualizações sociais de páginas públicas

    Pricing, marketing, catalog, feature, blog, changelog and mail-guide pages inherit the shared Open Graph and Twitter images while retaining explicit page images and metadata. The release checks validate the rendered image tags and their image responses.

  • Mostrar GitHub estrelas na navegação do site

    Desktop and mobile navigation display the cached repository star count, with an accessible exact count and a fallback when GitHub is unavailable.

  • Melhorar a orientação operacional

    Document Docker socket permissions and reconnecting after group changes, update the shared API/SDK/CLI/MCP references, and explain the supported cluster, recovery and runtime-image workflows.

Notas de atualização

  • Rebuild or recreate the affected control-plane and webmail deployments to apply their runtime updates. Explicit project runtime versions and image digest pins are preserved

    Updating Openship alone does not update every deployed app.

  • As compilações SSH rootful protegidas Docker exigem Buildx e root ou sudo sem senha para a política de trabalho confiável e operações do sistema de arquivos de cache. Os limites explícitos comuns de CPU/RAM e o compartilhamento de recursos não configurados mantêm seu comportamento existente.
  • O suporte existente ao Swarm é para controladores desktop/auto-hospedados, com transferência stop-first e serviços persistentes de instância única no gerenciador conectado. Ele não adota pilhas existentes arbitrárias nem adiciona clustering em nuvem hospedado. A replicação gerenciada PostgreSQL/Redis requer operadores Kubernetes auto-hospedados.
17 de out.2026v0.9.3RecursosCorreções25 atualizações

Esta versão melhora o monitoramento da nuvem e a confiabilidade do cache de construção, adiciona automação de implantação e visualizações isoladas de pull-request e facilita a configuração, observação e recuperação de trabalhadores e agendadores. Estas notas cobrem todas as alterações mescladas desde 0.9.2.

Automação e visualizações de implantação

  • Mova variáveis de comando para Ambiente

    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.

  • Prepare a saída da estrutura automaticamente

    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.

  • Revise montagens manuais de cache mais antigas

    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.

  • Detecte problemas de configuração mais cedo

    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.

  • Ative GitHub visualizações de solicitação pull

    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.

  • Recuperar operações de ciclo de vida de visualização

    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.

  • Use a automação do SDK

    Configure and list previews, inspect or migrate manual cache mounts, and move command variables through the shared validated project operations.

Trabalhadores, agendadores e reversão

  • Configurar funções sem reconstruir o aplicativo 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.

  • Veja e inspecione processos em segundo plano

    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.

  • Mantenha sugestões de funções independentes

    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.

  • Recuperar transferências de funções interrompidas

    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.

  • Proteja imagens ativas e de reversão

    Retained role replicas keep their required image artifacts protected during configuration changes and release cleanup.

  • Restaure o ambiente congelado do Compose com precisão

    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.

Monitoramento de nuvem, caches e armazenamento

  • Evite varreduras de monitoramento caras

    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.

  • Mostrar uso de RAM de convidado

    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.

  • Mantenha as métricas parciais úteis

    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.

  • Mantenha o escopo da limpeza do cache da nuvem

    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.

  • Aceite sistemas de arquivos sem totais fixos de inodes

    Unsupported or zero inode totals mean unknown availability rather than confirmed exhaustion. Real free-space and supported inode-exhaustion checks still protect deployment admission.

Domínios e entrada

  • Rotear domínios personalizados verificados na primeira implantação

    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.

  • Evite portas de host secundárias efêmeras

    Secondary loopback publications use the existing allocator and the target host's ephemeral-range checks.

  • Lidar com diversos aplicativos de acesso 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.

  • Esclareça a disponibilidade da borda

    Documentation explains edge failure behavior and recovery responsibilities for deployed applications.

Webmail

  • Resolva IDs de mensagens exatos para ações

    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.

  • Armazene em cache os ativos do aplicativo corretamente

    Fingerprinted assets receive immutable caching while application HTML is revalidated.

  • Servir ativos pré-compactados

    Negotiate available Brotli or gzip files with appropriate content types, encoding and cache headers.

16 de out.2026v0.9.2RecursosSegurança39 atualizações

Este patch adiciona execução de trabalhador e agendador, personalização de aparência pessoal e configuração de túnel gerenciado Cloudflare para servidores auto-hospedados. Espaços na nuvem, caches de construção reutilizáveis, mais aplicativos de catálogo e limpeza de armazenamento mais segura melhoram as operações diárias. Estas notas cobrem todas as alterações mescladas desde 0.9.1.

Trabalhadores e agendadores

  • Execute funções ao lado do seu aplicativo da web

    Declare workers and schedulers in openship.json ou a API do projeto. As implantações de aplicativo único Docker iniciam contêineres separados da imagem do aplicativo, com ambiente compartilhado, volumes e redes conectadas, seus próprios comandos e configurações de desligamento, e nenhuma porta publicada. As funções seguem pausa, retomada, reinicialização, reversão e exclusão do projeto.

  • Entregue singletons com segurança

    Scheduler renames, command changes, name swaps and conversions into workers stop and retain outgoing singletons before starting potentially conflicting replacements. Failed deployments restore them only after those replacements are confirmed removed. Failed retirement of an old role is surfaced in the deployment warning with its container identity.

  • Exigir uma inicialização verificada

    Every replica needs exactly one stable result for its container ID before optional exec health checks run. Missing inspections, duplicate results and processes that already exited successfully fail startup. Both project-defined and image-inherited PORT os valores são removidos das funções.

  • Torne a configuração da função explícita

    Move and copy refuse active, unfinished or preserved-cancelled role workloads even after saved roles are cleared. Preset-only when e unless chaves em funções declaradas produzem avisos em vez de aparecerem silenciosamente para controlar a execução. A seleção automática de funções de estrutura e a migração de funções entre servidores não estão incluídas.

  • Melhorar os padrões de encerramento da estrutura

    Rails presets have measured stop settings, and Laravel's scheduler preset uses SIGTERM with a 10-second grace period while queue and Horizon workers retain 90 seconds. Customize these bounds for long-running tasks; they do not guarantee task completion or exactly-once scheduling. Laravel web-role cache warming is available as an opt-in setting.

Aparência e painel

  • Personalize sua própria aparência

    Settings → General → Customize previews color tokens and typography live, with explicit Save, Discard and Reset. Import themes from JSON, a file or an HTTPS URL; export themes and libraries, including supported WOFF2 fonts. Preferences belong to the signed-in user and stay isolated across accounts and instances. API, SDK, CLI and MCP operations use the same theme format.

  • Mantenha as ferramentas operacionais juntas

    Project monitoring and logs share one navigation entry with their own views. Backups moves under Infrastructure. Project sidebars show assigned domains, migration retries retain destination choices, and migrated service deployments use the correct icons.

  • Reduza alertas falsos de interrupção

    The health watcher confirms repeated bounded Docker probe failures before announcing a server outage. Late probe replies cannot falsely announce recovery. Self-hosted administrators can clear resolved monitoring history with confirmation while retaining open incidents.

  • Melhore a navegação e a confiabilidade do terminal

    GitHub discovery no longer blocks dashboard pages, selection controls use consistent states, and leaving a server terminal during WebGL loading cancels setup and disposes the terminal. Instance connection and move actions have clearer setup and recovery guidance.

Cloudflare Túnel e domínios

  • Gerenciar entrada auto-hospedada de OpenShip

    Server → Security can connect or create a remotely managed named Cloudflare Tunnel using saved credentials, configure proxied DNS and optionally apply an existing reusable Access policy. Install a pinned connector on a supported Linux server or use its existing connector. Managed Openship Cloud routing retains its existing path.

  • Registrar domínios com configuração recuperável

    Explicitly enable automatic tunnel enrollment for new custom domains or connect existing domains individually. Setup records Access, tunnel and DNS progress, supports retry after interrupted requests, and removes only owned resources. External edits remain visible for review instead of being overwritten. Exact hostnames and www companheiros são apoiados; o registro automático curinga não é.

  • Escolha o comportamento primário e www

    The deployment wizard defaults a newly included companion hostname to a 301 redirect to the entered primary. Choose bare primary, www primary or Serve both on Cloud and self-hosted destinations. Redirect rows show their target instead of duplicate runtime inputs.

  • Mantenha as operações de domínio consistentes

    Service aliases on the same port are preserved, domains added through the CLI receive routing, and Cloud routing retries recover missing Pages through the owning Cloud connection.

  • Honre proxies confiáveis em bordas conteinerizadas

    Operator-declared proxy IPs reach the edge without rebuilding its image. Invalid addresses and CIDR prefixes are discarded. Failed configuration updates restore the previous shared trust include, and an incomplete rollback cannot activate a partial configuration.

Espaços na nuvem, cobrança e conexões

  • Veja a capacidade gerenciada como espaços na nuvem

    A shared picker, Overview and Activity views show projects, purchased capacity and measured usage, with clear retry states for unavailable readings. Existing allocations and subscriptions keep their identity; connected self-hosted server tools remain available.

  • Use a conta do Cloud proprietária de forma consistente

    Connected Desktop and self-hosted installations create Cloud projects through Cloud's API. Server, project and deployment operations enforce their organization and provider namespace. Cloud consent shows the actual account and organization and lets you switch either before explicitly authorizing the connection.

  • Continue as compras sem repetir a seleção do plano

    Pricing links carry the chosen plan into the signed-in app's checkout flow. Pending unpaid payments can be cancelled when supported by the provider so another plan can be selected; retries retain the original payment identity. Server cancellation is easier to find and repeated requests cannot create duplicate operations.

  • Configurar ações em espaços existentes

    Cloud's Add runner flow opens the capability form directly with the space picker. Local Actions lists remain available when Cloud discovery fails, and official runner containers support non-root SSH supervisors. Temporary runner profiles retain their separate funding flow.

  • Mantenha a transferência da instância com sua origem

    Control-plane provisioning on a linked managed destination stays owned by the source controller until the move transfers the instance, including resumed API-only and dashboard installations.

Crie desempenho e controle de recursos

  • Mantenha os recursos não configurados ilimitados

    Omitted build and service CPU/RAM limits no longer become sampled capacity caps or catalog sizing recommendations. Containers share the selected server's capacity unless limits are explicitly configured. Cloud plans and VM capacity still apply. Existing saved limits are preserved; select Full capacity to remove an older unwanted limit.

  • Permitir envios simultâneos na nuvem

    Different projects can submit builds while a sibling build is active. Unspecified resource dimensions remain shared; explicit limits, saved plan concurrency and exclusive maintenance protection remain enforced.

  • Reutilizar caches de compilação de projetos limitados

    Compatible builds retain project-owned BuildKit state and supported package/compiler caches while temporary workers are removed. Idle cache collection uses retention targets and storage-pressure checks, preserving active workers, release images and application data.

  • Opcionalmente, aqueça novos espaços na nuvem

    Operators can select a provider software disk with public build-image layers for new spaces. Matching images are pinned against their current upstream digest; unavailable or outdated packs fall back to registry resolution. Existing spaces are not reattached by an API redeploy.

  • Mostre o que a preparação de imagem está fazendo

    Registry pulls stream progress, preparation heartbeats and elapsed time into deployment logs. Build cleanup waits for tracked Docker commands to acknowledge completion, and static export publication normalizes public file permissions.

Catálogo, GPUs e bancos de dados compartilhados

  • Adicione aplicativos de documentos, painel e mídia

    Install Paperless-ngx, Wiki.js, Homepage, Immich and Jellyfin using pinned published images, persistent storage and protected initial setup. Homepage does not require a Docker socket.

  • Execute aplicativos de IA auto-hospedados

    Ollama offers CPU or one NVIDIA GPU, and Open WebUI connects to an existing backend with protected chat access. These templates use connected self-hosted destinations, not managed Cloud capacity. vLLM remains a disabled preview pending hardware verification.

  • Implante serviços de GPU NVIDIA

    Compose import, SDK/CLI sync and adoption share validated GPU selection and Docker device requests. Server detection and picker hints help choose a compatible destination. Unsupported or conflicting requests fail before image acquisition or service replacement.

  • Ignore compilações desnecessárias de WordPress e Odoo

    New catalog installs pull the official images and mount setup helpers through the normal deployment engine. Existing installations retain their saved recipes; reviewed catalog repair can update the application service while preserving database siblings, credentials and data.

  • Compartilhe bancos de dados nativos explicitamente

    Use in a project can connect ready native PostgreSQL or Redis databases to authorized projects in the same cluster. Saved grants and private network rules are checked together; ownership, backups and database management stay with the source project.

Segurança de armazenamento, exclusão e migração

  • Separe dados recentes de aplicativos em nuvem

    New logical volume names use immutable project IDs so reinstalling a deleted slug cannot adopt another project's data. Owned legacy mounts and explicitly imported volume identities remain intact.

  • Recupere a exclusão com falha claramente

    Failed first installs offer the existing explicit data-removal option, including owned volumes with no container. Data retention stays the default. Cleanup failures remain retryable operations instead of making a partly deleted project appear Live again.

  • Preservar recursos pertencentes a outros projetos

    Teardown can retain stale Cloud route and network references whose foreign ownership is confirmed. Unreadable or ambiguous ownership still blocks cleanup, and owned networks are removed by immutable identity rather than a potentially reused name.

  • Evite colisões efêmeras de porta host

    Docker allocation checks the target kernel's ephemeral range for both saved preferred ports and fresh candidates. Unsafe legacy allocations move to a safe port during deployment; if no safe candidate exists, allocation fails before reserving a replacement.

Correio, segurança e localização

  • Persistir conectividade de back-end de webmail

    Webmail deployed on its mail server saves the host-gateway mapping through normal service settings and deployment snapshots while retaining the certificate hostname for TLS. Sign-in connection attempts have bounded timeouts rather than hanging indefinitely.

  • Conecte caixas de correio existentes da nuvem

    The Emails screen installs the standard webmail client for existing IMAP/SMTP servers. It does not provision or administer a self-hosted mail server in Cloud; managed email remains Coming soon.

  • Reparar operações de correio em contêineres

    Boot restores maildir ownership, backups and restores use the actual host-mounted mail path, and fail2ban uses valid nftables syntax and explicit private PostgreSQL sidecar credentials. Database and unban failures no longer report success.

  • Redimensione sua caixa de entrada e painel de leitura

    Drag the divider or use its keyboard controls. Desktop widths are remembered separately from the mobile layout.

  • Evite clickjacking no painel

    Dashboard pages, authentication routes and redirects deny framing through CSP and X-Frame-Options. Customer application routing and headers are unchanged.

  • Expandir orientação e documentação traduzidas

    Supported dashboard locales include preferences, transfer, jobs, issues, pricing, diagnostics and audit descriptions. The website adds a blog and broader feature discovery, alongside updated catalog, runtime-role, Cloud, API, SDK, CLI and MCP documentation.

Atualize a API, bem como os clientes de desktop/painel antes de usar as novas configurações, operações de túnel gerenciadas ou receitas de catálogo que exigem 0.9.2. As migrações de banco de dados incluídas são executadas durante a inicialização normal da API.

13 de out.2026v0.9.1RecursosCorreções16 atualizações

Este patch adiciona um catálogo de aplicativos públicos, suporte para painel russo e controles de imagem em tempo de execução. Ele corrige salvamentos de fluxo de trabalho e recuperação na nuvem, atualiza webmail ao vivo e melhora o roteamento, aumenta a capacidade e o tratamento de imagens durante as reimplantações. Estas notas cobrem todas as mudanças desde 0.9.0.

Configuração de aplicativos, idioma e fluxo de trabalho

  • Navegue pelos aplicativos antes de instalar

    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.

  • Suporte ao idioma russo

    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.

  • Salvar fluxos de trabalho de ações personalizados

    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.

Recuperação de nuvem e webmail

  • Continue as instalações de aplicativos e a seleção do plano após o login

    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.

  • Reconectar links salvos do servidor em nuvem

    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.

  • Recuperar um aplicativo de webmail existente

    When a mail registration loses its webmail link, select an accessible existing app on the same mail server and hostname and choose Reconectar e implantar. A recuperação reutiliza o projeto, as credenciais e os volumes persistentes, preservando a propriedade do domínio e as verificações de permissão.

Configuração de tempo de execução e segurança de implantação

  • Selecione versões de tempo de execução correspondentes e imagens de produção personalizadas

    Generated PHP builds support PHP 8.3 and 8.4 through the generic runtimeVersion configuração. Docker builds de origem oferecem um recurso avançado runtimeImage substituir. As receitas selecionadas pela pilha validam os recursos reais de tempo de execução e a compatibilidade antes da ativação; configurações inválidas não atualizam parcialmente o projeto e a reversão de imagem retida preserva a versão original e a configuração da imagem.

  • Recuperar Cloud Actions de instâncias conectadas

    Desktop and self-hosted clients forward Cloud workflow and runner operations to their owning Cloud instance, with the same scope and permission checks.

  • Use a capacidade de construção disponível real do servidor

    Automatic Cloud builds account for running workloads and pending CPU reservations before choosing their worker size. Build setup also reports the effective workspace capacity.

  • Verifique novamente a integridade da implantação

    Project status and workload selection reuse current startup-health verification while retaining earlier warnings for review.

  • Rastreie as imagens atuais do contêiner durante as reimplantações do Compose

    Cached Docker inventory preserves immutable image identity, so port preflight and rollback can verify running services safely.

  • Receba alterações na caixa de entrada ao vivo

    Webmail refreshes after IMAP IDLE events, with event streams flushed through buffering proxies and correct folder routing.

  • Simplifique a página de backup do projeto

    The existing project header supplies its title, removing the duplicated backup heading and description.

  • Validar funções de tempo de execução declaradas

    Stack-role configuration rejects missing kinds, empty commands, incomplete exec probes and invalid replica counts. This is configuration/detection support for future role execution.

  • Preservar domínios que roteiam apenas caminhos específicos

    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.

  • Atualize imagens de implantação antes de substituir serviços

    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.

12 de out.2026v0.9.0RecursosCorreções40 atualizações

OpenShip Actions leva o CI do repositório para seus próprios servidores Linux e macOS e executores de nuvem. Esta versão também permite mover seu plano de controle OpenShip entre o desktop e um servidor, adiciona GitHub verificações de implantação e notificações compartilhadas e melhora o agendamento, o roteamento, o monitoramento e o webmail da criação da nuvem. Estas notas cobrem todas as mudanças desde 0.8.2.

OpenShip Ações

  • Execute o CI independentemente de GitHub ações

    Workflows in .openship/workflows/ use YAML estilo GitHub e execute OpenShip nos destinos selecionados. Acione-os manualmente, em solicitações push ou pull de repositório, em agendamentos, por meio de envio autenticado ou em Jobs. GitHub pode fornecer verificações de origem, eventos e confirmação sem executar o próprio fluxo de trabalho.

  • Usar fluxos de trabalho GitHub existentes com OpenShip executores

    Workflows in .github/workflows/ mantenha a orquestração, os segredos, os ambientes e as verificações de GitHub. Registre corredores oficiais em OpenShip destinos e direcione seus rótulos auto-hospedados. Jobs direcionados a rótulos hospedados em GitHub ainda são executados em GitHub. importar um fluxo de trabalho não altera silenciosamente sua plataforma de execução.

  • Um editor de fluxo de trabalho

    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.

  • Fluxos de trabalho reutilizáveis e trabalhos avançados

    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.

  • Escolha os corredores por capacidades verificadas

    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.

  • Revise o acesso antes da execução

    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.

  • Siga corridas sem perder seu lugar

    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.

  • Artefatos, caches e OIDC

    Independent workflows support artifact/cache actions through scoped storage access and configured backup destinations. Jobs with id-token: write pode solicitar tokens OIDC de curta duração OpenShip de uma instância HTTPS. Os provedores de identidade devem confiar explicitamente no emissor OpenShip. estes não são tokens emitidos por GitHub. As chaves de assinatura viajam com movimentos de instância.

  • Conheça os limites

    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.

Destinos e financiamento do Cloud Actions

  • Reutilize um servidor ou adicione um

    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.

  • Corredores temporários por trabalho

    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.

  • Financiamento e recuperação

    $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.

  • Configuração do operador de nuvem

    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 Verificações e notificações

  • Verificações de implantação habilitadas por padrão

    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.

  • A configuração de verificações mostra o acesso real

    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.

  • Adicionar canais de notificação inline

    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.

  • Um editor de notificação

    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.

Conexões de desktop e movimentações de instância

  • Mover o controle para um servidor

    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.

  • Volte usando os dados mais recentes

    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.

  • Conecte-se sem mover dados

    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.

  • Convites abertos no desktop

    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.

Servidores em nuvem gerenciados, construções e hospedagem

  • Gerencie o acesso ao servidor em um só lugar

    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.

  • Admissão de construção durável

    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.

  • Subsídios do plano salvos

    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.

  • Recupere compilações interrompidas com segurança

    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.

  • Sites estáticos são padronizados para Cloud Pages

    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.

  • Inicialização de aplicativos mais confiável

    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.

  • Gerenciadores de pacotes consistentes

    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.

Correções de implantação, roteamento e monitoramento

  • Escolha outra porta explicitamente

    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.

  • Mantenha o estado do roteamento consistente

    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.

  • Verifique o Cloud HTTPS na borda de serviço

    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.

  • Distinguir perda de conexão de falhas de solicitação

    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.

  • Resultados de implantação no Monitoring

    Projects show completed outcomes and failed deployments alongside application monitoring. Project cards, grids and backup history use more consistent spacing and responsive layouts.

  • Correção de compilação e tempo de execução

    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.

Diagnóstico, CLI, SDK e webmail

  • Relatório de erros estruturado

    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.

  • Cobertura de automação mais ampla

    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 /api caminhos e pares de ambientes posicionais e orienta os usuários a fazer login em caso de falhas de autorização. As ações estão disponíveis através openship api; esta versão não apresenta um dedicado openship actions grupo de comando.

  • Documentação atualizada

    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.

  • Melhorias no webmail

    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.

  • Correções de compatibilidade adicionais

    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.

  • Verificação de liberação

    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.

Atualizando

Os usuários do Desktop 0.8.2 podem usar o atualizador integrado. Os usuários de desktop ainda na versão 0.8.0 ou 0.8.1 devem baixar o Instalador 0.9.0 e instale-o manualmente uma vez. Saia de OpenShip e substitua o aplicativo; mantenha os dados do aplicativo para preservar projetos, servidores e configurações. O caminho de atualização do servidor/CLI não requer esta etapa de recuperação da área de trabalho. Atualize a API e o painel juntos; as movimentações de instância exigem versões compatíveis em ambas as extremidades.

6 de out.2026v0.8.2RecursosCorreções3 atualizações

Recuperação de atualização de desktop

  • Foram corrigidos os redirecionamentos de lançamento de GitHub no atualizador de desktop, mantendo hosts de download confiáveis, verificações SHA-256 e verificação de assinatura do editor.
  • Adicionado um teste de download Electron real ao CI existente e porta de teste de liberação, cobrindo redirecionamentos de instalador e de prova, destinos bloqueados, loops de redirecionamento, cancelamento e limpeza de download incompleto.
  • Este bug de redirecionamento afeta o atualizador do instalador de desktop. O caminho de atualização do servidor/CLI é separado e não precisa desta etapa de recuperação manual.

Usuários de desktop em 0.8.0 ou 0.8.1: instale esta atualização manualmente uma vez. O atualizador integrado nessas versões pode falhar com "Redirecionamento foi cancelado". Baixe o instalador para o seu sistema operacional no site Versão 0.8.2, saia de OpenShip e substitua o aplicativo instalado. Mantenha os dados do seu aplicativo: seus projetos, servidores e configurações locais são preservados. As atualizações subsequentes da área de trabalho usam o downloader fixo.

6 de out.2026v0.8.1RecursosCorreçõesSegurança50 atualizações

OpenShip Cloud agora executa projetos em servidores gerenciados com planos mensais próprios. Compartilhe um servidor entre aplicativos, adicione outro quando precisar e gerencie seus recursos de nuvem junto com projetos locais no desktop ou auto-hospedado OpenShip. Esta versão também adiciona chaves de acesso, autenticador 2FA e uma caixa de entrada de suporte privada, expande a automação CLI e melhora o faturamento, a migração e a recuperação de implantação.

Servidores em nuvem gerenciados

  • Um servidor, vários projetos

    Each managed server has its own subscription and shared CPU, RAM and disk. Builds, applications, Compose stacks and catalog services use the existing Docker and Bare deployment engines. Creating a project no longer allocates a separate VM or reserves another disk (#1036).

  • Escolha Docker ou Execução direta

    Use Docker for containers and Compose, or run compatible source applications as supervised host processes with Direct. The shared destination picker can select an existing server or start a purchase for another. New eligible source apps default to Direct below 2 GiB RAM; saved projects and explicit runtime choices are preserved (#1064).

  • Use a capacidade que você comprou

    A service can use the server's full available CPU and RAM, or use a custom container limit. Fractional CPU settings, including Micro, reach Docker correctly. Source builds use available server headroom and optional build caps; image-only installs do not start a source builder. Applications, builds and the operating system still share the host.

  • Inspecione o uso separadamente da capacidade

    Server monitoring distinguishes the purchased disk size from measured usage. Project containers and volumes have a disk breakdown, with shared images, build cache and system data shown separately. Missing readings stay unknown, and undeployed drafts no longer inflate running-service counts (#1011).

  • Gerencie o servidor quando precisar

    Reuse server diagnostics, terminals, listening-port checks and resource views. Networking controls outbound internet access; the Activity tab holds provisioning and resize logs. Scheduled command jobs can target shared or separately subscribed managed servers.

  • Recuperar operações sem perder projetos vizinhos

    Provisioning, resize and interrupted deployment work retain progress for retry. Resizing restores previously running services while leaving intentionally stopped ones stopped. Project deletion removes its own resources and preserves the shared server; server deletion checks remaining projects and subscription state.

Contas na nuvem em computadores e auto-hospedadas OpenShip

  • Seus recursos existentes na nuvem aparecem quando você se conecta

    Cloud projects, apps and managed servers join the local inventory. A server already linked to the installation appears once. Cloud-owned settings, deployment history and operations stay in Cloud rather than becoming local project copies (#1074).

  • Compre e use servidores gerenciados no mesmo painel

    Cloud subscriptions and provisioning remain in Cloud. Local projects can select an authorized managed server through the same destination picker as SSH servers, using an execution link for deployment, logs, terminals, jobs and backups.

  • As trocas de conta limpam o estado da conta anterior

    Inventories, project details, deployment history and billing responses follow the selected Cloud account and organization. Connections are revalidated for live operations; locally scoped automation credentials do not inherit the owner's Cloud account.

Faturamento e planos

  • Servidores mensais incluem o período pago integralmente

    New monthly plans cover purchased CPU, RAM and storage without a second compute-credit allowance or a monthly build-time cap. New offers have no project or running-service count limit; workloads share the server's physical capacity. Optional managed proxy transfer and storage retained after coverage ends remain separate charges.

  • Planos revisados e recursos personalizados

    Hobby is $5/month for 1 vCPU, 4 GiB RAM and 25 GiB disk; Starter is $20 for 2 vCPU, 8 GiB and 32 GiB; Pro is $39 for 4 vCPU, 16 GiB and 128 GiB; Scale is $99 for 8 vCPU, 32 GiB and 256 GiB. Custom lets you choose CPU, RAM and disk and review a quote before checkout.

  • A cobrança segue o servidor selecionado

    Switch servers without losing the page, inspect each subscription independently, or use Obter servidor para uma nova compra. Os clientes iniciantes veem planos em vez de telas de uso vazias. Comparações de atualizações menores mantêm cartões compactos e um resumo do plano atual separado; métodos de pagamento e faturas compartilham o portal Stripe do servidor.

  • Revise as alterações no plano antes de aplicá-las

    Show the provider's prorated amount, effective date and affected projects. Capacity upgrades apply after confirmed payment; resource reductions and billing-mode changes wait until renewal. Pending changes remain visible, and a resize requires restart consent. Disks can grow but cannot shrink in place.

  • Checkout tem um caminho de recuperação visível

    Payment confirmation, paid coverage and server readiness are separate steps. Setup failures expose progress and retry without asking for another purchase; the welcome dialog appears when setup completes. Unavailable offers show a dedicated dialog with retry and a support request for availability updates (#1062).

  • Retomar ou cancelar pagamentos inacabados

    Pagamentos pendentes lista a oferta salva de cada servidor e abre seu checkout original. O cancelamento confirmado pelo provedor permite que você escolha outro plano ou exclua um servidor não utilizado e não pago. As instalações conectadas e na nuvem compartilham o fluxo de recuperação, e a troca de contas descarta os detalhes e respostas de pagamento da conta anterior (#1067).

  • Visualizar níveis PAYG pré-pagos

    Compare three shared resource-pool tiers, configure server resources and select a credit package in one calculator. The estimate separates active vCPU-hours, reserved RAM and storage, with hourly costs and balance-duration scenarios. Enterprise contact is available in both purchase views. PAYG purchases remain disabled in this release (#1057).

Segurança da conta e GitHub

  • Chaves de acesso e autenticador 2FA

    Settings → Security supports passkey registration and removal, authenticator QR setup, and single-use recovery codes. Enabled 2FA also applies after social and passkey sign-in. These controls are available on Cloud and self-hosted installations with local accounts (#984).

  • A proteção da conta permanece consistente durante falhas

    Credential changes commit together, concurrent requests cannot reuse a challenge or recovery code, and password resets do not disable 2FA. OAuth, invitation and MCP handoffs resume after verification. Security setup state clears when the account changes.

  • O acesso ao repositório GitHub é independente do login

    One GitHub identity can authorize repositories for multiple Openship accounts without transferring login ownership. Reconnect existing installations from the shared connection flow, including direct installation links, and see completion or failure for each attempt (#992).

  • Os tokens pessoais funcionam em todo o fluxo do repositório

    Git settings remain reachable through the alternative connection option. A verified token can supply repository and owner listings and private-source access when no GitHub App connection is available. Account avatars and Git URL entry are clearer.

Suporte e integração

  • Uma caixa de entrada de suporte privada na nuvem

    Submit deployment, billing, account or general tickets, search your history, reply and resolve or reopen a conversation. The same personal ticket history is available from Cloud-connected desktop and self-hosted installations. Team membership does not expose another user's tickets (#1073).

  • As páginas de suporte e contato aceitam solicitações duradouras

    Submissions are saved before email delivery, with a receipt and notification to [email protected]. As novas tentativas de entrega sobrevivem às reinicializações da API, e as respostas do suporte aparecem na caixa de entrada e são enviadas por e-mail ao cliente. Os envios repetidos reutilizam o recibo original em vez de criar outro ticket (#970).

  • Telas de primeira execução e de conta mais claras

    Refreshed Cloud plan prompts, purchase welcome dialogs, email-verification and password-reset completion screens. The home page omits empty system-status cards for new Cloud accounts, and already subscribed users do not keep seeing the first-purchase promotion.

Aplicativos e migração

  • Os aplicativos têm seu próprio lugar

    A dedicated Apps sidebar entry and list keep catalog applications separate from source projects. Compact home rows, restored empty states and clickable app illustrations make discovery less cluttered.

  • Um assistente de implantação mais consistente

    Share destination and server controls across Cloud and self-hosted modes, with Full/Custom power choices, filled inputs, compact Build/Start settings, readable deployment-step icons and clearer draft project details. App install forms support grouped and two-column layouts.

  • A instalação do aplicativo explica as opções de roteamento e recursos

    Public dashboards start with domain routing and ask for confirmation before continuing without a recommended domain. Self-hosted app CPU/RAM recommendations are advisory; failed Cloud installs can be retried or cleaned up without treating an absent runtime as a teardown failure (#1009, #1016).

  • Importe Docker aplicativos para servidores de nuvem gerenciados

    Reuse the existing migration engine for images, environment, volumes, bind data and routes. Cloud can connect an external SSH server as a migration-only source. Target preparation, saved progress, verification and explicit cutover support recovery; source data is preserved and source-container retirement requires consent.

  • Revise as importações como cartões ou topologia

    Compact expandable service cards are the default, with a topology view, expand-all controls, repository linking and clearer Custom, Free and Internal-only routing choices.

Construções, implantações e recuperação

  • Parar cancela o construtor selecionado

    Cancellation reaches the worker's actual Docker or Bare runtime, including remote Git and archive preparation. The UI shows Parando… até que a limpeza termine e permita a redistribuição. O cancelamento de um build preserva os contêineres implantados que herdaram rótulos de build; a propriedade ambígua do serviço ainda bloqueia a ativação (#1059).

  • A saída da compilação permanece legível

    Cloud Docker streams preserve raw bytes, partial lines, UTF-8 characters and terminal progress updates. Uploads finish correctly when stdin closes. Disk and inode exhaustion are explained separately from memory failures, and temporary BuildKit cache is reclaimed after builds (#1058, #1064).

  • Os serviços Compose inalterados permanecem em execução

    Folder uploads and snapshot syncs no longer mark unchanged image services dirty. Import metadata preserves concurrent configuration edits; inherited project resource changes still apply while respecting per-service overrides (#989).

  • Os backups pré-implantação terminam antes da ativação

    Deployments wait for all configured pre-deploy backups and their cleanup, including when reusing a build. Failed backups offer retry, an explicit skip or stop. PostgreSQL dumps must succeed, and suspiciously small dumps are rejected against recent comparable backups before becoming restore points (#1060).

  • Compilações remotas e versões estáticas usam os caminhos corretos

    Subfolder refreshes preserve root manifests and rescan at the project root. Static output resolves relative to that root, and retained artifacts are checked on their deployment destination for rollback. Directory-only .dockerignore negações são honradas (#1010, #1041).

  • As verificações de integridade e o desligamento respeitam o tempo de execução

    Configured single-app readiness probes run through the deployment server; unreachable SSH leaves a check unverified. Docker replacement honors stop signals and grace periods, probe watchdogs are reaped, and Bare services retain the correct user privileges and artifact ownership (#1043).

  • Detecção Farm.js

    Identify Farm.js applications and supply the framework's build and output defaults (#1037).

Domínios, redes e monitoramento

  • Domínios gratuitos seguem o servidor gerenciado selecionado

    Availability and quota checks retain the destination through project creation, Compose synchronization and deployment. Route changes are validated before related settings are saved; editing an existing route at the limit does not count it as a new route (#1064).

  • Conecte Cloudflare da configuração do domínio

    Add and verify a DNS credential without leaving the DNS panel, review proposed records, then apply them. Cloudflare TXT quoting and Cloud certificate-status handling are corrected, while certificate checks verify the domain's project binding (#977).

  • HTTPS curinga mais confiável e recuperação de Edge

    DNS challenge hooks pass Certbot validation, Compose installations detect Edge correctly, and challenge route cleanup checks ownership. Whole-project rules handle a null path prefix correctly. Projects no longer have the unrelated 20-public-endpoint schema cap (#1054, #1003, #1017, #1045).

  • As atualizações de origem permanecem visíveis até a implantação ser concluída

    The project deployment tab indicates available updates; unchanged image services are not refreshed unnecessarily. Updates on the local Openship instance use the appropriate advisory flow, and resource reporting accepts current Docker runtime limits (#1006, #1047).

  • Correções de conexão e configuração

    Recover Cloud Docker connections after credential rotation, report missing proxy/bridge failures clearly, correct registry TLS/WebSocket dependency compatibility, and handle Docker networks without subnets during cluster setup (#970, #1068, #961).

SDK, CLI e correções de plataforma

  • Mais administração por meio do Ship SDK e da CLI

    Add commands for project resources, environments, storage and connections; credentials and DNS; monitoring, notifications and webhooks; workspace access and audit history. They use the shared platform operations and permission checks.

  • Direcionamento de comandos e edições de ambiente mais seguros

    Each CLI invocation keeps its selected endpoint, credential and organization. Directory links reject mismatched contexts. Partial service environment edits preserve other values and secret classification; full replacement is explicit. Deployment waits have deadlines and expose pending decisions, and request logs can be followed through the SDK's authorized Cloud stream.

  • Fluxos de trabalho mais claros do MCP Cloud

    Discover authorized managed destinations and deploy desktop folders through a connected server. Explicit promotion to Cloud can resume from its saved receipt after an interrupted response or cleanup, without importing the project again (#1056).

  • Correções de webmail e painel

    Spam, Not spam and Archive move messages into the correct IMAP folders. Notification settings and icons recover from hydration races, Teams accepts current Microsoft webhook hosts, member-access settings avoid repeated refetches, and background project deletion preserves navigation (#981, #1004, #1008, #1035, #1024, #1066).

  • Inicialização da API e validação de ação em massa

    Capacity previews pass the startup permission scan, and malformed bulk container requests are rejected instead of being interpreted as an empty request (#1033, #994).

  • Análise opcional de produtos em nuvem

    The hosted Cloud API can send configured PostHog events for signup, deployment and verified checkout/payment outcomes. Delivery is queued separately from those operations. Telemetry runs only on the hosted Cloud API; local operations, logs, secrets and session recordings are excluded.

Transferência de dados e notas de atualização

  • Exportações completas e portáteis

    Instance and project archives include plaintext environment values, server keys and credentials by default, without an export password. Treat the archive as sensitive or explicitly omit secrets. Imports still accept older encrypted archives and encrypt credentials with the destination's key.

  • As importações preservam o escopo e os dados selecionados

    Instance imports default to full replacement after confirmation. Project overwrite removes destination-only records in selected categories and applies cleared credentials atomically. Project analytics retain normalized hostnames, including www; campos de arquivo não suportados são rejeitados antes da alteração dos dados.

  • Atualize a nuvem antes dos clientes conectados

    New inventory and support features require the matching Cloud API. Desktop-initiated cancellation fixes require an updated desktop controller. Existing per-project Cloud deployments need an explicit migration to managed servers; updating alone does not consolidate VMs or replace saved subscription terms.

  • Mantenha a configuração de segurança da conta estável

    Self-hosted passkeys require HTTPS and a stable dashboard hostname through OPENSHIP_PUBLIC_URL (localhost é suportado para desenvolvimento). Reter e fazer backup BETTER_AUTH_SECRET, que protege segredos do autenticador e códigos de recuperação.

27 de set.2026v0.8.0RecursosCorreçõesSegurança62 atualizações

Dimensione aplicativos PostgreSQL e Redis em seus próprios servidores, conecte esses servidores por meio de rede privada e compartilhe arquivos entre instâncias de aplicativos. Esta versão também adiciona o SDK Node.js, expande a automação do MCP, atualiza o painel e a experiência do desktop e traz a implantação, o ambiente, o roteamento, o backup, o e-mail e as correções de segurança acumuladas desde a versão 0.7.2.

Clusters de servidores e redes privadas

  • Conecte servidores entre provedores

    Register and verify an existing private network or prepare an Openship-managed WireGuard network across your servers. Provider network groups retain their provider and network details; managed networking also supports custom infrastructure (#899, #900).

  • Redes e clusters de computação têm responsabilidades separadas

    The Networking tab owns addresses, connectivity and network operations. The Clusters tab groups selected servers from a private network and manages the runtime used by their projects.

  • Escolha quais servidores podem se comunicar

    Edit connections in the network topology, allow traffic in both directions or one direction, or remove a connection. Openship enforces the private-access policy on supported hosts and shows the provider firewall rules to apply before setup. Cluster setup checks that its selected servers have the bidirectional connectivity it requires.

  • Teste a rede a partir da topologia

    On-demand checks verify allowed paths and confirm that denied directions reject new connections. Results include TCP/UDP reachability, MTU, round-trip latency, loss and jitter; a selected pair can run a bounded throughput test. Saved results remain available for diagnosis.

  • Preparar, revisar, tentar novamente e limpar alterações de rede

    Missing prerequisites can be installed automatically, address allocation and firewall requirements are reviewed before apply, and reconnectable progress includes per-server steps and errors. Interrupted work exposes explicit retry or rollback. Failed members can be removed from setup, and removal reverts owned network changes.

  • Preparar servidores para dimensionamento de aplicativos

    Self-hosted and desktop controllers install k3s under the hood, join the selected SSH servers, and verify node readiness, pod traffic, service routing and internal DNS. Saved progress supports retry after failure or interruption; runtime removal checks dependent workloads and owned infrastructure first (#912).

Dimensionamento de aplicativos

  • Execute um aplicativo ou trabalhador em seus servidores

    Select a prepared cluster, publish the application's image to a shared registry, and deploy through the normal project flow. Set 1–100 replicas; subsequent replica changes reuse the active immutable image without rebuilding. Openship Edge routes public requests to the application, and the topology shows observed instances, placement and readiness.

  • Atualizar, reverter e recuperar aplicativos em execução

    Cluster deployments retain image history for rollback, and failed or cancelled candidate releases preserve the active release. Kubernetes replaces failed instances within the prepared cluster and routes to surviving ready instances after detecting an unavailable worker. Revision checks reject stale changes to a running project.

  • Monte arquivos compartilhados em instâncias de aplicativos

    Project-owned shared volumes can be attached at configured paths, including read-only mounts. Instances on different servers can read and write the same files; existing node-local mounts require a separate data migration.

Bancos de dados e armazenamento compartilhado

  • Escolha autônomo ou clusterizado PostgreSQL

    Managed databases have their own resources, progress, credentials and lifecycle. PostgreSQL clusters provide replicas, primary recovery, and private read/write and read-only endpoints. The database controller owns replication and failover independently of the application's replica count.

  • Execute Redis de forma independente ou como um cluster

    Redis clusters distribute data across shards with replicas. Grow or reduce the shard count after reviewing the change and taking a verified recent backup. Redis Cluster requires a cluster-aware client; resizing checks real cluster health and slot ownership.

  • Faça backup e recupere PostgreSQL e Redis

    Configure an eligible S3 destination for manual, hourly or daily backups. Restore a verified archive into a separate database, inspect it, then explicitly replace the application's saved connection and redeploy. Redis archives preserve values and expiry and are consistent per shard, rather than one transaction across all shards.

  • Importe bancos de dados existentes e prepare PostgreSQL upgrades

    Import eligible Docker PostgreSQL or Redis backups while the original application remains on Docker. PostgreSQL 17-to-18 upgrades create a separate logical copy for checking before connection replacement. Source data remains available; changes after the captured recovery point need a fresh capture before final cutover.

  • Compartilhe arquivos com cópias de disco independentes

    Enable shared storage on at least two independent servers, choose two or three copies, and create project-owned volumes. Inspect attachment and copy health, grow a mounted volume, and rebuild a lost disk copy.

  • Recuperar arquivos de fora do cluster

    Take manual or scheduled external backups and restore them into a new shared volume. Archives remain discoverable after deleting the original volume or removing empty shared storage; archive deletion is an explicit separate action.

  • Manter os dados ao remover um banco de dados

    Removal can retain its data for later recovery or explicitly delete it. Application, volume, storage and runtime cleanup enforce dependencies and ownership, so an unfinished cleanup or retained database cannot silently lose the infrastructure it still needs.

SDK, CLI e MCP

  • Um Node.js SDK junto com a CLI

    O openship pacote agora fornece OpenshipClient através openship/client para instalações remotas e createShip através openship/native para um mecanismo incorporado sem um servidor API separado. Ambos usam operações, validação e autorização de plataforma compartilhada. As instâncias nativas têm ciclos de vida de início/fechamento explícitos e escopos de espaço de trabalho verificados; ESM e CommonJS são suportados em Node.js 22 e mais recentes (#887).

  • O MCP cobre mais o ciclo de vida operacional

    Networking, cluster setup, replica scaling, managed databases, shared files, backup/restore, migration, routing and diagnostics have documented tools and ordered workflow prompts. Discovery respects workspace permissions and instance mode; required arguments and DELETE bodies survive dispatch, and path arguments cannot redirect a call to another route. Generated API, CLI and MCP references describe the available operations and explicitly excluded HTTP-only routes (#953).

  • Os fluxos de trabalho da CLI usam o SDK compartilhado

    Native mode and remote clients share deployment and source handling, and Jobs now has commands for its existing management and execution flows. Re-login preserves custom context endpoints, folder uploads require explicit opt-in, project display names can be changed safely, and failed component installation returns a failure to the caller.

Implantações e compilações

  • Execute comandos de liberação antes da ativação

    Configure releaseCommands nas configurações de compilação, openship.json ou a API/SDK do projeto. Os comandos são executados em ordem após a construção, usando o ambiente da versão candidata, com logs transmitidos e um orçamento de dez minutos por comando. Falha, tempo limite ou cancelamento interrompem a ativação. As implantações de aplicativo único Docker e Bare são suportadas; tipos de implantação não suportados rejeitam comandos configurados. As reversões os ignoram e a reversão do código do aplicativo não desfaz as alterações do banco de dados (#592).

  • A conclusão e o tempo decorrido sobrevivem às novas tentativas e atualização

    Workers retry a failed database completion acknowledgement without repeating deployment work. Cancellation records its outcome and duration atomically; late worker results cannot replace them. Both build views use the same persisted timing, including queued starts, rejected retries and terminal events (#940).

  • A retenção de reversão tem um limite previsível

    Project → Advanced → Rollback history defaults to five past deployments, with active and pinned deployments kept in addition. Cleanup runs after deployment and retention changes, retries failed removals, and preserves artifacts still referenced by another retained release. Older history remains browsable with pagination and accurate snapshot labels.

  • Compilações de fontes mais confiáveis

    Recursive Git submodules are fetched for build checkouts; Ruby builds respect declared versions and preserve Rails storage; PHP builds include EXIF and package assets needed by frontend builds. JavaScript PORT atribuições são detectadas, a criação inválida de monorepo vazio é rejeitada e as falhas de DNS do serviço em tempo de construção recebem uma explicação acionável.

  • Erros de implantação atingem a IU

    Rejected submissions show the API's specific validation or configuration error. Build streams reconnect without replaying output, and successful deployments can show live service logs. Preview variable sets cannot be deployed onto a production project's runtime.

Ambiente e Composição

  • Variáveis de serviço salvas permanecem visíveis

    The Environment tab reads effective values from Openship, including Compose values, shared project variables and explicit service overrides, with their sources. It remains usable when the server is offline. Saves update only edited rows, preserve untouched secrets, reject conflicting edits and remove an override by restoring inheritance where available (#926).

  • As atualizações do Compose são aplicadas sem portões de aprovação de rotina

    Repository changes merge automatically while explicit operator overrides remain. Saved environment values survive omitted source keys, unresolved expressions and legacy review resolution. Interpolation uses current configured values instead of stale scan results; legacy pending reviews reconcile on redeploy (#893, #916).

  • Recuperar e aplicar alterações ambientais deliberadamente

    Older or migrated services can recover missing variables from their running container for review and saving, without overwriting saved values. Apply compares against the running service and recreates supported Docker services from their existing image, retaining ports, networks, mounts and resource limits. Failed startup restores the previous container; unavailable comparisons remain unknown, and unsupported runtimes direct the operator to redeploy.

  • Download de ambiente e proteção secreta

    Download .env exports the listed values, including saved secrets, using quoting that round-trips through Upload .env. Inline service environment, build arguments and their saved deployment/Compose snapshots are now encrypted at rest; API presentation masks protected values and preserves them on round trips (#844).

Migração e portabilidade

  • A migração do Compose inclui a transferência de domínio

    Discovery reports existing proxies and matches Traefik routes through private container addresses as well as published ports. The wizard saves service environment and selected routes, prepares Edge during migration, and requests confirmation before taking over an existing proxy. Selected sites attach to their migrated services, existing certificates are reused, and unresolved routing prevents automatic source container removal (#905, #908).

  • Reutilizar um serviço em projetos

    Shared service connections retain the service's owner, data and connection settings instead of duplicating it. Existing Docker private links require separate migration when moving an application to a cluster.

  • Exporte a configuração, o ambiente e as credenciais de um projeto

    Project settings download a portable plaintext file without a passphrase. The export identifies its server and Cloud dependencies; import previews the contents and requires explicit target mappings. Runtime data stays on its original server, and Cloud projects require the same Openship Cloud account. Imported credentials are encrypted with the destination instance's key. Configuration transfer does not copy runtime volumes or perform a whole-instance server cutover.

Domínios e certificados

  • Wildcard HTTPS com verificação automática de DNS ou TXT manual

    Project and service domains such as *.example.com agora abra a configuração do certificado embutido. Provedores de DNS conectados automatizam a verificação; os pedidos TXT manuais mantêm seu progresso durante as reconexões e reinicializações do controlador. API, SDK e MCP compartilham as mesmas operações de início, status, verificação e cancelamento. Os certificados existentes sobrevivem às tentativas malsucedidas e o HTTPS é relatado como pronto somente depois que sua rota estiver ativa. Os certificados manuais incluem orientações de renovação em todos os nove idiomas do painel (#954).

  • Gerenciar vários domínios curinga

    Configure wildcard domains in Settings and choose the domain to use during project setup (#819).

  • Novas tentativas de roteamento reconciliam o estado salvo e ativo

    Retry routing checks Edge, reapplies project routes and synchronizes domains, with inline progress logs and refreshed results. Live ownership checks recover stale hostname/host-port reservations left by deleted or recreated projects. Repairs preserve complete routes and canonical endpoints when aliases are removed (#915, #922, #925).

  • Estados pendentes explicam o que acontece a seguir

    Domain details distinguish verification in progress, scheduled retry and failure, show the reason and next retry time, and offer a manual retry. Durable backoff prevents overlapping background sweeps from repeatedly retrying the same domain. An SSH observation failure no longer clears a working certificate or becomes a claim that HTTPS is absent (#911, #922).

  • Certificados importados e rotas de contêineres são recuperados corretamente

    Certificate lookup follows managed lineages and avoids collisions after import; recovery excludes ACME challenge ports from application upstreams. Static sites inside containers route through their owning service, and Edge serves an Openship error page for unavailable upstreams (#879, #913).

Backups e restauração

  • Faça backup agora a partir do painel de projeto, serviço ou volume

    Service shortcuts reuse an applicable policy and run only the selected service. Project policies skip stateless services and admit their eligible runs together. Progress shows saved phases, elapsed time and transferred bytes, reconnects across workers, and updates recent history even after the progress view is dismissed.

  • Backups incrementais opcionais

    Policies can reuse verified unchanged blocks, with a complete block index for each restore point. Retention preserves blocks still referenced by another snapshot, and storage totals count shared objects once. Full backups remain the default. Captures still scan the whole source and transfer through the Openship backup worker.

  • A retenção e os destinos permanecem consistentes

    Pruning runs after successful capture and through the scheduled sweep, preserving protected copies and backups used by active restores. Existing runs retain their original destination when a policy changes, and failed cleanup remains retryable without invalidating a successful backup. SFTP failures close streams and clean partial uploads instead of leaving the worker stuck (#817).

  • Restaurar validações antes de substituir dados

    Preparation and confirmed apply share source/target checks, integrity verification and exclusive access to the project or mail server. Runtime/stop failures abort before destructive writes; partial-write failures are reported and do not automatically restart a service on incomplete volume data. Redis/Valkey restore validates persistence settings, and PostgreSQL restore uses a transaction for each supported artifact. Release tests now exercise backup, incremental reuse, retention and restore with real Docker volumes and databases (#892, #946).

GitHub e acesso

  • As conexões da nuvem GitHub terminam no painel

    Installation completion refreshes repository access and the connection state instead of leaving the page loading after GitHub has finished. Device sign-in keeps its code and instructions visible until completion; transient and rate-limit failures no longer discard durable credentials (#920, #951).

  • A seleção do repositório permanece sincronizada

    Branches load on demand while keeping selection and keyboard focus, and changing the branch rescans deployment configuration. Partially successful push-webhook dispatches retry failed targets without redeploying targets that already completed (#847, #870).

  • O login e os convites respeitam o fluxo configurado

    Clients can discover enabled login providers, and signed-out invitees can reach account creation and complete acceptance without the dashboard's prior navigation race.

Painel e área de trabalho

  • Ícones compartilhados e layouts mais consistentes

    Dashboard and desktop use a theme-aware icon catalog with bundled local assets. Service headers, tabs, environment controls, volume forms, source settings and log controls have consistent spacing and typography; mobile navigation and crowded rows are improved (#942, #946).

  • A topologia fica dentro do projeto

    The graph has an optional expanded view, improved loading placeholders and compact service nodes. Clicking a node opens its details directly; long runtime identifiers truncate with copy actions rather than widening the panel.

  • As páginas de implantação colocam ações e registros em primeiro lugar

    Open site and Open project remain prominent, multiple exposed domains can be selected, and preparation, service status and single-app steps share clearer progress indicators. Logs have bounded layout, search and copy controls; history filters survive returning from a deployment.

  • As páginas de backup mostram dados retidos e estado real de execução

    Global and destination views share paginated history, restore actions and usage information. Successful retained copies, active attempts and physical storage totals are distinguished; history remains available after policy changes.

  • A inicialização da área de trabalho segue o tema do aplicativo

    A redesigned loading screen uses shared colors, clearer progress and service startup states (#952).

Monitoramento e confiabilidade do tempo de execução

  • O monitoramento se recupera após interrupções de conexão

    Desktop connectivity loss is distinguished from a confirmed remote runtime failure, with recheck and reconnection handling. Overlapping status requests no longer stop polling or replace newer results, and issue feeds remain available when a host adapter cannot start. Services show a checking state while runtime status is unknown (#927, #949, #951).

  • As visualizações de tráfego usam a mesma série temporal

    Overview and monitoring render timestamped request buckets with clear time ranges, area/column views and loading skeletons. Analytics failures stay within the affected view instead of appearing as empty traffic or replacing fresh data with stale responses.

  • Recursos de longa duração são limitados e liberados

    Container log retention is bounded for newly created managed containers, session caches preserve active work at capacity, and closed log, terminal and IMAP streams release their subscriptions. Busy builds retain their SSH transport; abandoned terminal handshakes release their slots and resumed shells remain bound to the authorized target (#950, #951).

  • A administração do servidor relata falhas acionáveis

    MacOS hosts expose system statistics, server responses match shared diagnostics contracts, and deletion refuses hosts with active deployments. SSH group refresh preserves active sessions after Docker installation.

Nuvem e API

  • O faturamento na nuvem segue a organização selecionada

    Plans, checkout, credit top-ups and renewal management use Oblien namespace entitlements. Purchased limits survive catalog changes, deployment/recovery checks enforce available capacity, and checkout completion verifies payment delivery rather than trusting the return URL. Billing portals remain scoped to the organization (#910).

  • APIs autônomas limitam inundações não autenticadas

    A separate per-IP guard runs before authentication without consuming the route's own limit. Cloud mode or explicit OPENSHIP_TRUST_EDGE=true delega esse teto externo ao proxy upstream, preservando os limites por rota (#123).

Correio

  • Verifique e renove os certificados que os clientes de email realmente usam

    Mail settings show expiry and the certificates served by SMTP and IMAP, with actions to check and renew them. Successful renewal reloads Postfix and Dovecot and verifies the served certificates. Automatic renewal uses the shared scheduler; expiry, renewal failures and stale served certificates appear in Health and Monitoring. Scheduled renewal requires the Openship controller to remain running.

  • Atualizações de webmail sem assinaturas duplicadas

    Inbox updates use a single owned SSE/IMAP IDLE connection with cleanup on disconnect. Replies fill recipients and subject correctly, Trash uses IMAP deletion, and mobile composer, accessibility and browser-cache failures are corrected (#897, #904, #921, #950).

  • O bloqueio de conteúdo remoto também abrange CSS

    Disabling remote images prevents CSS imports and URL-based fetches from leaking a read receipt (#220).

  • Configuração, entrega e alertas de correio são mais confiáveis

    Setup distinguishes an unverified public SMTP probe from a stopped server; database port selection handles conflicts; mounted certificates and Amavis state recover on restart. Relay TLS and SES MAIL FROM checks are corrected, delivery health evaluates the full queue, and captured messages remain until notification delivery is durably queued. Job and backup notifications include their relevant target, outcome and log details (#834, #865, #867, #945, #951).

Liberar verificações

  • Continuar uma versão não publicada com código atualizado

    Reuse successful whole checks only when their source and workflow inputs match, and rerun failed or affected checks. Artifact reuse verifies the original run and immutable artifact identity; concurrent tag changes and earlier publishing attempts prevent unsafe continuation.

  • Jornadas reais de aceitação de aplicativos, bancos de dados e armazenamento compartilhado

    Release checks exercise MCP dispatch, image publication, deployment, public routing, scaling, updates, rollback, worker recovery and project cleanup. Separate database tests verify real queries, replica/shard changes, backups, restores, imports and upgraded copies. Shared-storage tests use independent Linux VMs for SSH installation, cross-server writes, volume growth, disk-copy rebuilding and external backup recovery. These heavier journeys run in the release gate or on demand.

Notas de atualização

  • Dimensionando o escopo nesta versão

    Cluster management is available from self-hosted and desktop controllers. Application scaling supports single apps and workers with project-owned shared files. Compose application scaling, CPU/traffic-driven autoscaling, automatic server provisioning and live cluster membership changes are not included.

  • Mantenha o banco de dados e a chave de criptografia juntos

    This release includes database migrations and converts legacy plaintext service configuration when the engine starts. Back up the database and retain the instance encryption key (BETTER_AUTH_SECRET para instalações de API) antes de atualizar. O downgrade para uma versão anterior a esta proteção requer o backup do banco de dados correspondente. Use a Transferência de dados com segredos incluídos ao mover a configuração entre instâncias com chaves diferentes.

5 de set.2026v0.7.2RecursosCorreçõesBreaking1 atualização

Patch de manutenção suave para confiabilidade de compilação de Docker. Sem alterações significativas na API ou migrações de banco de dados.

Construções

  • As compilações Docker bem-sucedidas não são mais rejeitadas pelo texto do log de diagnóstico

    Fixes a regression present in 0.7.1 where successful workspace scripts reporting Exited with code 0 pode falhar na implantação (#832). As compilações de imagem única e Compose agora distinguem Docker erros do mecanismo da saída do aplicativo, tanto para construtores clássicos quanto para construtores BuildKit. As dicas de diagnóstico enriquecem as falhas reais sem substituir a conclusão bem-sucedida ou ocultar o erro de Docker; As compilações SSH continuam a usar o status de saída do comando. As salvaguardas de cancelamento e inatividade permanecem em vigor.

4 de set.2026v0.7.1RecursosCorreçõesSegurança24 atualizações

Esta versão fortalece o ciclo de vida completo da implantação, torna a reconciliação do Compose sem perdas, conclui a configuração do servidor remoto e o direcionamento da CLI, corrige a integridade e a administração do correio externo e envia o trabalho de convite, DNS, roteamento de catálogo e experiência de atualização acumulado desde 0.6.9.

Controle de origem

  • Os espaços de trabalho auto-hospedados podem possuir e gerenciar vários GitHub aplicativos

    Settings → Git now supports one-click GitHub.com manifest creation and manual GitHub/GitHub Enterprise Server registration, without an Openship Cloud or OAuth dependency. Private keys, client secrets, and webhook secrets are encrypted at rest; source-specific JWTs mint short-lived repository-scoped tokens against the correct API origin; GitHub sends verified lifecycle, push, and check webhooks directly to the instance. Owners can install an App on multiple accounts, rotate and verify credentials, select a default source, and safely delete one while project bindings move to an available replacement. Existing environment-backed Apps, gh, tokens pessoais e chaves SSH por servidor permanecem substitutos compatíveis (#782).

  • GitHub A instalação do aplicativo é segura para locatários de ponta a ponta

    Install callbacks bind a durable one-shot nonce to the initiating user and workspace and verify the reported installation against the configured App before atomically persisting and reconciling it. The cloud callback survives API replicas/restarts, rejects removed workspace members, and cannot bind another tenant's caller-supplied installation id. Installation rows, token caches, project bindings, lifecycle webhooks, and reconnects are workspace-scoped; webhook arrival order never guesses a workspace from membership order (#759).

Contas e equipes

  • Convites de organizações auto-hospedadas agora funcionam para novos usuários

    The claim page loads safely before sign-in, routes existing users back after login, offers token-bound account creation only when authorized, and exposes a copyable link beside each pending invitation. Invitation authorization, identity, credential, personal workspace, and membership now commit under one locked transaction, so cancellation races and failed signup cannot leave an unauthorized or partial account that blocks retry. Accept, reject, cancel, and signup mutations are serialized per invitation across API replicas. API access logs and Edge request telemetry also redact invitation bearer tokens and discard query strings before storage (#743).

DNS

  • Domínios personalizados de serviço usam o fluxo de trabalho de planejamento/aplicação de DNS explícito

    Saving a service route creates the same pending domain row as every other custom domain, then the shared records panel previews provider changes and applies them only when requested. The API documentation no longer promises a silent provider write that the product deliberately does not perform (#760).

Configuração do servidor

  • Servidores remotos sempre exigem Docker antes do Edge

    Server readiness no longer inherits the control plane's DEPLOY_MODE. Docker e Git são verificados para cada destino gerenciado, enquanto um planejador de dependência compartilhado insere e ordena Docker antes do Edge baseado em contêiner em toda a configuração de streaming, SystemManagere proteções de instalação direta de componentes (#767).

Construções

  • openship.json o ambiente agora atinge Dockercriações de arquivos de ponta a ponta

    Top-level project variables are recovered from the trusted source, encrypted into each deployment snapshot, and passed through the existing shared Docker build-argument resolver for first deploys, redeploys, webhooks, folder uploads, and explicit single-app mode. Native services[].buildArgs adiciona substituições por imagem (null herda o valor do projeto correspondente), enquanto o serviço env permanece apenas em tempo de execução (#795).

  • BuildKit cria trabalho a partir de instalações auto-hospedadas baseadas em Bun

    Docker's reverse h2c session now bypasses Bun's incompatible node:http caminho de atualização, mantendo a sessão BuildKit do dockerode e o serviço de autenticação de registro. Compilações locais do Compose usando diretivas de sintaxe, montagens de cache, heredocs e outros recursos de arquivo Docker somente do BuildKit não falham mais /session antes do arquivo Docker iniciar (#745).

Atualizações

  • Os prompts de atualização mostram o changelog do produto

    Dashboard and desktop update surfaces now read the matching version from the tagged CHANGELOG.md em vez de repetir o corpo da versão GitHub. O painel de atualização nativo mantém a cópia de aconselhamento separada de um changelog redimensionável e rolável, e todas as ações do changelog abrem a página da versão em openship.io em vez de GitHub (#752).

  • Implantações bem-sucedidas não anunciam mais atualizações obsoletas

    Resolving the tracked branch head refreshes its upstream cache while a deployment is in progress, and successful deployments invalidate cached upstream state before the UI refreshes. The update banner and issues feed therefore compare the live deployment against a fresh upstream version instead of an older cached commit or image digest (#726).

Aplicativos de catálogo

  • Os endpoints do aplicativo somente porta são realmente publicados

    An explicit port-only choice now persists a fixed all-interface Docker binding, including for catalog routes such as Supabase Kong that declare a served port but no Compose ports entrada. Isso faz com que o URL do servidor do assistente e {{publicUrl:…}} substituições verdadeiras. Tentar novamente um rascunho com falha reconcilia a ligação de forma idempotente e mudar para um domínio remove ou restaura apenas o mapeamento de propriedade do instalador (#770).

Entrega de correio

  • A configuração do correio agora prova a acessibilidade pública antes de declarar sucesso

    The final setup step combines the target's listener table with bounded off-box TCP checks for 25, 465, 587 and 993. The Health tab shows each port as a first-class signal, reusing a coalesced 60-second sweep, and test-email timeouts now identify provider firewalls/security groups/security lists/NSGs instead of blaming a stopped SMTP daemon when Postfix is demonstrably listening (#755).

  • A integridade do correio não trata mais respostas IPv6 com IP falso como DNS quebrado

    Synthetic ULA AAAA responses from Clash/sing-box are now unknown, correspondendo ao comportamento do registro A existente. Juntamente com a linha informativa do SpamAssassin e a comparação DKIM de string dividida normalizada, isso fecha todos os três caminhos de falsos positivos relatados em #240.

  • O webmail retransmitido mantém o caminho correto de entrega dividida

    Webmail continues to submit to the local Postfix on 465, which alone owns relay scope, DKIM signing, and provider credentials. The identical timeout reported in #391 now receives the shared public-port diagnosis; provider relay credentials are never copied into the webmail container.

  • O remetente da plataforma agora se auto-cura em vez de ficar preso no SMTP 535

    Cached openship@<domain> as credenciais são reutilizadas apenas enquanto a caixa de correio ativa e as linhas de encaminhamento permanecem ativas. Uma linha excluída é recriada automaticamente e um transportador já armazenado em cache gira uma vez e tenta novamente com segurança em uma rejeição de autenticação (#754).

  • A caixa de correio da plataforma é protegida e reparável

    Ordinary mailbox edit and delete operations reject the Openship-owned sender, while the Mailboxes tab exposes a dedicated password rotation/repair action that also works when the row is missing.

  • A configuração de email funciona com usuários SSH não root

    Relay maps and additional-domain DKIM configuration now elevate only root-owned host-file operations while Docker commands keep the login user's daemon context. Relay credentials are published atomically as 0600, e um servidor sem root ou sudo sem senha recebe uma recusa digitada acionável, a menos que a montagem de ligação de correio tenha sido explicitamente tornada gravável para esse login (#756).

Cancelamento de implantação

  • O cancelamento após a construção de uma imagem agora interrompe todo o trabalho de implantação

    Cancellation propagates through post-build preflight, human prompts, host-scoped provisioning locks, activation, health checks, routing, and both single-service and Compose pipelines. A durable database signal also wakes a worker running in another API process.

  • A reimplantação aguarda a conclusão real do trabalhador

    A cancelled row keeps its execution lease until cleanup has finished, while the dashboard shows the cancellation still stopping instead of offering a redeploy that cannot safely start. The API and CLI report success only after that lease is released; otherwise cancellation remains explicitly pending. Refreshing reattaches to that server-backed state (#757).

  • O cancelamento não pode substituir ou anular o lançamento ao vivo

    The cancelled transition is conditional and atomic, and cleanup excludes containers carried forward from the active Compose release. If ownership cannot be proven, cleanup fails closed.

Compor reconciliação

  • As edições do repositório não podem apagar silenciosamente as variáveis de ambiente do serviço

    Removing one or more environment keys from Compose now preserves the running service configuration and creates an explicit drift review, even when the operator never edited the imported baseline. Accepting that review remains the deliberate way to apply the deletion.

  • Projetos Compose de caminho local materializam seus serviços automaticamente

    project create --local-path ... --type services agora usa o scanner canônico da API e persiste as linhas detectadas imediatamente. A implantação e a reimplantação também releem a mesma fonte local por meio do reconciliador de três vias existente, de modo que um projeto herdado de linha zero se autorrepare em vez de entrar em um pipeline de serviços vazio (#751).

  • As expressões do Compose env têm um significado de sincronização/implantação

    Raw manual syncs preserve ${VAR} origem e resolvê-lo a partir do ambiente final do projeto/serviço no momento da implantação, enquanto Docker As sincronizações CLI normalizadas pelo Compose carregam um marcador de valor final explícito, portanto, escapado $$ nunca é expandido duas vezes (#751).

  • Falhas de terminal sobrevivem à atualização

    The deployment lifecycle writes one deduplicated terminal error into the durable build log for every lifecycle failure path, including an empty Compose service set, instead of leaving the explanation only in deployment.error_message (#751).

Interface de linha de comando

  • Novos projetos e implantações podem ter como alvo um servidor SSH registrado

    project create --server <id> armazena a ligação inicial, enquanto deploy --server <id> impulsiona uploads de Git e pastas por meio do mesmo resolvedor de destino no escopo da organização e simulação de implantação que o painel. A resposta de implantação expõe um ID estável para --watch, project get mostra o destino resolvido e uma implantação com falha nunca redireciona o projeto (#763).

30 de ago.2026v0.6.9Recursos7 atualizações

Esse hotfix crítico de segurança de implantação faz com que a propriedade e o roteamento herdados do Docker Compose falhem. As pilhas não gerenciadas existentes não podem mais ser confundidas com uma implantação OpenShip ou duplicadas silenciosamente, e uma reimplantação comum no mesmo servidor não pode mover um serviço roteado para uma porta de host diferente.

Implantações e roteamento

  • As pilhas existentes do Compose nunca são adotadas implicitamente

    Before changing containers or routes, a normal deployment checks the target for an untracked Docker Compose stack with the same project slug and service names. A collision now stops with FOREIGN_COMPOSE_STACK e instrui o operador a importá-lo/adotá-lo, removê-lo ou renomeá-lo. Os contêineres adotados explicitamente e os contêineres já rastreados por OpenShip continuam normalmente.

  • As portas de host do mesmo servidor permanecem bloqueadas durante as reimplantações

    A routed service keeps its active host port on its current physical server. If that port cannot be reclaimed safely, deployment stops before routing changes instead of allocating a new port and leaving the public hostname pointed at the wrong workload. A real server migration may still allocate a new host port.

  • Avisos de contêineres duplicados exigem evidência de propriedade

    Normal projects no longer claim same-slug containers through Docker Compose labels alone. Native Openship labels, the canonical managed name, or the tracked container id establish ownership; Compose-label recovery remains available only for an explicit adoption.

Compor reconciliação

  • Os metadados do analisador legado não criam desvios falsos no repositório

    Adding environment/build-argument template provenance to an older service baseline is treated as a one-time metadata upgrade, not as a Compose edit. Real changes arriving with that metadata are still reported, and operator-edited live values remain intact while the baseline advances.

Monitoramento

  • Issues agora é o espaço de trabalho Monitoramento

    The dashboard adds a Health view for every tracked project service, with fleet counts and state charts for healthy, unhealthy, crash-looping, down, and unknown workloads. Rows show the serving server and last observation, and link back to the service that owns the container.

  • Leituras de integridade reutilizam o inspetor existente

    The page reads an in-memory snapshot produced by the grouped health sweep and Docker-event accelerator; it does not create a poller per container or perform Docker I/O on page refresh. Per-service monitoring can be disabled before the workload enters the watch, inspection, event, or notification path.

  • As atualizações e novas verificações da frota continuam em segundo plano

    Bulk component updates start together without holding a modal open, retain their durable sessions across navigation and refresh, and allow an operator to reattach to a specific log. The checker batch similarly exposes one shared progress session so multiple tabs cannot multiply Git, DNS, Docker, or version scans.

Upgrade priority: critical for legacy or externally created Compose > workloads. Fully tracked Openship deployments are not expected to hit the > collision path, but installations that previously deployed a same-slug stack > outside the current control-plane records should upgrade before redeploying it.

25 de ago.2026v0.6.8RecursosSegurança20 atualizações

Os projetos do Compose agora são implantados como os serviços que declaram, com seus argumentos de construção e ambiente dinâmico intactos desde a importação até a reversão. As movimentações de instância podem ir diretamente de uma instalação auto-hospedada para outra sem copiar uma chave de criptografia, e o fluxo de trabalho do arquivo mostra e filtra o que ele carregará. Esta versão também fortalece a propriedade de domínio personalizado, a alocação de porta de host, os limites de credenciais Git e a recuperação de borda em Linux e macOS.

Transferência de instância

  • Mova uma instância diretamente, com credenciais incluídas

    The destination creates a single-use, ten-minute receive code for Replace or Merge mode; the source encrypts the selected database rows and plaintext credential bundle directly to that destination, and the destination immediately re-encrypts every transferred secret under its own instance key. Server SSH passwords and keys, environment variables, tokens, registry and DNS credentials, and backup credentials move without sharing either instance's BETTER_AUTH_SECRET ou gerenciar uma senha de transferência (#656).

  • Veja e filtre a exportação antes de baixá-la

    Settings now shows the durable row count and a count beside each optional history group. Analytics, audit/notification activity, backup history, incident history, and migration history can be included independently; configuration, projects, services, servers, users, and credential records always stay in the portable core. Leaving the selection absent preserves the legacy full export (#656).

  • Arquivos com credenciais não podem ser importados meio desbloqueados

    The offline export/import path remains available, but a file containing a sealed credential bundle now requires its passphrase before any database write. Invalid bundles are rejected before restore rather than importing rows whose secrets were silently scrubbed.

Composição e ambientes

  • Os serviços do Compose conduzem suas próprias compilações

    A project with composePath é materializado no pipeline de serviço em vez de cair em uma compilação de arquivo Docker genérico. Mapear e listar formas de build.args, argumentos simples e ${...} as expressões são armazenadas por serviço e sobrevivem à sincronização CLI, reconciliação, adoção de migração, reimplantação de instantâneos e reversão. As compilações de soquete, SSH, lote e nuvem Docker usam o mesmo resolvedor de argumento, e o registro do comando de compilação de OpenShip não imprime valores de argumento (#689).

  • A remoção dos argumentos de compilação do Compose remove os argumentos armazenados

    An empty args mapa ou um excluído args key limpa valores obsoletos e proveniência de interpolação, enquanto instantâneos criados antes da existência de argumentos de construção permanecem não destrutivos durante a reversão (#689).

  • Builds incompatíveis do Compose falham antes da implantação

    Malformed arguments, repository-escaping or remote contexts, and build features Openship cannot reproduce no longer leave the old service shape running silently. A declared Compose project with no materialized rows is scanned once to bootstrap its topology, while an explicit single-app choice remains single-app.

  • O ambiente do Dynamic Compose é resolvido no momento da implantação

    Raw expressions such as postgresql://user:${POSTGRES_PASSWORD:?set it}@postgres:5432/app são avaliados em relação ao projeto final, às camadas de liberação congelada, em linha e com escopo de serviço. Requisitos incorporados, chaves de passagem, padrões, expressões aninhadas e valores de escape retêm a semântica do Compose; uma variável necessária não resolvida falha nesse serviço com a chave ausente chamada (#673).

  • Variáveis de serviço manuais são substituições duráveis

    The service Environment tab now owns service-scoped environment rows rather than rewriting the Compose-owned service.environment objeto. Os valores adicionados na IU, portanto, sobrevivem a uma nova análise do Compose e à reimplantação do projeto. Salvar um segredo não revelado — incluindo renomear sua chave — preserva seu texto cifrado existente em vez de armazenar a máscara ou excluir o valor.

Implantações e roteamento

  • Imagens de contêiner pré-construídas podem ser rastreadas como versões

    A single-app project can resolve versions from GitHub Releases or an HTTPS version feed, optionally pin a version, and render that tag into a registry image template. Deploy and Update pull the application image directly on Docker or Cloud — no Git clone, Dockerfile build, or release archive — while drift detection compares deployed and upstream semver. Successful Docker releases freeze the immutable registry digest so rollback can reacquire the exact image after local retention expires; source changes apply atomically across environments and are available in both the dashboard Source tab and openship project release-image (#694).

  • Aplicar realmente significa reiniciar sem reconstruir para um único aplicativo

    Docker and host-mode projects reuse the active deployment's retained artifact even though they have no service rows. Apply never fetches Git or silently turns into a rebuild; if the artifact is gone, it says to Redeploy instead (#674).

  • O ponto de verificação de DNS abrange Docker e todas as rotas do Compose

    Pressing Deploy now shows records for single-app custom domains, service scalar routes, and multi-route Compose endpoints. Multiple hostnames appear together, www é agrupado com seu ápice e uma visualização de implantação remota usa o endereço público do servidor selecionado em vez do endereço desta instância (#663).

  • A reimplantação não pode desanexar um domínio personalizado

    Deployment reconciliation preserves both pending and verified custom-domain rows and their live targets when a release omits them. A failed deployment rolls back only generated managed routes, never user-owned custom configuration, and concurrent hostname claims use database-authoritative ownership instead of letting the losing project route another project's domain (#675).

  • Contêineres parados não podem transformar um nome de host antigo em outro aplicativo

    Loopback ports now have database-enforced, physical-target-wide ownership across organizations. Allocation reserves the port before Docker binds it, treats local and “This Server” as one namespace, and persists every routed Compose port through stopped and reconciling states. A stale vhost/TLS certificate can therefore never be repointed accidentally when a later deployment starts listening on the same number (#682, GHSA-284v-9jw3-jfhx).

  • Tentar novamente o roteamento repara a borda primeiro

    When openship-edge está parado ou ausente, Retry Routing reconcilia e verifica a integridade antes de tocar nos vhosts. Uma borda irrecuperável retorna um aviso acionável imediatamente, em vez de ficar suspenso até que a solicitação de rota expire (#693).

  • A exclusão do projeto não causa mais impasses em um ouvinte OpenResty vazio

    Route cleanup validates the installed configuration and signals only the verified running master instead of starting a second nginx process on ports 80/443. Listener checks account for every socket owner, including mixed SO_REUSEPORT ouvintes e falha no fechamento quando a propriedade não pode ser comprovada. Os sinalizadores de exclusão agora funcionam de forma consistente em strings de consulta e corpos JSON; forceOrphan registra a limpeza inacabada do host de forma duradoura antes de remover o projeto para que o coletor de lixo possa tentar novamente com segurança (#700).

Hosts e borda

  • A aquisição de origem Docker segue o transporte real

    Preflight and the build pipeline now share one source-location plan. Local socket and TCP daemon builds prepare source on the API host, remote SSH Docker builds may clone on the target, and bare or cloud builds retain their own boundaries. A local server row therefore no longer asks a nonexistent remote clone path to use ambient Git credentials (#654).

  • macOS montagens de borda usam caminhos de host físicos

    Bind sources are canonicalized on the machine that owns the Docker daemon, so /var e /etc resolver para seus /private/... alvos antes que Docker Desktop ou OrbStack os veja. Uma borda de aparência saudável com montagens lógicas obsoletas é recriada nos mesmos diretórios vhost, certificado, ACME e dados estáticos (#692).

Segurança

  • Um diretório de configuração CLI explícito GitHub é um limite de isolamento

    Fallback token discovery reads exactly the hosts.yml selecionado pela precedência CLI GitHub em Linux, macOS e Windows. Se GH_CONFIG_DIR ou XDG_CONFIG_HOME está definido, mas ausente ou sem token, OpenShip não passa mais para o diretório inicial de outro usuário e pega emprestada essa credencial (#687).

Correio OpenShip

  • O SMTP de entrada possui DNS dentro do chroot do Postfix

    Every mail-engine boot now refreshes resolv.conf e os arquivos NSS de suporte dentro do spool Postfix persistente antes do supervisor iniciar. O mecanismo falha ao fechar se nenhum resolvedor puder ser instalado, em vez de iniciar um serviço SMTP que rejeita todos os remetentes legítimos com 450 Helo Host not found (#686).

Painel

  • Os ambientes do projeto são atualizados sem atualização

    Creating an environment commits it to shared state immediately and reconciles the canonical list; deleting one removes it from every affected cache and navigates to the best surviving sibling. A failed follow-up read no longer makes a successful create look like it failed (#657).

17 de ago.2026v0.6.6RecursosCorreçõesSegurança27 atualizações

O correio aprende a receber e os segredos de terceiros levam você para casa. OpenShip O Mail agora captura, filtra e lê mensagens recebidas, e uma mensagem recebida pode gerar uma notificação. Além disso, um único armazenamento de credenciais com escopo organizacional substitui a tabela única de tokens DNS e desbloqueia pulls de imagens privadas em qualquer host. O catálogo de aplicativos pode ser instalado de ponta a ponta, o log de auditoria sai das Configurações para sua própria página e os uploads param de falhar em 1 MB.

Segurança

  • As gravações de trabalho são autorizadas nos próprios servidores de destino do trabalho

    Jobs are instance-wide, so the job:write a permissão (que verifica a associação à organização) não é, por si só, autoridade sobre os servidores nos quais um trabalho de comando é executado. A edição e a exclusão de um trabalho agora passam pela mesma verificação de servidor por destino que a criação e a execução de um trabalho já passaram, e uma negação é indistinguível de um trabalho que não existe. Relatado externamente; testes de regressão adicionados. As instâncias auto-hospedadas com mais de um nível de confiança devem ser atualizadas; OpenShip Cloud nunca foi afetado (a API Jobs é localOnly).

Credenciais

  • Uma loja para segredos de terceiros

    A provider registry (container registries, Cloudflare, and room for what comes next) behind one table, with every secret sealed in a single enc1: envelope em vez de uma coluna por campo. Uma credencial é verificada em relação ao seu provedor antes ele é armazenado, portanto, um token inválido é rejeitado onde você o cola, em vez de onde uma implantação precisa dele.

  • Imagens privadas atraem todos os hosts

    Registry auth is resolved per image from that store (#581). On a remote host the config goes to a temporary DOCKER_CONFIG diretório (0700, arquivo 0600) removido independentemente de o pull ser bem-sucedido ou falhar, portanto, um pull nunca edita o próprio operador ~/.docker/config.json. Os pulls locais ainda passam pelo armazenamento de credenciais do próprio daemon, que é o que mantém um desktop Docker credsStore trabalhando.

  • Credenciais DNS dobram-se nele

    Existing Cloudflare tokens are re-wrapped at boot. A token that cannot be decrypted (a rotated BETTER_AUTH_SECRET) é deixado exatamente onde está, e a linha herdada é excluída apenas quando a nova existe — uma falha no meio do movimento deixa uma duplicata, nunca zero credenciais.

  • As credenciais do Git têm sua própria guia

    Clone credentials were filed under API tokens, which is neither where you look for them nor somewhere a second Git provider could go. "API tokens" now means only that.

Correio recebido

  • Uma caixa de correio pode ser lida

    Inbound capture, read and watch, so mail that arrives is stored and retrievable rather than merely delivered.

  • A filtragem de entrada falha ao fechar

    Loop guards, a spam gate, and scope matching that drops a message it cannot confidently attribute instead of guessing an owner for it.

  • mail.inbound_received é uma notificação

    Inbound mail can drive a channel, in a mail group that appears only on self-hosted instances.

Correio OpenShip

  • A criação da caixa de correio é executada no mecanismo, não no host

    doveadm e chown executado no host, onde eles não existem, portanto, a criação de uma caixa de correio retornou 500 (GH-562).

  • A inicialização do banco de dados falha ruidosamente

    The script had no set -e, portanto, uma etapa com falha ainda relatou sucesso e deixou um mecanismo parcialmente provisionado com aparência saudável (GH-562).

  • As telas de e-mail se parecem com o produto

    The channel picker is now the same component the notification and job screens use, with real brand marks in place of a native checkbox that renders in the browser's colours rather than the theme's, and the admin tabs drop the borders and status dots that matched no pattern here.

Catálogo de aplicativos

  • Cada aplicativo é instalado

    Each catalog app now ships a UI and a connection, rather than installing into something you couldn't open.

  • verified significa publicado upstream

    The badge is reserved for bundles published upstream, so it stops implying a review it never represented. Neon is no longer marked verified (neond is a community control plane), and the experimental badge is off both Neon and PostHog.

  • Neon sobrevive ao tempo real de instalação

    Its bootstrap assumed a readiness it never waited for.

Migração

  • Uma seleção é resolvida por identidade, não por nome

    The wizard sent names and the server matched on them (#584), so two containers sharing a name collapsed into one pick, and a name matching something outside the selection could be adopted. A selection now carries container ids, falling back to names only for a service that has none.

  • A própria pilha de OpenShip foi excluída, não é um bloqueador

    The containers running Openship are skipped with the reason named, instead of the whole migration refusing to start.

  • Duas correções para o que uma varredura vhost importa

    Nginx's own default vhost is skipped rather than adopted as a site, and prefix-relative document roots resolve against their prefix.

Borda

  • Uploads padrão para 50 MB

    Nginx's built-in limit is 1 MB, and a project that never opened the proxy panel inherited it, so any real upload died with a 413 the app never saw. client_max_body_size 50m agora envia em http escopo em cada configuração de borda, o que deixa o valor do próprio projeto ganhando onde quer que seja definido. Os hosts instalados antes disso são reparados no local, e um valor ajustado pelo próprio operador nunca é substituído.

Registro de auditoria

  • Sua própria página

    Nothing on it is a setting: you never change anything there, you read what already happened. It sat three clicks inside Settings, which is how a review surface goes unread.

  • Cada filtro está no URL

    Filters and pagination are query parameters, so a view can be linked, shared and reloaded.

  • Os eventos não catalogados são catalogados

    Events emitted without a taxonomy entry now have one.

Correções

  • openship reset-admin-password funciona em uma instalação do Compose

    It authenticated with ~/.openship/internal-token, um arquivo que o caminho do Compose nunca grava: o contêiner da API é inicializado com o INTERNAL_TOKEN de ~/.openship/compose/.env. Então, em uma caixa de composição, o comando cunhado um novo token aleatório, enviei-o e relatei Unauthorized - o comando lockout-recovery era inutilizável exatamente na instalação que precisava dele. O token com o qual esta caixa está sendo executada agora está resolvido em um só lugar, os leitores nunca cunham e um token de propriedade do root .env este usuário não pode abrir, diz isso (executar novamente com sudo) em vez de relatar uma falha de autorização. A mesma correção atinge "Redefinir senha de administrador" do painel de controle, openship doctor (cuja leitura de integridade voltou vazia em todas as pilhas do Compose) e uma caixa vazia :80/:443 takeover, que procurou o token Compose e ignorou a importação dos sites migrados após interromper o proxy da operadora.

  • Uma redefinição de senha usa um código de 6 dígitos

    Rather than an emailed link.

  • Uma implantação cancelada mantém seu motivo

    The failure message was gated on failed sozinho, o que apagou o motivo em todas as linhas canceladas. Mas um cancelamento nem sempre é o seu Stop: a varredura de inicialização é cancelada com "Interrompido pela reinicialização do servidor" e uma falha parcial substituída registra o motivo. Com o motivo descartado, o assistente de instalação tinha apenas o genérico "Falha na instalação" para imprimir sobre uma linha que dizia cancelled.

  • O veredicto de uma instalação e seu motivo concordam

    The wizard decided "was this a cancel?" and "what do I show?" independently, so a stopped install could print "Install failed" underneath the heading "Install cancelled".

  • A verificação aparece apenas quando existe uma linha de domínio

    The optimistic row fell back to the bare hostname as its id, and every guard downstream reads that id as proof the server row exists. So a hostname with no row yet rendered a live Verify button that 404'd, along with a DNS-records panel that couldn't load.

  • Um commit abreviado não é um novo commit

    POST /deployments leva commitSha como tudo o que o chamador envia (openship deploy --commit 1eeaf76, a ferramenta de implantação do MCP, um script de CI) e o git verifica uma abreviatura com alegria: o código correto enviado enquanto a linha registrava um nome que nenhuma comparação poderia corresponder. A verificação de desvio comparou-o com o branch HEAD de 40 caracteres, e como ambos os lados renderizam sete caracteres, a página do projeto anunciava "Novo commit disponível 1eeaf76... você está implantado em 1eeaf76" - permanentemente, com um Redeploy que nunca poderia limpá-lo. Dois shas agora nomeiam o mesmo commit quando um é um prefixo do outro na própria abreviatura floor do git, uma referência que não é um sha (uma tag, HEAD) é lido como "não posso dizer" em vez de desvio, e a referência do chamador é resolvida para o sha completo antes que qualquer coisa o armazene ou compare - o que também desfaz as verificações de confirmação por serviço GitHub, rejeita um sha curto e a desduplicação já implantada do webhook.

11 de ago.2026v0.6.5RecursosCorreçõesSegurança73 atualizações

Um endurecimento e liberação de alcance. Os problemas de segurança relatados foram corrigidos (consulte Segurança abaixo), o canal de controle contêiner→host é provisionado e diagnosticado de ponta a ponta, em vez de falhar silenciosamente, e OpenShip agora é instalado em qualquer mainstream Linux — e em hosts onde você não faz login como root. Também acrescenta openship edge (todo o proxy reverso do terminal), limites reais de recursos que respeitam a máquina que você possui, um shell de produto de correio OpenShip com entrega dividida, webmail reconstruído como um aplicativo de catálogo comum e cinco novos aplicativos de um clique.

Segurança

  • Correções de segurança

    This release resolves a number of reported security issues, with regression tests added for each. Areas touched: authorization on instance-wide and GitHub operations, access-token minting, path handling, the mail engine, webmail's HTML sanitizer, the desktop shell, and redaction in stored build output. Details are published as advisories on the repository. A atualização é recomendada.

  • Endurecimento

    Host-control operations are pinned to the host channel rather than defaulting to the API process's own container, cloud builds can never run on the API host, and stored SSH key material is encrypted at rest and stripped from any cross-host export.

O canal de controle do host

  • openship up provisiona o canal contêiner → host e informa quando não pode

    When Openship runs in Docker, a handful of operations are genuinely host-level (freeing a foreign proxy off :80/:443, configuração do sistema host, mecanismo de e-mail, gravação da configuração gerada pelo aplicativo de catálogo) e chegam ao host por SSH na ponte interna. Instalar agora gera a chave, anexa um restrito from=-fixado authorized_keys linha, verifica se o sshd escuta um endereço que os contêineres podem alcançar, abre a porta em qualquer firewall que o host execute e verifica a viagem de ida e volta - em vez de relatar sucesso e falha na primeira operação do host semanas depois.

  • Ele investiga todas as camadas, porque a falha não se parece com nada

    This address is host-local, so it traverses filter/INPUT onde uma negação padrão ufw vidas; as portas de contêiner publicadas são DNAT e ignoradas, e é exatamente por isso que o resto da pilha parece saudável enquanto este canal trava. Firewall, endereço de escuta sshd, chave e acessibilidade são investigados e relatados separadamente.

  • Uma explicação, cinco superfícies

    The CLI preflight, the API's boot banner, openship doctor, o banner do servidor do painel e o log de implantação em que uma operação de host termina tinham histórias diferentes. Eles agora leem um vocabulário compartilhado, porque cada linha é "sua instalação está boa, este recurso não está" ou "sua instalação está quebrada" - e um operador que lê o errado ou destrói uma caixa de trabalho ou ignora um recurso morto por meses.

  • openship update repara um canal não provisionado

    An install from before this work, or a raw docker compose instalar, pode ser corrigido atualizando, em vez de executar novamente up e arriscando o meio ambiente. Uma implantação que precisa do canal emite o aviso uma vez por implantação, antes da distribuição, em vez de uma vez por serviço.

  • O canal deve ser root, e diz isso

    An operation that needs a root-owned path fails with the actual cause instead of mkdir: cannot create directory '/root': Permission denied.

  • Documentado para instalações feitas à mão

    .env.example explica todas as cinco etapas (chave, linha de chaves autorizadas restritas, endereço de escuta sshd, regra de firewall, recriar a API porque env_file: é lido na criação do contêiner) e um novo página de solução de problemas caminha o reparo.

Qualquer Linux e hosts que não sejam root

  • OpenShip é instalado nas distros que sempre afirmou

    Docker installation was curl get.docker.com | sh em cada Linux, um script que recusa firmemente Amazon Linux, AlmaLinux, Oracle Linux e Alpine. Cada site de chamada tinha sua própria tabela de gerenciamento de pacotes (havia cinco, e eles discordavam), seu próprio teste de systemd e sua própria leitura de "host fora da minha lista de permissões" - sempre "nada a fazer". Os fatos do host agora vêm de um detector, os comandos que atuam neles residem em um módulo e adicionar uma distribuição é um erro de compilação, em vez de uma operação silenciosa.

  • Um mecanismo Docker em funcionamento nunca é substituído implicitamente

    Only an explicit reinstall overrides an engine that's already running, and an installer that skips an already-working component says so instead of leaving the one actionable line nowhere at all.

  • A implantação como um usuário não root funciona

    Three layers answered "may I do root-owned work here?" differently: component installs gated properly, toolchain installs never gated at all, and the server state store assumed the login was root. There's now one privilege resolver, and it elevates the write rather than the verify (so a sudo shell nunca resolve um problema diferente $HOME). Um host de comando forçado que não consegue relatar um uid não recebe mais instruções para "conectar-se como root", o que era o oposto de sua correção.

  • Conjuntos de ferramentas de linguagem são instalados por host, não por suposição

    The toolchain catalog and installer were rewritten onto the same host profile, so a bare-metal build on a non-Debian box gets its runtime installed instead of a not found no momento da construção.

`openship edge`

  • Todo o proxy reverso, do terminal

    A new top-level command: edge up levanta o proxy e serve :80/:443, edge migrate assume um nginx/Apache/Caddy existente e importa seus sites, edge takeover e edge free reivindicar os portos, edge sites lista o que pode ser importado e edge repair diagnostica por que não está sendo veiculado (--fix resolve um conflito de porta).

  • Domínios, regras e tráfego sem abrir o painel

    edge domains add app.example.com --port 8080 registra um nome de host em uma porta e emite um certificado; edge rules gerencia limites de taxa por rota, proibições e acesso geográfico/CIDR; e edge traffic, edge analytics e edge logs leia o que o proxy já registra. As operações de host são apenas Linux; a metade do plano de controle funciona em qualquer máquina, incluindo desktop, em qualquer contexto que esteja ativo.

  • Documentado como referência e passo a passo

    A new A borda guia para as tarefas e um guia completo referência de comando.

Limites de recursos

  • Os contêineres auto-hospedados são ilimitados por padrão

    A self-hosted project silently inherited the cloud free tier (0.5 vCPU · 512 MB) and OOM-killed memory-hungry images. On your own box the container's real ceiling is the machine, so 0 (sem limite) agora é o padrão e cada consumidor testa um limite antes de aplicar um limite.

  • Um limite personalizado é limitado pela máquina real

    Caps were validated against hardcoded constants (4 cores / 8192 MB), so a 64 GB box could not be told to give a container more than 8 GB. The ceiling is read from the Docker daemon's own /info (NCPU, MemTotal) — idêntico para o soquete local e um daemon remoto na ponte SSH em pool — voltando para o sistema operacional quando Docker não estiver acessível. A nuvem permanece inalterada: um espaço de trabalho medido ainda é dimensionado a partir da tabela de camadas.

  • Implanta o comprovante da capacidade do destino

    A cap larger than the host can allocate is rejected before any build work starts, with the machine's real numbers in the message.

Correio OpenShip

  • Execute a instância como um produto de correio

    An instance can present itself as Openship Mail (OPENSHIP_PRODUCT, ou uma alternância em Configurações): o painel esquerdo se torna o plano de controle de e-mail – as dez guias de administração promovidas para entradas de navegação em três títulos, além das linhas de host e configurações que um operador ainda precisa – e a navegação da plataforma fica oculta. Isso é apenas apresentação, nunca um limite de autorização: o webmail ainda é implantado por meio do pipeline comum do projeto, para que os terminais da plataforma permaneçam ativos. A nuvem é sempre a plataforma completa.

  • Alternar entre servidores de e-mail

    The mail surfaces are scoped to a selected server rather than assuming one, with a switcher in the shell and the scope carried through the admin tabs.

  • Provedores de retransmissão de saída são identidades reais

    The relay code carried a "ses" | "custom" union, então SendGrid, Mailgun e Postmark perderam suas identidades no momento em que foram salvos: nenhuma inclusão de SPF, nenhuma viagem de ida e volta na UI, e adicionar um provedor significava editar um if no serviço, o construtor DNS e o scanner. Os fatos por provedor agora são dados que todos os três leem, e a entrega dividida (receber aqui, enviar por meio de outra pessoa) é uma configuração de primeira classe.

  • "A correspondência está realmente saindo desta caixa?"

    The daemon sweep reports that nine processes are running, which says nothing about whether Postfix can hand a message to the next hop. One wrong character in a relay password gave nine green daemons, green DNS, a Test-tab email that reported success (our Postfix accepts and queues before the relay hop), and mail that quietly deferred forever. Outbound delivery is now probed and surfaced on its own, with a reworked Health tab and a summary that names the failing hop.

  • Um console de e-mail

    Live engine output in the dashboard, so a setup that stalls can be read rather than guessed at.

  • Backups que você pode agendar

    The mail admin Backup tab gains a real schedule and retention plan, wired to the same pruning the rest of Openship uses.

  • A configuração falha mais cedo e de forma mais clara

    A preflight checks the things that used to surface mid-stream (password shape, firewall step, DNS), and setup errors render in a banner instead of vanishing into the stream.

Webmail

  • Webmail é um aplicativo de catálogo comum agora

    It installs through the same generic installer, image, volume and routing pipeline as every other app, and installs from /apps just as well as from /emails. The mail-specific part is the only part that stayed: which IMAP/SMTP backend it belongs to — one of your Openship mail servers, or an external provider.

  • O link é armazenado, não analisado em um slug

    The old lookup read webmail-<serverId> recue do slug do projeto, que o instalador genérico nunca produz e que vinculou incorretamente qualquer projeto que alguém chamou de "Webmail Prod". Agora é uma chave estrangeira real, anulada (não órfã) quando o projeto de webmail é excluído, com um substituto de slug herdado que carimba a coluna na primeira vez que resolve uma instalação pré-existente.

  • Sua própria imagem e bootstrap de banco de dados

    A dedicated webmail Dockerfile and a bootstrap script, so first boot provisions its schema instead of depending on the mail engine's.

Catálogo de aplicativos

  • Cinco novos aplicativos de um clique

    Meilisearch, Redis, PostHog, Umami and Neon (Postgres), each declaring its internal connection so it can be linked into a project over the internal network.

  • Emblemas que informam o que você está instalando

    Verified, unverified and hosting-mode badges with explanatory tooltips, so a community template isn't visually indistinguishable from one Openship has booted and checked.

  • Atualizações de esquema de catálogo

    The published app.schema.json obtém os campos acima, e os documentos de referência e o guia "Adicionar um aplicativo" foram reescritos em torno deles.

Roteamento e domínios

  • Uma implantação para de limpar seu vercel.json roteamento

    registerRoute substitui todo o vhost, então um chamador que omitiu cleanUrls / redirects / headers não os deixou sozinhos, ele os excluiu. Esses campos foram construídos em linha em dois locais, portanto, uma implantação simples não os aplicou nem os preservou, e uma reimplantação não relacionada apagou silenciosamente tudo o que um "roteamento de nova tentativa" havia instalado. Eles agora são compilados uma vez, em um módulo puro que todo site de registro de rota carrega.

  • Uma decisão sobre o que a borda disca

    A single resolver owns the proxy_pass alvo: uma porta de host de loopback fixada por padrão (estável durante a reinicialização, nunca voltada para a Internet), o IP da ponte do contêiner como uma opção avançada e um substituto transparente para o IP do contêiner para um serviço Compose interno que não publica nenhuma porta de host. Selecionável por instância, com auto como padrão.

  • Um redirecionamento de domínio sobrevive à emissão de certificado

    The redirect installed for a hostname is no longer reverted the moment certbot succeeds, and it no longer re-fires on internal rewrites.

  • IPs de clientes reais na borda

    The real-IP configuration is derived in one place for every scope, so free subdomains and custom domains agree on what the visitor's address is.

  • As regras de rota têm um conjunto de ponta a ponta

    Per-route rate limits, bans and access rules are covered by an e2e test that drives the real proxy.

DNS

  • Cloudflare DNS, conectado

    Connect a Cloudflare token and Openship writes the records a domain needs itself (#37), issues wildcard certificates over the DNS-01 challenge, and can route a domain through a tunnel instead of an open port.

  • Nós apenas tocamos nos registros que criamos

    The provider claims a record it wrote and leaves everything else in the zone alone, and it refuses to write a hostname it hasn't claimed. Deleting a domain in Openship therefore cannot remove a record that was already there.

Servidores

  • Um formulário de adição de servidor

    The page and the modal were two 400-line forks that had drifted; they're now one component with a variant, so a field added in one place exists in both.

  • Cole ou carregue uma chave privada SSH

    ssh_key_path aponta para um arquivo no host da API, que é inútil em uma instância remota ou VPS onde sua chave reside em seu próprio laptop. Uma chave agora pode ser colada ou carregada de qualquer navegador, armazenada criptografada em repouso, nunca serializada de volta para o cliente e preferida ao caminho no disco, quando presente.

  • O banner de conexão da página do servidor se explica

    Reachability, host channel state, and what each one does or doesn't affect, rather than a single red dot.

  • Os padrões de implantação não podem ser definidos como algo derivado

    The instance default target is a server or cloud; "this machine" is derived (on a server-host box it is already in the server list), so it's no longer an option that means two different things.

Projetos e implantações

  • Renomear um projeto a partir de seu título

    A rename modal, plus copy-id and pause/resume, on the heading where the name actually is. The slug stays immutable (it's infrastructure identity); the display name is free.

  • As ações do contêiner passam por um tubo

    Pause, restart and logs run through the same deployment-runtime path as everything else, so they can't disagree with the platform about which host or runtime a service lives on.

  • Reconciliar e desmontar são mais estáveis

    Record-only deletes, orphan GC scheduling, pending actions and port checks were tightened around the same runtime path.

  • A origem, a construção e o tempo de execução de um projeto são três coisas distintas

    Two boolean flags (hasBuild, hasServer) cada um representava duas preocupações diferentes, de modo que uma implantação poderia ser aceita e falhar um estágio depois. Um projeto agora é descrito por três eixos ortogonais — de onde vem o código (git, uma imagem pré-construída ou um upload), como ele é construído (arquivo Docker, buildpack, estático ou nada para construir) e o que é executado depois (web, trabalhador ou estático) — resolvido em um local que cada estágio lê. Os projetos existentes são classificados exatamente como eram antes.

  • Um aplicativo de arquivo Dockerde repositório privado é clonado novamente

    A Dockerfile build runs no buildpack step, so it naturally carried hasBuild=false, e a única porta que decide se deve buscar um token de clone com chave nesse sinalizador - descartando o token e falhando no clone em um repositório privado, mesmo que o arquivo Docker precise do repositório como seu contexto de construção. Se o código será obtido agora depende apenas de onde ele vem, nunca de como foi construído.

  • Um trabalhador é um tipo de implantação de primeira classe

    A long-running process with no port (a queue consumer, a bot, a cron loop) had nowhere to go: called a server it failed preflight for a missing port, called static it was routed through file-serving and failed for a missing docroot. worker agora é sua própria carga de trabalho – construída como qualquer outro aplicativo, executada como um contêiner sempre reiniciado, sem porta e sem rota, e verificada quanto a um comando de inicialização em vez de uma porta. Escolha-o na opção Servidor / Trabalhador / Estático de um projeto ou defina workload: worker em openship.json.

Compor e instalar

  • up preserva seu .env

    A variable you set by hand is kept and marked as yours, instead of being regenerated out of a fixed key list.

  • Um segredo nunca é removido de uma instalação em execução

    up detecta que criaria um segredo que uma instalação existente já possui (o que deixaria o ambiente criptografado indescriptografável) e recusa, em vez de substituí-lo silenciosamente. O substituído .env é guardado para recuperação.

  • Versões de imagens podem ser fixadas

    An explicit --image-version vence o ambiente e a própria versão da CLI, para o caso em que um release atinge o npm antes de suas imagens chegarem ao registro.

  • Um diretório de dados estrangeiro Postgres foi recusado e não adotado

    The volume's contents are probed before a cluster is started on top of them.

  • openship doctor e repair cobrir mais

    The host channel, an unprovisioned install, and port conflicts, in the same run.

  • Adotar uma pilha do Compose não publica mais suas portas de host

    A migrated 5432:5432 ligaria o host 5432 na próxima implantação e colidir com o que já o continha (geralmente o próprio Postgres de OpenShip), abortando a implantação. Adoção mantém apenas o porto de contêineres; o serviço é acessado pelo nome na rede do projeto e reexposto na aba Domínios. O aviso diferencia uma porta que foi publicada off-box — a regra de publicação de Docker passa pelo firewall do host, portanto, era genuinamente acessível pela Internet — de uma porta apenas de loopback, para que você saiba se algum alcance externo foi realmente abandonado.

  • stop_signal e stop_grace_period são homenageados na reimplantação

    A service that asks for a longer shutdown window now gets a graceful stop, with its own signal and grace period, before it's replaced or torn down, instead of being SIGKILLeditado no meio da gravação por uma remoção forçada imediata. Um contêiner que não aceita ainda interrompe a maneira mais rápida, portanto, não há latência adicional de reimplantação.

Agentes e controle de acesso

  • Conceda a uma automação um shell em um recurso, não em toda a organização

    The only way to let something run a command was a custom-command job, whose grant reaches every server in the org and can't be narrowed. Command execution now hangs off each resource's own permission: a grant on one server (server:admin) é um shell host confinado a essa caixa e uma concessão em um projeto (project:service:write) executa comandos dentro dos contêineres de serviço desse projeto — nada mais amplo. Cada execução é auditada com seu comando, diretório de trabalho e resultado, e o executivo do contêiner é recusado em um tempo de execução que não pode isolá-lo.

  • Agentes de IA são executivos sobre MCP

    Two new MCP tools expose host and in-container execution, each requiring the matching per-resource grant, with a hard timeout and an output cap (the agent's call blocks on the reply and the whole body lands in its context). Tools that only work on a self-hosted box are now hidden on the hosted platform, instead of being advertised there and returning 404.

  • Um editor de acesso e um agente ativo podem ter escopo redefinido

    The MCP consent screen, personal-access-token scoping and member grants were three separate editors and are now one. A connected agent's access can be edited in place from Settings — narrowed, or widened (widening to unscoped asks first) — and applies on its next request, with no disconnect-and-reconsent.

  • Os escopos que você sempre pode aplicar agora podem ser concedidos

    Several platform areas (jobs, notifications, analytics, settings, updates, cloud) could be checked for but never handed out, so there was no middle ground between "deploy only" and "the whole account"; they're grantable now, with billing and audit marked sensitive. Listing a collection honors a wildcard grant too — a token allowed to read a server by id no longer 404s when it tries to enumerate them.

Área de trabalho

  • As implantações locais são protegidas por um explícito "em breve"

    Desktop mode is built to control remote servers; running the workload on the desktop itself isn't enabled yet, and the UI now says that once, in one place, instead of offering a target that fails later.

  • Endurecimento da casca e um atualizador mais seguro

    See Security above.

Documentos e site

  • Páginas novas e reescritas

    "The edge" guide, the openship edge referência de comando, solução de problemas de canal de host, um guia "Adicionar um aplicativo" reescrito e referência de catálogo de aplicativos, além de notas sobre instalação, atualização e registros/monitoramento.

  • Documentos recebem visualizações sociais

    Generated OG images per page.

  • Uma página de changelog melhor

    Entries collapse to headlines and expand to detail, with controls to expand or filter, driven by this file.

Correções

  • O login com autenticação zero não altera um navegador remoto para sempre

    An instance with no sign-in form grants its session only to a browser on the same machine, so bouncing a remote one was guaranteed to fail, leaving a spinner and then either a connection error for a host that isn't yours or an endless redirect. The page now names the cause.

  • A remoção da retenção de correio respeita os backups de correio

    Pruning no longer considers a mail engine backup an ordinary project artifact.

  • Um contêiner migrado ingressa na rede em que está roteado

    A same-server migration attached a container that was never published, leaving it unreachable behind a verified domain.

  • Cancelar uma compilação interrompe todos os caminhos de compilação

    Cancellation reached some paths and not others, so a cancelled build could still be deployed: remote Docker builds kept running, and the static extract went on to publish the output of a build you had already stopped. A cancelled deployment is now terminal.

  • Uma reimplantação de composição autônoma não assume o controle da versão ativa

    A redeploy where every service was carried forward unchanged settled without advancing, so it no longer displaces the release that is actually running.

  • Uma verificação de integridade armazenada sobrevive ao formulário de configurações

    Editing project settings preserved the healthcheck test rather than dropping it, and a NONE a matriz de teste é lida como desabilitada em vez de um comando.

  • Um despejo finalizado para de pendurar

    Exec-stream sinks close on EOF, and the upload stall bound matches the producer's idle budget, so a completed backup can't wait forever on a stream that already ended.

  • Um projeto de arquivo Dockernão precisa de comando

    Projects that rely on the image's own entrypoint deploy without one.

  • Cada nova string é traduzida

    The release's new copy landed across all shipped languages, with the parity test extended to the new namespaces.

7 de ago.2026v0.6.1RecursosCorreçõesBreaking52 atualizações

Um grande lançamento. Ele adiciona um plano de rede completo de serviço a serviço, monitoramento 24 horas da integridade do contêiner e análises reais com geografia do visitante e histórico de uso - além de um mecanismo de correio em contêiner independente, uma visão de infraestrutura de toda a frota com atualizações com um clique, um log de auditoria que você pode filtrar e atribuir, alertas do Telegram e um instalador baseado em Node que retira o último da classe de travamento Bun.

Rede serviço a serviço

  • Qualquer projeto agora pode ser conectado a outro pela rede interna

    Every project (a plain single-app, a raw Compose stack, a monorepo, or an imported one) now shows a Connection card with its internal address (http://<alias>:<port>) e pode ser escolhido como uma fonte "Usar em um projeto". Anteriormente, apenas aplicativos de catálogo com um bloco de conexão declarado, ou pilhas Compose de vários serviços, eram acessíveis internamente; um projeto de aplicativo único não tinha nenhum endereço interno. A acessibilidade no mesmo limite é automática e o cruzamento de um limite permanece explícito – um alias só se torna acessível quando você conecta um consumidor à rede. Somente auto-hospedado e ignorado para sites estáticos (sem porta de escuta) e aplicativos hospedados na nuvem (que se vinculam ao Público).

  • Dê a um serviço um nome de host interno personalizado

    A service can carry a custom east-west DNS alias that resolves alongside its default name, set from the service's Settings tab and available to single-app, Compose, and monorepo services alike. Openship normalizes it to a valid hostname and rejects one that collides with another service on the same project network, and the internal-address card shows the alias its containers actually answer to. Self-hosted only.

  • Um editor de configurações de serviço mais claro

    The service Settings tab groups fields into labelled sections and swaps free-text boxes for structured editors: ports and volumes are entered as chips (with per-item limits enforced as you type) and depends-on is a picker of the project's other services. The image and build-from-source fields are shown together — fill either, and a build context wins over a stale image — instead of an image/build mode toggle.

Integridade e incidentes do contêiner

  • OpenShip monitora seus contêineres 24 horas por dia, não apenas durante a implantação

    Until now a container was health-checked exactly once, during the ~15s window right after a deploy, and then never looked at again unless a human was staring at the project page. A new health watch polls every server's Docker daemon once a minute (and reacts within about 10 seconds when Docker itself reports a container dying or restarting), so an app that falls over or drops into a crash loop at 3am raises an alert through your existing notification channels instead of waiting for a user to complain. Self-hosted only.

  • Contêineres quebrados chamam você uma vez, não a cada minuto

    A container stuck in a restart loop is broken on every poll, so a naive watcher would fire 60 alerts an hour about one fault. Instead each fault becomes a single incident: one message when it opens, one more only if it gets strictly worse (unhealthy → crash looping → down), and one all-clear that tells you how long it was down. A fault must be observed twice before it notifies, and an in-flight deploy, an operator's own docker stop, ou um projeto desativado nunca dispara um alarme falso.

  • Um servidor inacessível é um alerta, não um por aplicativo nele

    When a box's Docker daemon stops answering, Openship opens a single server-level incident that names how many projects it can no longer monitor, and freezes those projects' health rather than falsely marking them recovered. The record is durable, so a box that has been down for days does not re-page every time the control plane restarts.

  • Uma guia Saúde em cada projeto, com 30 dias de histórico de incidentes

    Each project gets a Health tab listing its currently open incidents plus a rolling 30-day history of resolved ones with downtime durations. It also states whether monitoring is actually switched on (an operator toggle in the Jobs module) and surfaces the server's own outage when a box is unreachable, so an empty tab is never misread as "all good." Self-hosted only.

Análise e uso de recursos

  • Veja de onde vêm seus visitantes

    The Monitoring tab draws a per-country choropleth of visitors alongside a ranked list, and animates real-time request ripples fed by the same stream the Logs tab tails, so you can watch where requests are landing right now. It works the same way self-hosted and on Cloud, and it can tell "no visitors yet" apart from "geo lookups aren't set up on this box," which used to render identically as an empty map. On a multi-domain project the whole view scopes to a chosen domain.

  • As contagens de visitantes agora são números reais, não contagens de solicitações

    The dashboard's visitor figure was a request count relabelled "unique IPs," so five page views from one browser counted as five people. It's now a genuine count of distinct visitors, deduplicated at the edge with a per-day salted hash that never stores an address or a per-visitor row — the number is honest while still collecting no behavioural data on your end users.

  • Principais caminhos e códigos de resposta que contêm dados reais por trás deles

    The Top Paths table was hardcoded empty and error rate couldn't be answered from anything saved. Both are real now: the daily rollup records normalized request paths (query strings stripped, ids collapsed, so tokens never become keys) and the full status-code mix, and a new card expands each 2xx/3xx/4xx/5xx class to the exact codes beneath it. On self-hosted, per-path aggregation is opt-in per project (a toggle, default off, including on existing projects) because it adds measurable work to every request the edge handles; on Cloud paths are aggregated automatically. Every other analytics dimension is unchanged.

  • O histórico de uso é mantido, para que você possa ver o que levou à falha

    CPU, memory and network usage used to exist only as a live stream that vanished when you closed the tab, so "was memory climbing before it got OOM-killed at 3am" had no answer. Usage is now sampled on a schedule into 5-minute buckets and charted over time, per service. A Compose project reports its whole stack with a per-service breakdown and an All/service scope picker instead of just the one container the primary service owned; a static site (nothing to measure) now says so plainly instead of showing four zeroed metrics. Self-hosted Docker deployments; bare non-Docker deployments report zero network, since per-process accounting isn't available there.

  • Domínios ocupados mantêm suas análises

    A domain pushing more than about 2 GB in a single minute (roughly 286 Mbps — routine for video or large downloads) used to overflow a 32-bit byte counter and kill the analytics scrape for that entire domain, so the busiest sites were precisely the ones with no analytics. The bandwidth counters are now 64-bit and collection keeps up. Self-hosted edge.

  • A análise não desaparece mais silenciosamente quando ninguém está olhando

    Traffic analytics live in the edge's memory under a TTL and were only flushed to the database when someone opened a project's Analytics tab, so a project nobody viewed for a day lost its per-minute data. A background scrape job now persists every server's analytics on a schedule whether or not anyone is watching, collecting a whole server in one pass instead of a separate memory scan per domain.

  • As dicas de ferramentas do gráfico podem ser lidas em todos os temas

    Tooltips were effectively transparent in the dark themes (plot lines showed straight through the text) and on light cards the hover marker rendered as a stray white block below the tooltip. Both are fixed with a shared tooltip style reused across the monitoring and billing charts.

Borda e proxy reverso

  • Ajuste o proxy reverso por projeto

    A project's Routing settings now expose a full set of proxy tunables instead of a handful: raise or entirely remove the upload size limit, set connect/read/send/keepalive timeouts, control response buffering and gzip level, turn on HTTP/2, tighten request-header limits, and verify TLS to the upstream — each value validated before it reaches the generated nginx config and labelled with its own directive name. On self-hosted it also reads back what the edge is actually serving next to what you saved, flags any drift in colour, and offers a one-click adopt, so a hand-edited vhost or a value the sanitizer dropped can't quietly disagree with your settings. Self-hosted only.

  • A análise por país e as regras do país funcionam na borda conteinerizada

    The containerized edge shipped without the MaxMind geo library or its country database, so every lookup returned nothing: no per-country analytics were recorded, and country-based route rules failed closed (a single-country ban silently blocked all traffic). The library and a GeoLite2 database — parsed and validated before shipping — are now baked into the edge image, so geo works from a box's first install with no runtime download.

  • Corrija a identidade do visitante atrás de Cloudflare ou de um balanceador de carga

    Behind a proxy the edge treated the proxy as the client, which broke four things at once: visitor country resolved to the PoP, distinct-visitor counts collapsed, per-IP rate limits put the whole planet in one bucket, and IP bans banned a PoP instead of a visitor. The edge now recovers the real client address from CF-Connecting-IP, confiando apenas nos intervalos publicados de Cloudflare como ponto de conexão.

  • As regras por rota atingem o limite mesmo quando não estão no loopback da API

    Pushing a project's route rules to a local edge now goes through the same resolved edge-management path as the rest of Openship instead of assuming the edge lives on the API host's own loopback. On setups where it doesn't — such as the containerized edge — rate-limit, ban, and country rules now actually take effect.

  • A pílula "Edge ready" corresponde ao estado real do servidor

    Edge readiness is now read from whether Openship's edge container is actually running, the same fact the Infrastructure tab and System Health use. Before, a leftover bare-host OpenResty install could make the pill claim "ready" while the server tab reported the edge as down.

Domínios personalizados e gratuitos

  • Grátis .opsh.io domínios só roteiam para um servidor cujo controle você comprovou

    Openship Cloud's shared edge now forwards a free subdomain to your server only after that server answers a challenge proving it owns the target, a proof that lasts 90 days and that Cloud re-checks about a week before it lapses. Openship prepares the box to answer the moment you set up its edge, so a free domain added later works without a redeploy, and a background sweep re-asserts, reads back over the server's own public address, and re-verifies anything expired — so a box left undeployed for months no longer silently loses its free URLs. A slug can't be pointed at someone else's box, and a server that can't yet answer is told why. Requires Openship Cloud.

  • Domínios gratuitos e personalizados agora funcionam em sites estáticos

    Adding a free .opsh.io domínio para um projeto estático usado para registrar nada no limite, então a URL passou para o curinga sem nenhuma origem por trás dele; editar o domínio de um projeto estático não gravou nenhum vhost até a próxima reimplantação. Ambos agora emitem uma rota real no instante em que você salva, servindo os arquivos construídos do projeto - o mesmo comportamento que os aplicativos proxy já tinham.

  • Um certificado que foi emitido, mas depois encontrou um obstáculo, não está mais perdido

    If an ACME order completed but a later step failed (the vhost rewrite, the reload, or the read-back), the domain stayed stuck in "provisioning" with no expiry recorded, which made it invisible to the renewal sweep — a valid certificate then sat on the edge and expired ~90 days later. Openship now re-reads the edge after a failed issuance and records a certificate that's actually present, so renewal stays scheduled.

  • Domínios personalizados inválidos são rejeitados na porta

    Setting a custom domain to something that isn't a public hostname (localhost, um IP simples, um único rótulo ou um valor com um caminho/porta/esquema) usado para retornar sucesso, criar uma linha de domínio pendente inoperante e até mesmo escrever um server_name localhost; vhost na borda compartilhada. Os caminhos de gravação agora validam nomes de host personalizados e recusam nomes inválidos, ao mesmo tempo em que permitem que um projeto que já contém um valor inválido seja editado e removido.

  • A edição de um domínio gratuito não mostra mais uma falsa "Ação necessária"

    A single edit could sync the same free subdomain to Cloud twice, and the two racing challenges reset each other's token, so the route worked but the project reported "Action Required" anyway. Callers that run their own managed-edge sync now suppress the duplicate, so each edit issues one challenge and the status reflects reality.

  • Redirecionamentos e limites de upload entram em vigor ao salvar

    Raising a route's upload limit or adjusting its timeouts now applies as soon as you save instead of waiting for the next redeploy, and a domain redirect is applied live to static-site domains too, not only to proxied apps.

E-mail

  • O Mail funciona como um mecanismo independente em vez de assumir o controle do seu servidor

    Setting up mail no longer installs iRedMail's daemons directly onto the host or reboots the box. Postfix, Dovecot, spam and virus filtering, and DKIM now run inside a single openship-mail contêiner com seu banco de dados vmail em um arquivo secundário Postgres, em rede de host para que o e-mail ainda veja IPs reais do cliente e a borda permaneça fora do caminho de dados do e-mail. A configuração se resume a oito etapas cujos únicos pré-requisitos são Docker e a borda do openship, e cada parte do estado do correio (fila, maildirs, chaves DKIM, configuração) reside em montagens de ligação do host, portanto, a atualização é um pull-and-recreate que mantém seus dados. Somente auto-hospedado.

  • Mail usa a mesma borda e TLS que todo o resto

    Mail setup no longer stands up its own host OpenResty and certbot on the side. The certificate for mail.<domain> é emitido por meio da borda aberta compartilhada, o mesmo caminho que o TLS de qualquer outro domínio segue, e agora é registrado para renovação como qualquer outro domínio - um certificado de correio em uma borda conteinerizada (sem temporizador certbot de host) usado para simplesmente expirar aproximadamente 90 dias após a instalação, silenciosamente; uma renovação com falha agora gera uma notificação.

  • Servidores de e-mail configurados antes da conteinerização continuam funcionando

    The move to containers is topology-aware, so a server whose mail was installed the old way (system daemons, database on the host) still reports accurate component health and stays fully manageable: SQL queries, outbound SES/SMTP relay config, and daemon restarts all target the right engine. When the engine genuinely is stopped or was never installed, admin actions now return a clear message telling you to restart it or re-run setup instead of a bare 500 leaking a Docker "No such container" error.

Infraestrutura remota

  • Veja todas as bordas gerenciadas e contêineres de correio em um só lugar

    A new Infrastructure view lists each server's edge and mail container with the image version it's running against the version this release pins (for example edge 0.4.0 → 0.5.0), and flags which are behind, stopped, or missing. An attention rollup surfaces the ones that genuinely need hands — an edge that's down, or absent on a box that hosts projects — separately from the ones that merely have an update available. Self-hosted only.

  • Atualizar, reparar ou instalar um contêiner sem tocar no shell

    Update swaps a behind container onto the pinned image (rollback-guarded), Fix restarts a stopped one in place, and a server with no edge gets a one-click Install that runs the first- install path with 80/443 takeover consent. Each apply streams its pull/recreate/ verify progress and survives a dropped connection, and a fleet-wide Update all / Restart stopped does the same across every server at once. Self-hosted only.

  • Atualize automaticamente sua infraestrutura remota na atualização

    A new instance-wide toggle lets the control plane update every remote edge and mail container automatically when you upgrade Openship (its APP_VERSION avança), para que o infra da sua frota rastreie a versão que você está executando sem varredura manual. É do lado do servidor, por isso funciona também no desktop, diferente da atualização automática do próprio aplicativo de desktop e desativado por padrão. Somente auto-hospedado.

  • A detecção de desvio permanece atualizada por conta própria

    With auto-scan on (the default), opening the Infrastructure tab or the home page quietly runs one detect-only scan when the cached state is stale, throttled to about every 30 minutes per browser, so the attention dot reflects reality without pressing Scan. It only refreshes what's shown — it never applies an update, which stays the separate auto-update toggle. Self-hosted only.

  • Caixas legadas não são mais sinalizadas como quebradas

    A server converted to the containerized edge kept listing its leftover host OpenResty as a component with an Update button for a config nothing loads; those superseded host modules are now dropped from the view. And a legacy host-native mail engine (systemd Postfix/Dovecot) that was quietly delivering mail used to show up as "Stopped, container missing" — it's now labelled as not containerized rather than inventing a version. Self-hosted only.

Docker migração

  • Os sites migrados mantêm o limite de upload e os tempos limite sob os quais foram executados

    When you move or take over a Docker stack, the reverse-proxy tunables the source vhost declared (upload size limit, upstream read timeouts) are now carried onto the migrated project before the new edge vhost is rendered. Previously the site silently reverted to nginx's 1 MB / 60 s defaults at cutover, so the first large upload after a move failed with a 413 and nothing tied it back to the migration. Adoption is additive: a limit you set by hand always outranks a value inferred from the old box. Self-hosted only.

  • Adotar uma pilha não republica mais portas internas

    A compose service that published a container port on a random host port (a single-part ports: entrada, por ex. um banco de dados 5432 (a origem nunca foi verdadeiramente exposta) agora não é exposto durante a adoção, em vez de ser republicado no destino, para que uma migração não exponha desnecessariamente serviços internos ou colida com o que já contém uma porta de host. A porta ainda é mostrada no assistente para que você possa rotear até ela, e o tráfego entre serviços continua sendo resolvido por nome na rede compartilhada. Somente auto-hospedado.

  • O assistente informa quais env vars não foram transportados

    When adopting a foreign stack, environment variables that exactly match the image's baked-in defaults are dropped rather than imported as explicit config (the image still supplies them at runtime). The wizard now lists exactly which keys were skipped and why — common with Coolify/Nixpacks images that bake config as ENV layers — so you know what to re-enter if you later change the image.

  • Não há mais nomes de host fantasmas no assistente de importação

    The wizard used to invent a hostname from the project name whenever a step had no route chosen, labelling port fields, previewing monorepo sub-app hosts, and even wiring the "Visit Site" button to a host that would never exist. It now shows only hosts your config actually names, and hides "Visit Site" entirely when the deployment has no public domain.

Registro de auditoria

  • Veja exatamente o que seu assistente de IA mudou

    Every audit entry now records where the action came in from (the dashboard, an MCP client, the CLI, the API, a webhook, or the system itself), and you can filter the log down to a single source. Isolating MCP-driven activity finally answers "what did the AI assistant do," which was impossible before because an MCP write and a CLI write produced identical rows. Entries written before this release show as an honest "unknown" rather than being mislabelled.

  • Desative a auditoria e controle por quanto tempo ela será mantida

    Each organization can switch audit recording on or off and pick a retention window (7, 30, 90, 180 or 365 days). Turning recording off stops new entries but never touches the ones already written, and the act of disabling is itself logged first, so the trail always explains why it went quiet. The switch is per-organization, so on a shared cloud instance one tenant can't disable everyone's audit log.

  • Uma verdadeira barra de filtros sobre o log

    You can narrow by category, actor, date range and free-text search, with a live count on every category tab. Search resolves project, server and domain names, so typing a name like "api-gateway" turns up entries that only ever stored an opaque id, and rows now display the human name of the affected resource, resolved server-side in one batched lookup per page.

  • Paginação do log não ignora mais ou repete linhas

    Entries that share a timestamp are now ordered by a stable tiebreaker, so scrolling through pages no longer reshuffles them; two entries created in the same instant could previously appear twice or vanish between pages.

Notificações

  • Envie alertas para o Telegram

    Telegram joins email, Slack, Discord, and Teams as a notification channel: point a BotFather bot at a chat, group, or forum topic and Openship delivers your deploy, health, and job alerts there. The bot token is stored encrypted, and the channel list shows which bot does the sending.

  • As configurações de notificação auto-hospedadas eliminam os botões que nunca podem ser acionados

    On a self-hosted box the billing notification categories are fed by the SaaS billing system, so they were switches that could never send anything. They no longer appear, and the remaining categories are organized into tabbed groups in Settings.

Instalar e embalar

  • OpenShip agora instala e atualiza no Node, nunca um Bun global

    O curl | sh e os instaladores do PowerShell baixam uma carga útil CLI independente e verificada pelo sha256 que é executada no Node: eles usam o Node 22+ do sistema se você tiver um e, caso contrário, vendem um Node 22 oficial de nodejs.org para ~/.openship, e eles migrarão você silenciosamente de qualquer instalação anterior do Global-Bun sem tocar no seu próprio Bun. openship update segue o mesmo caminho - baixe novamente a carga verificada, atualize o tempo de execução primeiro - para que uma atualização que aumente o piso do nó se cure em vez de quebrar. Isso retira a classe de travamento Bun-vs-ssh2 que poderia eliminar operações SSH remotas.

  • O servidor de e-mail é enviado como imagem oficial

    Openship's official multi-arch (amd64 + arm64) image set, built and published to GHCR and Docker Hub each release, now includes openship-mail junto com a API, o painel e as imagens de borda, para que um mecanismo de e-mail auto-hospedado não precise mais ser criado a partir do código-fonte.

  • openship up agora funciona em Docker sem raiz em vez de falhar criptograficamente

    Bringing up the compose stack on a rootless daemon used to abort the install with Docker's opaque "error while creating mount source path … permission denied," because a rootless daemon can't create the edge's bind-mount directories under root-owned paths. The CLI now creates those directories itself and, when it can't, prints the exact one-time sudo mkdir/chown comandos para executar (#372).

Implantações e composição

  • Uma implantação em funcionamento nunca é registrada como falha

    Build output that carried a raw NUL byte or a broken Unicode character (as a failed docker exec faz quando ele derrama seu fluxo multiplexado, cabeçalhos de quadro e tudo) fez com que a gravação do log falhasse e OpenShip interpretou incorretamente a gravação rejeitada como a própria implantação falhando: uma implantação ativa e em execução foi marcada como falha e seus contêineres foram destruídos, enquanto a visualização de implantação permaneceu presa em "Implantação". Os logs de build armazenados agora são higienizados e têm tamanho limitado, a gravação do resultado elimina qualquer log ou blob de erro Postgres recusa em vez de perder o status, e o evento de terminal que fecha a transmissão ao vivo sempre é acionado.

  • Seu URL de acesso e portas de domínio personalizado sobrevivem a uma reimplantação

    A project's deploy target is now stored durably on the project itself (a new server_id coluna) em vez de viver apenas nos metadados voláteis da implantação mais recente. Antes, um instantâneo novo ou parcial poderia perder essa ligação, regredir silenciosamente o projeto para uma implantação local, retirar as portas de seus domínios personalizados (um 502) e redefinir a URL de acesso para localhost:3000; os projetos existentes hospedados no servidor são preenchidos, portanto, isso não pode prejudicá-los na próxima reimplantação. Um domínio personalizado verificado também é preservado em vez de excluído ou apagado, mesmo quando o conjunto de endpoints de uma implantação o omite. Somente auto-hospedado.

  • Uma instalação de domínio gratuito agora tem um destino de implantação

    A box set up with a free .opsh.io O domínio poderia terminar a integração sem servidores listados e sem nada para implantar, porque o registro da linha local "Este servidor" dependia de uma etapa de inicialização cujo caminho nunca é executado. A caixa agora materializa sua própria linha de destino de implantação quando os servidores são listados pela primeira vez, quando ela se conecta a OpenShip Cloud e na redefinição do administrador. Anexando um grátis .opsh.io domínio para um projeto posteriormente não precisa mais ser reimplantado primeiro, já que cada implantação agora prepara a caixa para responder à verificação de propriedade. Somente auto-hospedado.

  • Os domínios de serviço respeitam seu limite de upload e configurações de proxy

    A compose service's own domain ignored the project's reverse-proxy tuning, so the main app would accept a 50 MB upload while the same project's service domain rejected it at nginx's 1 MB default with a 413. Those settings now apply to every domain a project writes — per-service, static, single-domain composites, path fan-out, and single-app native deploys. Self-hosted only.

  • URLs de serviço de aplicativo de catálogo são resolvidos por porta e nunca ficam em branco

    Apps that route one container port to a domain and leave another port-only (Convex, for one) used to get an empty or self-referential origin injected (CONVEX_SITE_ORIGIN="", ou um 127.0.0.1 que dentro de um contêiner aponta para o próprio contêiner). Cada porta agora é resolvida de forma independente, um serviço somente de porta retorna ao real alcançável da caixa http://host:port, e um {{publicUrl:…}} o token que ainda não pode ser resolvido é deixado sem definição — portanto, o padrão da própria imagem se aplica — com um aviso alto no log de implantação em vez de um espaço em branco silencioso.

  • O aviso de roteamento informa quando a borda é o problema

    When a deploy succeeds but its domains aren't being served, the post-deploy warning now checks why: if the edge container itself is down it tells you to bring the edge back up, instead of sending you off to your DNS provider to debug routes that are actually fine. Self-hosted only.

Nota de atualização: esta versão supera as versões de borda fixada e imagem de correio. Em auto-hospedado, abra a nova visualização Infraestrutura para atualizar a borda de cada servidor e o contêiner de correio na imagem fixada — ou ative a atualização automática em toda a instância para que o plano de controle faça isso em cada atualização.

31 de jul.2026v0.5.0RecursosCorreções25 atualizações

A reversão é reconstruída para realmente restaurar uma versão, além de uma rodada de correções na integração do MCP e nos domínios personalizados.

Reverter

  • Reverta qualquer versão, em todos os projetos

    The Rollback action used to be greyed out on projects using the default settings, because nothing marked their releases as restorable. It's now available on every successful release, and it is a single action: Openship reuses the release's retained image when it's still on the server (seconds, no rebuild) and rebuilds that release's commit when it isn't. It can no longer dead-end — the "Redeploy this commit" fallback button is gone because the one action already covers it, and the confirmation tells you which of the two you're about to get.

  • Uma versão restaurada volta completa

    A rollback now runs the same deploy pipeline a normal deploy does, replaying that release's own frozen configuration and environment variables. Previously it hand-assembled a bare container, which meant a "successful" rollback could come back with no environment variables, no published port (a 502 behind your domain) and its volumes detached. Restores now get the health check, the crash-loop watch, routing, logs and a build log of their own, exactly like any other deploy.

  • Compose stacks rollback por serviço

    Only services whose image is missing are rebuilt; a service the deploy never touched keeps running on the image it already has, so rolling back your app code doesn't bounce your database.

  • Sites estáticos revertem seus arquivos

    A static release's artifact is its built files on disk, not an image, so restoring one copies that version's files back into place (hard-linked, so it costs almost no extra disk) and re-points the edge at them. No image, no rebuild. A static rollback previously tried — and failed — to restart a directory as if it were a process.

  • A restauração nunca interrompe a versão em que você está

    A restore reuses its source release's image, so two releases can share one. Retention now knows that and will not delete an image another retained release still needs.

  • O histórico de reversão se dimensiona para o disco

    How many releases stay restorable is now measured from free space on the deploy host and your project's real image size (a quarter of what's free, between 2 and 20 releases), instead of a fixed 5. You can still pin an exact number; clearing the field returns it to automatic.

  • As configurações foram movidas para perto dos backups

    Rollback retention now lives in the project's Backup tab, and in the deploy wizard's target panel where you pick the server, with the measured snapshot size and free disk shown inline. Pinning a release to keep it restorable indefinitely is unchanged.

  • Defina a retenção enquanto você ainda escolhe o servidor

    The wizard's rollback controls are editable on a first deploy too, and the choice is applied when the project is created. They used to render read-only until the project existed, which was the one moment you were actually looking at them. The card also names what a retained version é em seu projeto - arquivos criados para um site estático, caso contrário, imagens - em vez de falar sobre imagens de qualquer maneira.

  • O painel Avançado do assistente diz o que há nele

    It listed only the build location while hiding the rollback window and clone location; it now names each section it contains. The summary chips next to the target (Static, Sandboxed, tier) lost their coloured pill backgrounds and read as plain text, with the one that matters — an unsandboxed "direct on host" runtime — still called out in colour.

  • A inversão da configuração de retenção se aplica a versões existentes

    It used to be frozen onto each deployment as it was created, so turning on instant rollback did nothing for anything already deployed.

Correções encontradas durante a reconstrução da reversão

  • Versões mais antigas não puderam ser implantadas ou restauradas

    A release whose configuration snapshot predated the "production paths" setting crashed the deploy pipeline outright. This affected plain redeploys too, not just rollback.

  • Uma restauração não é mais recusada por falta de configurações de compilação

    A release that reuses an existing image needs no install or start command, but pre-deploy checks demanded them. Adding a required setting would otherwise have made every older release un-restorable.

  • Projetos somente de imagem de registro podem ser implantados novamente

    A stack adopted from a Docker migration has no git repository and needs none, but deploys were refused for not having one.

  • As implantações do Compose registram qual serviço executou qual imagem

    Six of the nine places that write per-service deployment records left the service name blank, so a later rollback couldn't tell services apart and rebuilt the whole stack.

  • Um campo de histórico de reversão limpo não significa mais "não manter nada"

    An empty value now falls back to the default instead of purging every restorable release.

  • Docker fora de Docker área de trabalho acessível

    Local deploys honor DOCKER_HOST (e um caminho de soquete explícito) em vez de assumir /var/run/docker.sock, então Colima, Rancher Desktop, Podman e Docker sem raiz funcionam.

Nota de atualização: esta versão descarta um não utilizado artifact_retained_at coluna da tabela de implantação por serviço. Nada leu ou escreveu.

MCP

  • Fluxos de implantação guiados

    The MCP server now ships a prompt catalog (deploy-from-git, deploy-a-folder, install-catalog-app, e uma visão geral da orientação) para que um cliente de IA siga a sequência correta de ferramentas em vez de fazer engenharia reversa a partir de uma lista simples. Suas ferramentas de gravação agora carregam corpos de solicitação digitados de ponta a ponta (projetos, implantações, domínios, webhooks, notificações, conexões, aplicativos) e cada prompt aponta para github.com/oblien/openship/issues quando um cliente encontra um bug na plataforma.

  • Os tokens com escopo listam as ferramentas certas

    A token granted a single GitHub repo (or the "create your own projects" scope) now correctly advertises the tools it can actually call. Previously the per-repo GitHub tools and the project create/list tools were filtered out of tools/list, portanto, um token com escopo definido não viu nada com que trabalhar.

Domínios personalizados

  • www é o seu próprio domínio, não um anexo do seu

    "Include www" always created a second hostname, but the pieces around it still treated the pair as one thing. Renewing SSL for a domain issued the www certificado dentro da mesma operação, sem proteção: um www que não foi apontado para o servidor ainda falhou depois o ápice já havia sido bem-sucedido e o ápice foi relatado como quebrado. Adicionar um domínio com a opção ativada também mostrou apenas o registro DNS do apex, portanto www nunca foi resolvido, seu certificado nunca pôde ser emitido e cada implantação tentou novamente um nome de host que havia sido configurado para falhar. Ambos os nomes de host agora obtêm seu próprio registro DNS, seu próprio botão Verificar, seu próprio certificado – e sua própria falha.

  • Redirecionar um domínio para outro

    Any domain can now answer a 301 (or 302) to another domain of the same project, set on the domain's card. www usa-o por padrão (www.example.com → example.com), e a direção é sua para virar ou desligar. As movimentações de domínio antigo para novo domínio funcionam da mesma maneira. O caminho e a string de consulta são preservados, o host de redirecionamento ainda obtém seu próprio certificado e um destino fora do projeto — ou um redirecionamento que faria um loop — é recusado.

  • Verify mantém o log quando falha

    The verify modal streamed certbot's output and then, on any failure, replaced the whole console with one line: "the connection closed before the operation reported a result — check the domain's status." The actual reason was discarded. The log now stays on screen in every outcome, with Copy log and Try again next to it. And if the connection really does drop, Openship reads the domain's state back and tells you what happened instead of asking you to go and look.

  • Uma execução concluída para de se reportar como falha

    A keep-alive ping could race the final event of any live-log stream (verify, edge setup, deploys) and win, so the browser never received the result of an operation the server had already completed. Stream writes are serialized now, and a result that has arrived can no longer be overwritten by the connection closing behind it.

  • Dois domínios em um servidor não brigam mais por certificados

    Certificate issuance is serialized per server, not just per hostname. www tornou dois domínios pendentes o caso normal, e uma verificação manual poderia colidir com a nova tentativa em segundo plano trabalhando no irmão: ambos executaram o certbot, ambos queriam a mesma porta de desafio e um morreu com um erro que parecia um problema de DNS.

  • O registro A mostra o IP do seu servidor

    On a self-hosted install the pre-deploy DNS panel now fills the A record's value with the server's public address (detected once when the server is registered) instead of leaving it blank.

  • Orientação correta de DNS auto-hospedado

    The panel no longer tells you to add a TXT record on a self-hosted box; there isn't one — HTTPS is issued automatically on the first deploy. The DNS modal is also lighter and on-theme, and the "Include www" switch now sits below the domain field so it no longer shifts the input as you type.

28 de jul.2026v0.4.7RecursosCorreções7 atualizações

A história de auto-hospedagem da CLI foi finalizada, as migrações remotas Docker tornaram-se confiáveis e um lote de correções chega ao plano de controle para uma versão mais estável.

Interface de linha de comando

  • Uma instalação concluída abre o painel de controle, não o assistente de configuração

    Bare openship (e a fonte openship-dev) agora reconhece uma instalação do Docker Compose (o padrão é Linux). A nova execução após a configuração gerencia a pilha em execução, em vez de orientar você pelo nome/e-mail/domínio do zero novamente.

  • Iniciar / Parar / Reiniciar no painel de controle aciona a pilha real

    On a compose install these now run docker compose up -d / restart / down e leia o estado real da pilha, em vez de direcionar uma unidade systemd que nunca foi instalada (que relatou "parada" para uma pilha íntegra).

Migrações e remoto Docker

  • A ponte SSH → Docker não trava mais ou falha falsamente em um servidor íntegro

    Migrating from another platform (Coolify/Dokploy/Dokku) or adopting a running Docker host could stall the reachability check — or drop the request outright — under the Bun-hosted API, even against a perfectly healthy daemon. The bridge now starts reading the request socket immediately and verifies each forwarded channel actually carries data, falling back to docker system dial-stdio em uma nova conexão quando um canal abre morto. Contribuição de @jbermudez00 (#271).

Correio

  • A configuração do servidor de e-mail funciona no aplicativo de desktop

    The iRedMail engine is now shipped inside the packaged desktop app (and the CLI bundle) and located by an explicit path, fixing the Transfer iRedMail Engine … tar: could not chdir falha na instalação.

Correções

  • A conexão auto-hospedada GitHub prioriza o token

    A remote (VPS) instance pastes an access token inline in the Library, with no gh auth login dicas; o caminho gh CLI agora é apenas para desktop, ao qual pertence.

  • O assistente de implantação chega diretamente à configuração

    The deploy-target picker no longer flashes on entry. A sensible target is applied silently and stays one click away in the summary bar at the top.

  • O plano de controle para de listar um serviço fantasma

    The self-managed "Openship" project no longer shows a bogus public openship serviço (e seus perdidos openship-openship.opsh.io route) que não correspondia a nenhum contêiner e dizia "Parado" para sempre.

27 de jul.2026v0.4.0RecursosCorreçõesSegurança8 atualizações

Uma correção de segurança para a borda, migrações que se comportam como um projeto de repositório nativo e um lote de correções de roteamento/confiabilidade.

Segurança

  • Hosts HTTPS não roteados são rejeitados, não com serviço cruzado

    The edge now owns a 443 servidor padrão que recusa qualquer nome de host que não seja roteado (aquele que você removeu, nunca adicionou ou apenas apontou para o IP da caixa). Antes disso, tal solicitação chegou ao primeiro vhost carregado e foi atendida certificado e back-end de outro aplicativo. Aplica-se automaticamente na próxima implantação, tanto na borda vazia quanto na borda conteinerizada. Crítico – consulte o aviso no aplicativo.

Migrações

  • Um projeto migrado agora é um projeto de repositório nativo

    A migrated compose stack redeploys like any repo project: it reclones and reconstrói build: serviços e puxa image: uns, em vez de falhar em uma tag de construção congelada (404 no such image). A imagem em execução é reutilizada apenas uma vez, na transição.

  • Toda a composição é o plano de implantação

    The migrate screen lists every repo compose service, not just running containers, so a service with no container (e.g. redis, ou um aplicativo que não estava ativo) é construído/puxado e roteado como o resto, com seu ambiente e rota editáveis no cartão.

  • Bancos de dados reutilizados permanecem acessíveis

    A reused container is joined to the new project's network under its service-name alias, so a freshly-built app resolves postgres:5432 por nome, exatamente como uma implantação nativa.

  • Um serviço migrado informa o contêiner em que ele realmente é executado

    Service state is read live from the host and matched by identity (label → openship-<slug>-<svc> nome → ID rastreado → compor rótulos), então um contêiner OpenShip adotado no lugar (seus rótulos de janela de encaixe ainda nomeiam o projeto anterior) não mostram mais "Parado" enquanto atende o tráfego. O log de cada execução agora termina com o contêiner, o estado e a correspondência de cada serviço.

Correções

  • O estado do serviço nunca é adivinhado no banco de dados

    Start/Stop/Restart, logs, terminal, backup/restore and volume sizes resolve the container against the host first, so a redeploy that replaced it no longer leaves them failing with no such container - ou, em Iniciar, iniciar um duplicar contêiner ao lado daquele em execução. Um contêiner de loop de falha agora lê Reiniciando em vez de um "Em execução" verde e um host inacessível lê Desconhecido em vez de repetir o último status de implantação.

  • A remoção de uma rota nunca exige erroneamente OpenShip Cloud

    The free-domain gate classifies by hostname, so removing a custom-domain route (or any route) is no longer blocked by an unrelated free subdomain still in the set.

  • A exclusão de um serviço não pode travar

    Runtime teardown is time-bounded, so a slow or unreachable server no longer strands the delete before the record is removed.

22 de jul.2026v0.3.0RecursosCorreçõesSegurança13 atualizações

Construções nativas do Apple Silicon, compatibilidade imediata com configurações de implantação de outras plataformas e um lote de correções de auto-hospedagem e confiabilidade.

Transferências

  • Aplicativo de desktop nativo Apple Silicon (arm64)

    MacOS now ships separate braço64 e Intel x64 dmgs (ambos construídos e com soma de verificação SHA-256 no CI), para que os Apple Silicon Macs sejam executados nativamente em vez de no Rosetta. Windows (x64) e Linux (AppImage) permanecem inalterados.

Implantar · detecção de pilha

  • Implanta repositórios já configurados para outra plataforma, como estão

    The stack detector now reads railway.toml/railway.json e vercel.json (comandos de construção/instalação/inicialização/saída, estrutura e roteamento) e os dobra sobre sua própria detecção. Um repositório que já informa a Railway ou Vercel como compilá-lo é implantado da mesma forma aqui, sem reconfiguração. Cada fonte de configuração é executada por meio de um registro de analisador compartilhado (sem maiúsculas e minúsculas especiais por fonte).

  • openship.json

    An optional repo-root config to declare build, routing, env, and domains up front; it's authoritative over auto-detection and rides the same engine, for the repo root and each monorepo sub-app.

Auto-hospedagem

  • Implanta em seu próprio servidor por padrão

    A self-hosted instance targets the server it runs on, never Openship Cloud, unless you explicitly choose cloud.

  • As verificações de integridade funcionam quando o plano de controle está em contêineres

    The post-deploy probe reaches your app through the host gateway, so a containerized self-host no longer fail-reverts an otherwise-healthy deploy.

  • OpenResty é instalado em distros mais recentes

    The edge install no longer pins the APT repo to a codename that doesn't exist yet (e.g. Ubuntu 26.04), and self-heals a box already broken by the old pin.

Interface de linha de comando

  • openship stop na verdade para

    The service and its children are reaped by process group and any ports it held are swept, so a restart can't strand the old process on a new port.

Confiabilidade e correções

  • Corpos de solicitação JSON malformados agora retornam 400, não 500.
  • O caminho de saída estática da nuvem está confinado

    The Pages output path resolves through one shared, sandboxed resolver so a build can't escape its output dir.

  • Verificação de DNS de correio detecta registros DMARC duplicados.
  • Os metadados de descoberta do OAuth são veiculados corretamente atrás de um URL público.
  • Fluxos executivos SSH feche de forma limpa no tempo limite em vez de vazar.
  • Atrapalhou a implantação do Laravel dispositivo de teste fora de um vulnerável laravel/framework (CRLF email advisory)

    A fixture only, never a shipped dependency.

22 de jul.2026v0.2.2RecursosCorreções12 atualizações

Aplicativos e trabalhos crescem, um servidor auto-hospedado agora pode se comunicar com GitHub por conta própria, os backups ganham um lar real e um lote de correções de confiabilidade de exclusão/login/banco de dados.

Aplicativos

  • Configurações do aplicativo do dia 2

    Installed apps now expose a curated settings surface (schema-driven) so you can change an app's real config after install without digging through raw env. Edits go through a safe env-merge and tell you whether a full redeploy (vs a quick restart-apply) is needed.

  • Assistente de instalação limpa por aplicativo

    Clicking a catalog app opens a focused, business-only setup that creates the project on confirm; the technical deploy wizard is now the "Advanced" path (no more orphaned draft projects from a half-finished install).

  • OpenShip Mail é um aplicativo de primeira classe

    It appears in the catalog alongside Convex and n8n and hands off to the mail wizard. The rest of the catalog shows as Em breve (esmaecido, não instalável) para esta versão.

Empregos

  • Backups automatizados aparecem em Jobs

    (Read-only) — backup schedules run on the same job runner as everything else (zero duplication), so their next/last run sits right next to your system and custom jobs.

Servidores · GitHub

  • Conecte GitHub em um servidor

    Each self-hosted server now authenticates to GitHub on its own, from a dedicated GitHub guia: faça login com um código de dispositivo (como gh), cole um token, gere uma chave SSH para adicionar à sua conta ou use somente leitura por repositório registrado automaticamente implantar chaves. As credenciais são armazenadas criptografadas e exatamente o mesmo painel de conexão é reutilizado dentro do fluxo de implantação, portanto, uma credencial ausente pode ser corrigida com um clique no meio da implantação. Os clones de repositório privado agora funcionam sem sua área de trabalho online.

Cópias de segurança

  • Backups redesenhados

    Per-destination storage stats, a sticky status rail, and clickable rows that open a per-destination detail page showing exactly which projects and services back up there.

Nuvem

  • Limite de projeto por usuário

    Openship Cloud enforces a hard cap on projects per user (env CLOUD_MAX_PROJECTS_PER_USER, padrão 2), tanto na criação quanto no upload/garantia da pasta. Auto-hospedado é ilimitado.

Confiabilidade e polimento

  • As exclusões nunca ficam presas

    Project deletion shows a real Excluindo estado, e quando a desmontagem da fonte não pode ser concluída, você obtém uma limpeza "Excluir do armazenamento" opção que elimina o registro imediatamente (os recursos restantes são recuperados posteriormente pelo GC). A exclusão atômica do tipo tudo ou nada permanece o padrão.

  • Correção de login na área de trabalho

    The login redirect now lands on the same loopback host the session cookie was minted on (localhost ⇄ 127.0.0.1), para que o painel não abra mais sem cookies e retorne para /login.

  • Inicialização de banco de dados incorporado

    No more false "locked by a different machine" on your own box when the machine-id probe is momentarily flaky; the cross-machine guard now only fires on a genuinely different, stable machine id.

  • Tema mais calmo e consistente

    Status colors (success / warning / danger / info) are unified semantic tokens across the whole dashboard, and the dim theme's greens and reds are tuned for comfortable contrast.

  • Servers empty state refreshed

    Clearer illustration, a Ver documentos ação e um ícone distinto por bloco "o que é configurado".

20 de jul.2026v0.2.0RecursosCorreções11 atualizações

Um grande recurso + lançamento de proteção em todo o fluxo de implantação, catálogo de aplicativos, roteamento, servidores, trabalhos e cadeia de ferramentas de construção.

Implantar

  • Redesenhado "Onde você deseja implantar?" step

    Unified page-style header with the Continuar ação alinhada à coluna de configuração e uma seletor de servidor recolhido e pesquisável (com um "Adicione seu próprio servidor" embutido).

  • Correção do conjunto de ferramentas do gerenciador de pacotes

    Pnpm/yarn are now enabled via corepack em cada caminho de construção (nuvem, arquivo Docker gerado, host vazio, preparação do espaço de trabalho monorepo, construção local na nuvem). Correções pnpm: not found na implantação.

Aplicativos

  • Catálogo de aplicativos pesquisável e com guias de categoria com um clique

    , Expanded to 15 production-ready self-hosted apps: Convex, n8n, Ghost, Directus, NocoDB, Metabase, Grafana, Gitea, code-server, Uptime Kuma, Vaultwarden, FreshRSS, Stirling PDF, IT-Tools, Excalidraw.

  • Cartão inicial "Apps" atualizado; os cartões de catálogo mostram logotipos reais de marcas.

Roteamento e domínios (fonte única de verdade)

  • Domínios personalizados ativados projetos baseados em serviços now flow through the same verify → DNS-records → SSL pipe as single-app domains

    A verifiable pending row is minted on add/create/edit, one canonical hostname normalizer is shared across storage/routing/domain-service, lookups are cross-tenant-safe, and certbot is gated on verification (no wasted Let's Encrypt attempts).

Servidores

  • Página de servidores redesenhada (guias, acessibilidade ao vivo, bandeiras de países).
  • Por servidor Git auth tab (token / SSH key / deploy keys) with a comfortable full-width card

    Connect-on-server credentials honored in preflight.

Empregos

  • Ganhos na página de empregos pesquisar + uma visão geral barra lateral do filtro de status (em execução/com falha/agendado/desativado), mostrado quando existem trabalhos personalizados.

Equipe e espaço de trabalho

  • Convidar membro

    Is only offered where it works (team orgs on a multi-user instance); single-user/personal instances are guided to migrate or create a team org instead of hitting a dead end.

Adicionar serviço

  • O OpenShip Cloud A guia de imagem mostra um CTA "Conectar a OpenShip Cloud" quando a instância não está vinculada e o alternador de origem tem um contraste mais claro.

Outro

  • Docker fluxo de migração, backups por projeto/serviço, verificações de conectividade unificadas, localização em árabe (RTL), página de roteiro de marketing e aprimoramento de janela de desktop (macOS inserção de semáforo).