Registro de cambios

¿Qué hay de nuevo?

Funciones, correcciones y mejoras enviadas en OpenShip.

31 lanzamientos
18 nov2026v1.0.1CaracterísticasCorrecciones13 actualizaciones

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 actualización

  • 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 nov2026v1.0.0CaracterísticasSeguridad42 actualizaciones

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 actualización

  • 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 nov2026v0.9.12CaracterísticasCorreccionesSeguridad46 actualizaciones

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.

Construir seguridad

  • Pase los entornos de compilación generados por Docker a través de secretos temporales de BuildKit en lugar de incrustar valores en Dockerarchivos o historial de imágenes. Enmascare los valores configurados en registros transmitidos, resúmenes de errores y notificaciones de fallas, incluida la salida dividida y multilínea. Conserve los límites de los trabajadores de la nube, las compilaciones de servidores paralelos y la limpieza después de la cancelación.
  • 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

  • Mantenga los servicios de imágenes a los que les faltan resúmenes de implementación visibles como no verificados. Inspeccione la imagen en ejecución a través del tiempo de ejecución de implementación existente para detectar etiquetas movidas, con lecturas limitadas y sin escrituras en filas de implementación. Mostrar el estado de actualización no disponible sin una insignia de actualización.
  • 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.

Dominios

  • 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 reescribir archivos de ruta perimetral sin cambios y repetir lecturas remotas durante un registro. Conserve el contenido y los permisos exactos de los archivos mientras conserva la validación de rutas, las recargas, la activación de certificados y la reversión transaccional.
  • 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, por lo que al eliminar un dominio se eliminan solo los registros propios 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.

correo

  • 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 actualización

  • 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 nov2026v0.9.11CaracterísticasCorreccionesSeguridad31 actualizaciones

Actualización recomendada para la recuperación del inicio de sesión en el escritorio, las conexiones del asistente, los análisis del repositorio y la confiabilidad de la implementación. Incluye todos los cambios fusionados en principal desde 0.9.10, con mejoras en la administración del correo y actualizaciones de seguridad en tiempo de ejecución más claras.

Asistentes y Escritorio

  • Inicio de sesión de Codex en instancias alojadas

    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.

  • Recuperación de cuenta de escritorio

    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 en macOS

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

  • Investigaciones y preguntas

    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.

  • Configuración del espacio de trabajo del asistente

    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.

Implementaciones, enrutamiento y seguridad

  • Redactar actualizaciones de comandos

    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.

  • Fallos en la aplicación del entorno

    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.

  • Cambios en el entorno 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.

  • Comportamiento estático 404

    Add an explicit SPA fallback setting to shared routing controls, the API and openship.json. Mantenga el respaldo de SPA habilitado de forma predeterminada; deshabilitarlo devuelve respuestas y usos 404 reales 404.html cuando esté disponible.

  • Componer inventario perimetral

    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.

  • Escaneos de repositorios privados

    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.

  • Importaciones de Docker 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.

  • Límites del host de la nube

    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.

  • Revisiones de seguridad condicionales

    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.

  • Conflictos de eliminación de bases de datos

    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 correo y aplicaciones.

  • Gestión de fallos2ban

    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.

  • Remitentes de alias directos

    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.

  • Configuración de escritura de aplicaciones

    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.

  • Verificación de actualización de seguridad

    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.

  • Imágenes de supabase

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

  • Preparación de RabbitMQ

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

Panel de control, facturación y documentación.

  • Restauración del 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.

  • Devoluciones de pago

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

  • Fallos de puerta de enlace

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

  • Análisis de la primera implementación

    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.

  • Redacción de inicio rápido

    Remove an abrupt line break in the setup description.

Notas de actualización

  • Actualice la API (incluidas todas las réplicas), el panel y la aplicación de escritorio juntos. Este parche no agrega ninguna nueva migración de base de datos del plano de control.
  • Si una instalación de escritorio anterior ya muestra solo Usuario local y no tiene una identidad autenticada guardada, use Volver a la configuración, Continuar con la nube e inicie sesión una vez. Esto preserva los datos existentes y registra al propietario para una futura recuperación.
  • Aplique cambios en la política del remitente de alias directo actualizando la imagen del motor de correo administrado y el plano de control. Las políticas personalizadas de SQL y de correo nativo del host siguen siendo administradas por el operador.
  • Vuelva a implementar un contenedor de sitio estático generado existente después de cambiar su configuración alternativa de SPA. Los sitios existentes conservan el comportamiento SPA hasta que se modifiquen explícitamente.
  • 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 nov2026v0.9.10CaracterísticasCorrecciones17 actualizaciones

Parche recomendado para fallas de inicio, recuperación y consentimiento de OAuth del asistente de nube en 0.9.9. También corrige implementaciones, enrutamientos y restauraciones, e incluye todos los cambios fusionados en principal desde 0.9.9, con aplicaciones de catálogo adicionales y sincronización opcional de calendario/contactos.

Nube, agentes y GitHub acciones

  • Recuperación del asistente en la nube

    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.

  • Devoluciones de llamada de consentimiento

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

  • Remitentes de correo electrónico de clientes

    Use the SMTP transport's authorized sender by default. Optional SMTP_SUPPORT_FROM y SMTP_BILLING_FROM los alias requieren permiso de envío en esa cuenta SMTP; Los alias permanecen fuera del relevo de la nube.

  • Precios de referencia

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

  • Acciones de solicitud de extracción

    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.

Implementaciones, dominios y copias de seguridad

  • Redactar reconfiguración

    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.

  • Implementaciones de imágenes almacenadas

    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.

  • Servicio www redirecciones

    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.

  • Reglas de ruta comodín

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

  • Seguridad de restauración de volumen

    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, correo y panel de control

  • Catálogo de aplicaciones

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

  • Enrutamiento de puertos de catálogo

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

  • Calendario y contactos

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

  • Detalles del error

    Add a copy action to error toasts for sharing diagnostics.

Notas de actualización

  • Actualice la API, el panel y todas las réplicas de API juntas. Este parche no agrega ninguna migración de base de datos nueva. Al actualizar desde una versión anterior a 0.9.9, siga también las notas de autenticación, conexión y actualización de SMTP de esa versión que aparecen a continuación.
  • Las restauraciones de volumen ahora requieren suficiente espacio temporal en el disco para preparar el archivo entrante antes de la extracción. La extracción después de la validación no es transaccional.
  • La verificación de la versión conserva la plantilla de redacción 0.9.9 publicada para que la puerta de actualización pruebe la instalación anterior real, incluidos los datos y rutas almacenados.
3 nov2026v0.9.9CaracterísticasCorreccionesSeguridad27 actualizaciones

Actualización de seguridad crítica que cubre autenticación, aprobaciones de conexión a la nube, aislamiento del servidor y entrega de correo electrónico cifrado. Incluye todos los cambios fusionados en principal desde 0.9.8, además de mejoras en implementación, facturación, asistente y panel.

Seguridad

  • Dependencias de autenticación

    Upgrade Better Auth and its plugins/adapters to 1.7.15 and the Hono Node adapter to 2.1.3. Address OAuth state, proxy, consent, rate-limit and static-path middleware advisories.

  • OAuth y compatibilidad de inicio de sesión

    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.

  • Aprobación de conexión a la nube

    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.

  • Identidad y límites del 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.

  • Aislamiento del 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 cifrado

    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 seguridad y mantenimiento del host.

  • Parches 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.

  • Mantenimiento observable

    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.

  • Preferencias de asesoramiento

    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.

Implementaciones y soporte de host

  • Redactar revisión de fuente

    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.

  • Construcciones de Git fijadas

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

  • Recuperación de borde

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

  • Anfitriones de la archifamilia

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

  • Datos GeoIP nuevos

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

  • Verificación de liberación

    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.

Nube, facturación y correo electrónico

  • Recuperación de pago

    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.

  • Escalado de aprovisionamiento

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

  • Correos electrónicos 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.

  • Guía del plan de nube

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

Asistentes y tablero

  • Descubrimiento de modelos conectados

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

  • Agentes en servidores Cloud pagos

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

  • Actividad de herramienta compacta

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

  • Dominios y referencias

    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 actualización

  • 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 cuentas antes de actualizar desde Better Auth 1.6.

  • Reemplazar autor container: referencias de espacios de nombres con service:<name> para un servicio en la misma pila. Los montajes de enlace de host están deshabilitados de forma predeterminada. Los operadores de instancias autohospedadas confiables pueden habilitar explícitamente OPENSHIP_ALLOW_HOST_BIND_MOUNTS=true; Los montajes de hosts en la nube siguen restringidos.
  • SMTP autenticado debe admitir TLS/STARTTLS verificado. Configure un punto final de envío compatible con TLS si el punto final anterior solo aceptaba la entrega de texto sin formato.
2 nov2026v0.9.8Características2 actualizaciones

Parche recomendado que restaura la creación de agentes con alcance y las automatizaciones respaldadas por agentes introducidas en 0.9.7.

  • Tiempo de ejecución del asistente compatible

    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.

  • Verificación de liberación

    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 nov2026v0.9.7CaracterísticasCorreccionesSeguridad18 actualizaciones

Actualización recomendada que presenta agentes de IA específicos, automatizaciones revisadas e integraciones de aplicaciones de chat. Incluye actualizaciones de seguridad de dependencias y todas las correcciones de 0.9.6.

  • personajes agentes

    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.

  • Monitoreo de atajos 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.

  • Transferencias de acciones del asistente

    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.

  • Espacio de trabajo de 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.

  • Edición de automatización

    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.

  • Investigar con 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 asistentes con alcance

    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.

  • Introducción a los 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.

  • Identidad 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.

  • Asistente de chat en vivo y 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.

  • Asistente de rebajas

    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.

  • Acceso al asistente y resultados de herramientas

    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.

  • Asistente en aplicaciones de chat

    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.

  • Automatizaciones asistentes

    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 de la aplicación de chat

    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; conservar las comprobaciones de permisos y realizar un seguimiento de los mensajes de respuesta individuales mediante reintentos.

  • Asistente de suscripción

    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.

  • Liberación de endurecimiento

    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.

  • Correcciones de implementación

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

1 nov2026v0.9.6CaracterísticasSeguridad34 actualizaciones

Actualización recomendada para recuperación de bases de datos, compilaciones y migraciones confiables, GitHub programación de acciones y actualizaciones de infraestructura administrada.

  • Recuperar PGlite después de un accidente de contenedor

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

  • Mantener legibles los errores de compilación de Docker

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

  • Mantenga las imágenes en tiempo de ejecución de monorepo alineadas con cada servicio

    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.

  • Agregar una base de manifiesto con ámbito 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).

  • Conservar registros activos 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).

  • Admite el inicio de sesión OIDC autohospedado y 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).

  • Mantenga vivas las sesiones de BuildKit

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

  • Mover imágenes con referencia a resumen 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).

  • Mover proyectos de una sola aplicación sin 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).

  • Mantener GitHub trabajos en cola en movimiento

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

  • Mantenga los diagnósticos de la nube disponibles durante el inicio de la 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 la salud después de reemplazar un contenedor de servicios

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

  • Escanee repositorios privados con credenciales 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).

  • Haga coincidir las sugerencias de los trabajadores de Laravel con las dependencias de producción

    Suggest the standard queue worker when Horizon is only in require-dev, coincidiendo con el Compositor predeterminado --no-dev instalar. Las opciones de roles explícitas siguen estando disponibles (#1171).

  • Mantenga los roles de tiempo de ejecución disponibles después de eliminar los servicios adjuntos

    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 falsas advertencias de roles obsoletos después de las implementaciones

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

  • OpenShip Gana

    Explain the Cloud affiliate program at /affiliates, con una división de comisiones interactiva, calendario de recompensas mensuales y anuales, orientación sobre pagos y una vista previa social dedicada. Etiquete la entrada de afiliado del panel Gane con un ícono de caja de regalo en la barra lateral izquierda.

  • Inicie los servicios de CockroachDB correctamente

    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 almacenamiento de escaneos lentos de caché de compilación

    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 imágenes de primeras implementaciones interrumpidas

    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 en la nube

    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.

  • Revisar las ediciones del entorno compartido

    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.

  • Aclarar el pago y las ganancias por referencias

    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 servicios administrados después de una actualización de imagen interrumpida

    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 los nombres de los recursos de permisos al inicio

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

  • Cargue el entorno de origen de la aplicación seleccionada

    Use the app folder's openship.json cuando esté presente y, de lo contrario, recurrirá a la raíz del repositorio, coincidiendo con la configuración que se muestra durante la instalación (#1480).

  • Autenticar submódulos privados con el token GitHub seleccionado

    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 reintentos de reinicio y asignaciones de puertos

    Retain configured on-failure límites de reintento y todos los enlaces publicados durante la creación del contenedor.

  • Mantenga las rutas perimetrales utilizables antes de una primera implementación

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

  • Mantenga intacta la identidad de la fuente de implementación

    Expose the selected revision as OPENSHIP_COMMIT_SHA, conserve los resúmenes de imágenes de Redacción transportados y aplique las rutas de implementación configuradas de manera consistente (n.° 1499, n.° 1475, n.° 1472).

  • Mostrar los comentarios correctos en el panel

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

  • Conservar el alcance del aviso de actualización

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

  • Alinear los precios de la nube con los períodos de facturación

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

  • Mantenga disponibles las versiones de escritorio

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

24 oct2026v0.9.5CaracterísticasCorreccionesSeguridad4 actualizaciones

Esta revisión restaura el inicio de Compose autohospedado después de la actualización 0.9.4.

  • Restaurar la preparación del panel y el inicio perimetral

    Bind the dashboard's Next.js server to 0.0.0.0 dentro de su contenedor para que la comprobación de estado del loopback pueda alcanzarlo. Aplique la misma configuración de enlace en los entornos Compose generados por CLI, autohospedados de referencia y desde el origen. Los puertos de host publicados conservan sus valores predeterminados de loopback existentes (#1461).

  • Pruebe la actualización completa del 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 los requisitos previos de reconstrucción del código fuente antes de una actualización de seguridad

    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 Redistribución de código abierto acción en lugar de ofrecer una actualización que fallará. La redistribución todavía utiliza los controles de implementación del proyecto existentes; la procedencia de la fuente, los pines de imágenes y la autorización del inquilino siguen vigentes (#1462).

  • Incluir la corrección de imagen del trabajador empaquetado.

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

Recuperación desde 0.9.4

correr openship update después de que se publique 0.9.5. La actualización recrea la API, el panel y el borde a través del proceso normal y preserva la base de datos existente, Redis y el almacenamiento de aplicaciones. Para una recuperación temporal en 0.9.4, configure HOSTNAME: "0.0.0.0" en Redactar del servicio de panel environment y correr docker compose up -d con el archivo Compose existente y el nombre del proyecto de esa instalación. Una ejecución CLI posterior regenera ese archivo; actualice a 0.9.5 para obtener una solución permanente.

24 oct2026v0.9.4CaracterísticasCorreccionesSeguridadBreaking80 actualizaciones

Esta versión agrega implementación a Docker clústeres Swarm existentes, replicación de bases de datos revisada, facturación anual de la nube, OpenShip administración de planes de soporte, avisos de seguridad en tiempo de ejecución, selección explícita de aplicaciones monorepo y protección con contraseña perimetral. La recuperación de la implementación, el almacenamiento persistente, las operaciones en la nube y el correo web reciben correcciones de confiabilidad y seguridad. Estas notas cubren los cambios desde 0.9.3.

Proyectos, repositorios y entorno

  • Elija qué aplicaciones monorepo implementar

    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.

  • Mantenga grandes listas de dominios manejables

    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.

  • Cree servicios adicionales desde el repositorio

    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 la topología de Compose durante la detección

    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.

  • Omitir envíos de espacios de trabajo no 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 y exclude para reglas explícitas; El análisis incierto mantiene la implementación en lugar de omitir silenciosamente los cambios.

  • Lea la revisión de la fuente solicitada de manera consistente

    Retries and explicit-commit deployments read Compose files and openship.json valores predeterminados de esa confirmación, en lugar de mezclar un pago anterior con la configuración más reciente de la rama.

  • Utilice una vista de entorno 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.

  • Aclarar cómo guardar y aplicar cambios de entorno.

    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.

  • Completa GitHub conexiones y 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 dónde se ejecutan realmente las compilaciones

    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.

Implementaciones, almacenamiento y recuperación.

  • Extraiga imágenes de trabajadores administrados de instalaciones empaquetadas

    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.

  • Hacer una copia de seguridad del almacenamiento de aplicaciones independientes

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

  • Utilice comandos y roles de lanzamiento con infraestructura adjunta

    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 las configuraciones de roles no admitidas

    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 las variables de composición requeridas 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.

  • Reintentar una compilación Docker completada

    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.

  • Actualizar imágenes en tiempo de ejecución 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.

  • Preserve the incumbent through eligible Compose replacements

    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.

  • Resolver la recuperación de enrutamiento interrumpido antes de admitir un reintento

    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.

  • Mantener los datos declarados de imágenes en todas las redespliegues

    Self-hosted and Desktop-managed Docker replacements reuse stable project-owned volumes for image VOLUME declaraciones. El almacenamiento heredado se recupera del contenedor saliente exacto verificado; la propiedad faltante o en conflicto detiene la implementación en lugar de adjuntar un huérfano no relacionado o comenzar con datos vacíos. Los montajes explícitos tienen prioridad y los volúmenes de propiedad retenidos aparecen en las vistas previas de eliminación.

  • Requerir persistencia de trabajo para implementaciones básicas

    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.

  • Iniciar un servicio con almacenamiento vacío sin borrar sus datos antiguos

    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.

  • Adaptar la retención de artefactos a la capacidad del 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.

  • Informar errores de restauración útiles

    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 actualizaciones del plano de control de Compose de manera confiable

    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.

  • Exponer el control de intercambio por servicio

    Opt into resources.swapDisabled para servicios Docker compatibles con un límite de memoria positivo y contabilidad de intercambio verificada. La validación compartida conserva el límite requerido en todas las ediciones de configuración. Esto cambia el servicio seleccionado, sin cambiar el intercambio en todo el host ni imponer nuevos límites de compilación.

  • Mantenga precisos los tiempos de implementación

    Build measurements survive terminal outcome writes, service timings include image preparation, and measurements freeze before cleanup. Unknown durations remain unknown, skipped builds display 0s, y los servicios intactos no adquieren medidas inventadas.

Clústeres, escalado y topología.

  • Implementar en un enjambre 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.

  • Revisar el escalado y la replicación de bases de datos.

    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.

  • Ver los miembros de la base de datos en la descripción general

    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.

  • Haga que la configuración y recuperación de K3 sean más 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.

Dominios, ingresos y certificados

  • Rutas autohospedadas y vistas previas nativas protegidas con contraseña

    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.

  • Finalizar el enrutamiento de servicios y 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.

  • Publicar dominios de solo redireccionamiento sin un puerto de destino

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

  • Deje las cargas de trabajo sin rutas independientes del borde

    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 pgAdmin sin un dominio 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.

  • Mantener disponibles las imágenes del catálogo

    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 comodín principales 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.

  • Reemplace los certificados manuales sin interrumpir el estado de renovación

    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.

  • Mejorar la recuperación y el diagnóstico de enrutamiento

    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.

  • Mantener la gestión de túneles en el menú de ruta.

    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.

Nube, facturación, monitorización y Acciones

  • Gestione la infraestructura propiedad del cliente desde la nube

    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.

  • Elija facturación en la nube mensual o anual

    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.

  • Actualizar la capacidad de la nube básica

    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 la selección de planes y la recuperación de pagos

    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.

  • Mantenga la facturación y el acceso de gestión coordinados

    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 conflictos de pago pendientes

    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 los flujos de uso de la nube

    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.

  • Recuperar terminales Cloud huérfanos de forma precisa

    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.

  • Reutilice las credenciales del proveedor con ámbito y conserve la orientación sobre limitación

    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 los errores de implementación relacionados con los 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.

  • Reflejar incidentes de tiempo de ejecución en el estado del proyecto.

    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 promedios de respuesta a partir de solicitudes.

    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 los ejecutores de acciones activos a través de fallas temporales 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.

  • Fusionar el historial de acciones de forma fiable

    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.

  • Mantenga un espacio de trabajo personal activo durante los cambios de cuenta

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

Seguridad y credenciales

  • Parchear el entorno de prueba DOM

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

  • Haga coincidir los avisos de seguridad en tiempo de ejecución con las cargas de trabajo implementadas

    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 parches revisados a través del proceso de implementación

    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.

  • Entregar avisos de seguridad a través de los canales de notificación 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.

  • Fijar tiempos de ejecución parcheados y herramientas de compilación

    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.

  • Mantenga las regresiones en tiempo de ejecución en las comprobaciones de lanzamiento

    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 es un alias de Bun.

  • Preservar la autoridad a través de los límites de los inquilinos y las terminales

    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.

  • Alcance de las conexiones de respaldo en el momento de su 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.

  • Otorgar capacidades de token más limitadas

    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.

  • Proteger compilaciones remotas Docker de destinos de metadatos

    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.

  • Verificar la publicación del trabajador antes de liberar paquetes dependientes

    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.

  • Mantenga aislados los servicios de vista previa deshabilitados

    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.

  • Separar cuotas de puntos finales de webhook detrás de direcciones compartidas

    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.

Escritorio, webmail, sitio web y documentación

  • Cree instaladores de Windows con tiempos de ejecución parcheados

    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 el inicio visible del escritorio sin conexión

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

  • Reparar asignaciones de hosts de correo web administrados más antiguos

    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.

  • Vista previa de archivos adjuntos de Office con representación 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.

  • Actualice las dependencias de correo y editor de manera 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.

  • Mantenga intactas las vistas previas sociales de las 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 estrellas en la navegación del sitio

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

  • Mejorar la orientación operativa

    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 actualización

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

  • Las compilaciones SSH rootful protegidas Docker requieren Buildx y sudo root o sin contraseña para la política de trabajo confiable y las operaciones del sistema de archivos de caché. Los límites explícitos ordinarios de CPU/RAM y el uso compartido de recursos no configurados conservan su comportamiento existente.
  • El soporte existente de Swarm es para controladores de escritorio/autohospedados, con transferencia de parada primero y servicios persistentes de instancia única en el administrador conectado. No adopta pilas existentes arbitrarias ni agrega agrupaciones en la nube alojadas. La replicación administrada PostgreSQL/Redis requiere operadores Kubernetes autohospedados.
17 oct2026v0.9.3CaracterísticasCorrecciones25 actualizaciones

Esta versión mejora el monitoreo de la nube y la confiabilidad de la caché de compilación, agrega automatización de implementación y vistas previas de solicitudes de extracción aisladas, y hace que los trabajadores y programadores sean más fáciles de configurar, observar y recuperar. Estas notas cubren todos los cambios combinados desde 0.9.2.

Automatización de implementación y vistas previas

  • Mover variables de comando al entorno

    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.

  • Preparar la salida del marco automáticamente

    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.

  • Revisar montajes de caché manuales anteriores

    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 los problemas de configuración antes

    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.

  • Optar por GitHub vistas previas de solicitudes de extracción

    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 operaciones de vista previa del ciclo de vida

    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.

  • Utilice la automatización del SDK

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

Trabajadores, programadores y reversión

  • Configurar roles sin reconstruir la aplicación 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.

  • Ver e inspeccionar procesos en 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.

  • Mantenga sugerencias de roles independientes

    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 traspasos de roles interrumpidos

    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.

  • Proteger imágenes activas y revertidas

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

  • Restaurar con precisión el entorno de Compose congelado

    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.

Monitoreo, cachés y almacenamiento en la nube

  • Evite costosos escaneos de monitoreo

    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 el uso de RAM de invitados

    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.

  • Mantenga útiles las métricas parciales

    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.

  • Mantenga el alcance de la limpieza de caché en la nube

    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.

  • Aceptar sistemas de archivos sin totales de inodos fijos

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

Dominios e ingreso

  • Enrutar dominios personalizados verificados en la primera implementación

    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 puertos de host secundarios efímeros

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

  • Manejar aplicaciones variadas Cloudflare Acceder

    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.

  • Aclarar la disponibilidad del borde

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

correo web

  • Resolver ID de mensajes exactos para acciones

    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.

  • Almacenar en caché los activos de la aplicación correctamente

    Fingerprinted assets receive immutable caching while application HTML is revalidated.

  • Servir activos precomprimidos

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

16 oct2026v0.9.2CaracterísticasSeguridad39 actualizaciones

Este parche agrega ejecución de trabajadores y programadores, personalización de la apariencia personal y configuración de túnel Cloudflare administrado para servidores autohospedados. Los espacios en la nube, las cachés de compilación reutilizables, más aplicaciones de catálogo y una limpieza de almacenamiento más segura mejoran las operaciones diarias. Estas notas cubren todos los cambios combinados desde 0.9.1.

Trabajadores y programadores

  • Ejecute roles junto a su aplicación web

    Declare workers and schedulers in openship.json o la API del proyecto. Las implementaciones de una sola aplicación Docker inician contenedores separados de la imagen de la aplicación, con entornos compartidos, volúmenes y redes conectadas, sus propios comandos y configuraciones de apagado, y sin puertos publicados. Los roles siguen a la pausa, la reanudación, el reinicio, la reversión y la eliminación del proyecto.

  • Entregar singletons de forma segura

    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.

  • Requerir una startup 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 los valores se eliminan de los roles.

  • Hacer explícita la configuración de roles

    Move and copy refuse active, unfinished or preserved-cancelled role workloads even after saved roles are cleared. Preset-only when y unless Las claves en roles declarados producen advertencias en lugar de parecer silenciosas para controlar la ejecución. La selección automática de roles de marco y la migración de roles entre servidores no están incluidas.

  • Mejorar los valores predeterminados de cierre del marco

    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.

Apariencia y tablero

  • Personaliza tu propia apariencia

    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.

  • Mantenga las herramientas operativas 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.

  • Reducir las falsas alertas de cortes

    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.

  • Mejorar la navegación y la confiabilidad del 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 y dominios

  • Administrar el ingreso autohospedado desde 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.

  • Inscribir dominios con configuración recuperable

    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 se apoya a los compañeros; La inscripción automática comodín no lo es.

  • Elija el comportamiento primario y 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.

  • Mantenga las operaciones del dominio 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.

  • Respete los servidores proxy confiables en los bordes en contenedores

    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.

Espacios en la nube, facturación y conexiones

  • Vea la capacidad administrada como espacios en la nube

    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.

  • Utilice la cuenta de nube propietaria de forma constante

    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.

  • Continuar compras sin repetir la selección del plan

    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 acciones en espacios 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.

  • Mantener la transferencia de instancia con su fuente

    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.

Construir control de rendimiento y recursos

  • Mantener los recursos no configurados sin límites

    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 envíos simultáneos a la nube

    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 cachés de compilación de proyectos delimitados

    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, nuevos y cálidos espacios en la nube

    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.

  • Mostrar qué está haciendo la preparación de la imagen.

    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, GPU y bases de datos compartidas

  • Agregue documentos, paneles y aplicaciones multimedia

    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.

  • Ejecute aplicaciones de IA autohospedadas

    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.

  • Implementar servicios 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.

  • Evite compilaciones innecesarias de WordPress y 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.

  • Compartir bases de datos nativas explícitamente

    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.

Almacenamiento, eliminación y seguridad de la migración

  • Separe los datos nuevos de la aplicación en la nube

    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.

  • Recuperar la eliminación fallida 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 pertenecientes a otros proyectos.

    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 colisiones efímeras entre el puerto y el 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.

Correo, seguridad y localización

  • Persistir en la conectividad backend del correo web

    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 buzones de correo existentes desde la nube

    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 operaciones de correo en contenedores

    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.

  • Cambie el tamaño de su bandeja de entrada y panel de lectura

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

  • Prevenir el clickjacking en el panel

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

  • Ampliar la guía y la documentación traducidas

    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.

Actualice la API y los clientes de escritorio/panel antes de usar las nuevas configuraciones, operaciones de túnel administradas o recetas de catálogo que requieren 0.9.2. Las migraciones de bases de datos incluidas se ejecutan mediante el inicio normal de la API.

13 oct2026v0.9.1CaracterísticasCorrecciones16 actualizaciones

Este parche agrega un catálogo de aplicaciones públicas, compatibilidad con el panel de control ruso y controles de imágenes en tiempo de ejecución. Corrige los guardados del flujo de trabajo y la recuperación en la nube, actualiza el correo web en vivo y mejora el enrutamiento, la creación de capacidad y el manejo de imágenes durante las reimplementaciones. Estas notas cubren todos los cambios desde 0.9.0.

Configuración de aplicaciones, idioma y flujo de trabajo

  • Explorar aplicaciones antes de instalarlas

    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.

  • Soporte de idioma ruso

    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.

  • Guardar flujos de trabajo de acciones 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.

Recuperación de correo web y nube

  • Continuar con las instalaciones de aplicaciones y la selección de planes después de iniciar sesión

    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.

  • Vuelva a conectar los enlaces guardados del servidor en la nube

    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.

  • Recover an existing webmail app

    When a mail registration loses its webmail link, select an accessible existing app on the same mail server and hostname and choose Reconectar e implementar. La recuperación reutiliza el proyecto, las credenciales y los volúmenes persistentes al tiempo que preserva la propiedad del dominio y las comprobaciones de permisos.

Seguridad de implementación y configuración en tiempo de ejecución

  • Seleccione versiones de tiempo de ejecución coincidentes e imágenes de producción personalizadas

    Generated PHP builds support PHP 8.3 and 8.4 through the generic runtimeVersion configuración. Docker compilaciones fuente ofrecen una versión avanzada runtimeImage anular. Las recetas seleccionadas por pila validan las capacidades reales de ejecución y la compatibilidad antes de la activación; las configuraciones no válidas no actualizan parcialmente el proyecto y la reversión de imágenes retenidas conserva la versión original y la configuración de la imagen.

  • Recuperar acciones en la nube de instancias conectadas

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

  • Utilice la capacidad de construcción disponible real del 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.

  • Vuelva a comprobar el estado de la implementación

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

  • Realice un seguimiento de las imágenes del contenedor actual durante las redespliegues de Compose

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

  • Reciba cambios en la bandeja de entrada en vivo

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

  • Simplifique la página de copia de seguridad del proyecto

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

  • Validar roles de tiempo de ejecución declarados

    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 dominios que enrutan solo rutas específicas

    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.

  • Actualizar imágenes de implementación antes de reemplazar servicios

    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 oct2026v0.9.0CaracterísticasCorrecciones40 actualizaciones

OpenShip Las acciones llevan el CI del repositorio a sus propios servidores Linux y macOS y a los ejecutores de la nube. Esta versión también le permite mover su plano de control OpenShip entre el escritorio y un servidor, agrega comprobaciones de implementación GitHub y notificaciones compartidas, y mejora la programación, el enrutamiento, el monitoreo y el correo web de la compilación en la nube. Estas notas cubren todos los cambios desde 0.8.2.

OpenShip Acciones

  • Ejecute CI independientemente de GitHub acciones

    Workflows in .openship/workflows/ use YAML de estilo GitHub y ejecute OpenShip en destinos seleccionados. Dispárelos manualmente, mediante envíos o solicitudes de extracción del repositorio, según programaciones, mediante envío autenticado o desde trabajos. GitHub puede proporcionar fuentes, eventos y comprobaciones de confirmación sin ejecutar el flujo de trabajo en sí.

  • Usar flujos de trabajo de GitHub existentes con OpenShip ejecutores

    Workflows in .github/workflows/ Mantén la orquestación, los secretos, los entornos y las comprobaciones de GitHub. Registra corredores oficiales en OpenShip destinos y apunta a sus etiquetas autohospedadas. Los trabajos destinados a etiquetas alojadas en GitHub aún se ejecutan en GitHub; importar un flujo de trabajo no cambia silenciosamente su plataforma de ejecución.

  • Un editor de flujo de trabajo

    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.

  • Flujos de trabajo reutilizables y trabajos avanzados

    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.

  • Elija 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.

  • Revisar el acceso antes de la ejecución

    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.

  • Sigue carreras sin perder tu 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.

  • Artifacts, caches and OIDC

    Independent workflows support artifact/cache actions through scoped storage access and configured backup destinations. Jobs with id-token: write puede solicitar tokens OIDC de OpenShip de corta duración desde una instancia HTTPS. Los proveedores de identidades deben confiar explícitamente en el emisor de OpenShip; estos no son tokens emitidos por GitHub. Las claves de firma viajan con movimientos de instancia.

  • Conoce los límites

    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 y financiación de Cloud Actions

  • Reutilizar un servidor o agregar uno

    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 temporales por trabajo

    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.

  • Financiamiento y recuperación

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

  • Configuración del operador de la nube

    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 Comprobaciones y notificaciones

  • Comprobaciones de implementación habilitadas de forma predeterminada

    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.

  • La configuración de comprobaciones muestra el acceso 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.

  • Agregar canales de notificación en línea

    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.

  • Un editor de notificaciones

    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.

Conexiones de escritorio y movimientos de instancias

  • Mover el control a un 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.

  • Retroceder usando los datos más recientes

    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.

  • Conéctate sin mover datos

    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.

  • Invitaciones abiertas en el escritorio

    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, compilaciones y hosting en la nube administrados

  • Administre el acceso al servidor en un solo 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.

  • Admisión de construcción duradera

    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.

  • Asignaciones guardadas del plan

    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.

  • Recuperar compilaciones interrumpidas de forma segura

    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.

  • Los sitios estáticos utilizan de forma predeterminada las páginas en la nube

    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.

  • Inicio de aplicaciones más confiable

    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.

  • Consistent package managers

    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.

Deployment, routing and monitoring fixes

  • Elija otro puerto explícitamente

    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.

  • Mantenga el estado de enrutamiento 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 Cloud HTTPS en el borde de servicio

    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 la pérdida de conexión de los errores de solicitud

    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 la implementación en Monitoreo

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

  • Corrección de compilación y tiempo de ejecución

    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 y correo web

  • Informe de errores estructurado

    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 automatización más amplia

    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 rutas y pares de entornos posicionales, y guía a los usuarios para iniciar sesión en caso de fallas de autorización. Las acciones están disponibles a través de openship api; esta versión no presenta un dedicado openship actions grupo de mando.

  • Documentación actualizada

    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.

  • Mejoras en el correo web

    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.

  • Correcciones de compatibilidad adicionales

    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.

  • Verificación de liberación

    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.

Actualizando

Los usuarios de Desktop 0.8.2 pueden utilizar el actualizador integrado. Los usuarios de escritorio que aún tengan 0.8.0 o 0.8.1 deben descargar el instalador 0.9.0 e instálelo manualmente una vez. Salga de OpenShip y reemplace la aplicación; Mantenga los datos de la aplicación para preservar proyectos, servidores y configuraciones. La ruta de actualización del servidor/CLI no requiere este paso de recuperación del escritorio. Actualice la API y el panel de control juntos; Los movimientos de instancia requieren versiones compatibles en ambos extremos.

6 oct2026v0.8.2CaracterísticasCorrecciones3 actualizaciones

Recuperación de actualización de escritorio

  • Se corrigieron los redireccionamientos de la versión GitHub en el actualizador de escritorio mientras se conservan los hosts de descarga confiables, las comprobaciones SHA-256 y la verificación de la firma del editor.
  • Se agregó una prueba de descarga de Electron real al CI existente y a la puerta de prueba de lanzamiento, que cubre el instalador y las redirecciones de prueba, los destinos bloqueados, los bucles de redireccionamiento, la cancelación y la limpieza de descargas incompletas.
  • Este error de redireccionamiento afecta al actualizador del instalador de escritorio. La ruta de actualización del servidor/CLI es independiente y no necesita este paso de recuperación manual.

Usuarios de escritorio en 0.8.0 o 0.8.1: instalen esta actualización manualmente una vez. El actualizador integrado en esas versiones puede fallar con "La redirección fue cancelada". Download the installer for your operating system from the versión 0.8.2, salga de OpenShip y reemplace la aplicación instalada. Conserve los datos de su aplicación: sus proyectos, servidores y configuraciones locales se conservan. Las actualizaciones de escritorio posteriores utilizan el descargador fijo.

6 oct2026v0.8.1CaracterísticasCorreccionesSeguridad50 actualizaciones

OpenShip Cloud ahora ejecuta proyectos en servidores administrados con sus propios planes mensuales. Comparta un servidor entre aplicaciones, agregue otro cuando lo necesite y administre sus recursos en la nube junto con proyectos locales desde el escritorio o desde el alojamiento propio OpenShip. Esta versión también agrega claves de acceso, autenticador 2FA y una bandeja de entrada de soporte privada, amplía la automatización CLI y mejora la facturación, la migración y la recuperación de la implementación.

Servidores en la nube administrados

  • Un servidor, múltiples proyectos

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

  • Elija Docker o Ejecución directa

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

  • Utilice la capacidad que compró

    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.

  • Inspeccionar el uso por separado de la capacidad

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

  • Administre el servidor cuando lo necesite

    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 operaciones sin perder proyectos vecinos

    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.

Cuentas de nube en escritorio y autohospedadas OpenShip

  • Tus recursos existentes en la nube aparecen cuando te conectas

    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 y use servidores administrados desde el mismo panel

    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.

  • Los cambios de cuenta borran el estado de la cuenta 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.

Facturación y planes.

  • Los servidores mensuales incluyen su período de pago completo.

    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.

  • Planes revisados y 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.

  • La facturación sigue el servidor seleccionado

    Switch servers without losing the page, inspect each subscription independently, or use Obtener servidor para una nueva compra. Los clientes nuevos ven planes en lugar de pantallas de uso vacías. Las comparaciones de actualizaciones más pequeñas mantienen tarjetas compactas y un resumen del plan actual por separado; Los métodos de pago y las facturas comparten el portal Stripe del servidor.

  • Revisar los cambios del plan antes de aplicarlos.

    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.

  • El pago tiene una ruta de recuperación visible

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

  • Reanudar o cancelar pagos pendientes

    Pagos pendientes enumera la oferta guardada de cada servidor y abre su pago original. La cancelación confirmada por el proveedor le permite elegir otro plan o eliminar un servidor no utilizado y no pagado. Las instalaciones conectadas y en la nube comparten el flujo de recuperación, y al cambiar de cuenta se descartan los detalles de pago y las respuestas de la cuenta anterior (#1067).

  • Vista previa de niveles PAYG prepagos

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

Seguridad de la cuenta y GitHub

  • Claves de acceso y 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).

  • La protección de la cuenta se mantiene constante durante las fallas

    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.

  • GitHub el acceso al repositorio es independiente del inicio de sesión

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

  • Los tokens personales funcionan en todo el flujo del repositorio

    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.

Soporte e incorporación

  • Una bandeja de entrada de soporte en la nube privada

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

  • Las páginas de soporte y contacto aceptan solicitudes duraderas

    Submissions are saved before email delivery, with a receipt and notification to [email protected]. Los reintentos de entrega sobreviven a los reinicios de la API y las respuestas de soporte aparecen en la bandeja de entrada y se envían por correo electrónico al cliente. Los envíos reintentados reutilizan su recibo original en lugar de crear otro ticket (#970).

  • Pantallas de cuenta y de primera ejecución más 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.

Aplicaciones y migración

  • Las aplicaciones tienen su propio 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.

  • Un asistente de implementación más 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.

  • La instalación de la aplicación explica las opciones de enrutamiento y 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 aplicaciones a servidores en la nube administrados

    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.

  • Revisar importaciones como tarjetas o topología

    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.

Builds, deployments and recovery

  • Detener cancela el constructor seleccionado

    Cancellation reaches the worker's actual Docker or Bare runtime, including remote Git and archive preparation. The UI shows Parando… hasta que finalice la limpieza, luego permite la redistribución. La cancelación de una compilación conserva los contenedores implementados que heredaron las etiquetas de compilación; la propiedad ambigua del servicio aún bloquea la activación (#1059).

  • La salida de la compilación permanece legible

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

  • Los servicios de redacción sin cambios siguen ejecutándose

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

  • Las copias de seguridad previas a la implementación finalizan antes de la activación

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

  • Las compilaciones remotas y las versiones estáticas utilizan las rutas correctas

    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 las negaciones se respetan (#1010, #1041).

  • Los controles de estado y el apagado respetan el tiempo de ejecución

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

  • Detección de Farm.js

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

Dominios, networking y monitorización

  • Los dominios gratuitos siguen el servidor administrado seleccionado

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

  • Conecta Cloudflare desde la configuración del dominio

    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 comodín y recuperación de Edge más confiables

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

  • Las actualizaciones de origen permanecen visibles hasta que se completa la implementación

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

  • Correcciones de conexión y configuración.

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

Correcciones de SDK, CLI y plataforma

  • Más administración a través de Ship SDK y 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.

  • Ediciones de entorno y orientación de comandos más seguras

    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.

  • Flujos de trabajo de MCP Cloud más claros

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

  • Correcciones de correo web y panel de control

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

  • Inicio de API y validación de acciones masivas

    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álisis opcional de productos en la nube

    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.

Notas de actualización y transferencia de datos

  • Exportaciones completas y portátiles

    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.

  • Las importaciones conservan el alcance y los datos seleccionados

    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; Los campos de archivo no admitidos se rechazan antes de cambiar los datos.

  • Actualice la nube antes que los 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.

  • Mantenga estable la configuración de seguridad de la cuenta

    Self-hosted passkeys require HTTPS and a stable dashboard hostname through OPENSHIP_PUBLIC_URL (localhost es compatible para el desarrollo). Conservar y realizar copias de seguridad BETTER_AUTH_SECRET, que protege los secretos del autenticador y los códigos de recuperación.

27 sept2026v0.8.0CaracterísticasCorreccionesSeguridad62 actualizaciones

Escale las aplicaciones PostgreSQL y Redis en sus propios servidores, conecte esos servidores a través de redes privadas y comparta archivos entre instancias de aplicaciones. Esta versión también agrega el SDK Node.js, amplía la automatización de MCP, actualiza el panel y la experiencia de escritorio y trae las correcciones de implementación, entorno, enrutamiento, respaldo, correo y seguridad acumuladas desde 0.7.2.

Clústeres de servidores y redes privadas

  • Conecte servidores entre proveedores

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

  • Las redes y los clústeres de computación tienen 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.

  • Elija qué servidores pueden comunicarse entre sí

    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.

  • Probar la red desde la topología.

    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.

  • Prepare, revise, reintente y limpie los cambios de red

    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.

  • Prepare servidores para el escalado de aplicaciones

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

Escalado de aplicaciones

  • Ejecute una aplicación o un trabajador en sus 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.

  • Actualizar, revertir y recuperar aplicaciones en ejecución

    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.

  • Montar archivos compartidos en instancias de aplicaciones

    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.

Bases de datos y almacenamiento compartido

  • Elija independiente o agrupado 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.

  • Ejecute Redis de forma independiente o como un clúster

    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.

  • Realizar una copia de seguridad y recuperar PostgreSQL y 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 bases de datos existentes y actualice PostgreSQL

    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.

  • Compartir archivos con copias de disco independientes

    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 archivos desde fuera del clúster

    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.

  • Conservar datos al eliminar una base de datos

    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 y MCP

  • Un SDK de Node.js junto con la CLI

    El openship El paquete ahora proporciona OpenshipClient a través de openship/client para instalaciones remotas y createShip a través de openship/native para un motor integrado sin un servidor API independiente. Ambos utilizan operaciones, validación y autorización de plataforma compartida. Las instancias nativas tienen ciclos de vida de inicio/cierre explícitos y ámbitos de espacio de trabajo verificados; ESM y CommonJS son compatibles con Node.js 22 y posteriores (#887).

  • MCP cubre una mayor parte del ciclo de vida operativo

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

  • Los flujos de trabajo CLI utilizan el SDK compartido

    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.

Implementaciones y compilaciones

  • Ejecute comandos de liberación antes de la activación

    Configure releaseCommands en configuración de compilación, openship.json o la API/SDK del proyecto. Los comandos se ejecutan en orden después de la compilación, utilizando el entorno de la versión candidata, con registros transmitidos y un presupuesto de diez minutos por comando. El fallo, el tiempo de espera o la cancelación detiene la activación. Se admiten implementaciones de aplicación única Docker y desnudas; Los tipos de implementación no admitidos rechazan los comandos configurados. Las reversiones los omiten y la reversión del código de la aplicación no deshace los cambios en la base de datos (#592).

  • La finalización y el tiempo transcurrido sobreviven a los reintentos y a la actualización

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

  • La retención de reversión tiene un límite predecible

    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.

  • Construcciones de fuentes más confiables

    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 Se detectan asignaciones, se rechaza la creación de monorepo vacío no válido y las fallas del servicio DNS en el momento de la compilación reciben una explicación procesable.

  • Los errores de implementación llegan a la interfaz de usuario

    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.

Entorno y composición

  • Las variables de servicio guardadas permanecen visibles

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

  • Las actualizaciones de redacción se aplican sin puertas de aprobación de rutina

    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 y aplicar cambios ambientales 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.

  • Descarga del entorno y protección 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).

Migración y portabilidad

  • La migración de redacción incluye la transferencia del dominio

    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 un servicio en todos los proyectos

    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.

  • Exportar la configuración, el entorno y las credenciales de un proyecto.

    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.

Dominios y certificados

  • HTTPS comodín con DNS automático o verificación TXT manual

    Project and service domains such as *.example.com now open inline certificate setup. Connected DNS providers automate verification; Las órdenes TXT manuales conservan su progreso a través de reconexiones y reinicios del controlador. API, SDK y MCP comparten las mismas operaciones de inicio, estado, verificación y cancelación. Los certificados existentes sobreviven a los intentos fallidos y se informa que HTTPS está listo solo después de que su ruta esté activa. Los certificados manuales incluyen orientación sobre renovación en los nueve idiomas del panel (#954).

  • Administrar múltiples dominios comodín

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

  • Los reintentos de enrutamiento concilian el estado guardado y en vivo

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

  • Los estados pendientes explican lo que sucederá a continuación

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

  • Los certificados importados y las rutas de contenedores se recuperan correctamente

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

Copias de seguridad y restauración

  • Realice una copia de seguridad ahora desde el panel de proyecto, servicio o volumen

    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.

  • Copias de seguridad incrementales opcionales

    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.

  • La retención y los destinos se mantienen 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 antes de reemplazar datos

    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 y accede

  • Las conexiones a la nube GitHub finalizan en el panel

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

  • La selección del repositorio 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).

  • El inicio de sesión y las invitaciones respetan el flujo 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.

Panel de control y escritorio

  • Íconos compartidos y diseños más 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).

  • La topología permanece dentro del proyecto.

    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.

  • Las páginas de implementación dan prioridad a las acciones y los registros

    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.

  • Las páginas de respaldo muestran los datos retenidos y el estado de ejecución real

    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.

  • El inicio del escritorio sigue el tema de la aplicación.

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

Monitoreo y confiabilidad del tiempo de ejecución

  • La supervisión se recupera después de interrupciones de la conexión

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

  • Las vistas de tráfico utilizan la misma serie 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.

  • Los recursos de largo plazo están limitados y 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).

  • La administración del servidor informa fallas procesables

    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.

Nube y API

  • La facturación en la nube sigue la organización seleccionada

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

  • Las API independientes limitan las inundaciones no 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 ese techo exterior al proxy ascendente conservando al mismo tiempo los límites por ruta (#123).

correo

  • Comprobar y renovar los certificados que realmente utilizan los clientes de correo

    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.

  • Webmail se actualiza sin suscripciones 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).

  • El bloqueo de contenido remoto también cubre CSS

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

  • La configuración, entrega y alertas del correo son más confiables

    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 cheques

  • Continuar una versión no publicada con código actualizado

    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.

  • Viajes reales de aceptación de aplicaciones, bases de datos y almacenamiento compartido

    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 actualización

  • Alcance de escala en esta versión

    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.

  • Mantenga la base de datos y la clave de cifrado juntas

    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 instalaciones API) antes de actualizar. La degradación a una versión anterior a esta protección requiere la copia de seguridad de la base de datos correspondiente. Utilice Data Transfer con secretos incluidos al mover la configuración entre instancias con diferentes claves.

5 sept2026v0.7.2CaracterísticasCorreccionesBreaking1 actualización

Parche de mantenimiento suave para la confiabilidad de la compilación Docker. Sin cambios importantes de API ni migraciones de bases de datos.

construye

  • Las compilaciones exitosas Docker ya no son rechazadas por el texto del registro de diagnóstico

    Fixes a regression present in 0.7.1 where successful workspace scripts reporting Exited with code 0 podría fallar la implementación (#832). Las compilaciones de imagen única y Compose ahora distinguen los errores del motor Docker de la salida de la aplicación, tanto para los compiladores clásicos como para los BuildKit. Las sugerencias de diagnóstico enriquecen las fallas reales sin anular la finalización exitosa ni ocultar el error de Docker; Las compilaciones SSH continúan usando el estado de salida del comando. Las salvaguardias de cancelación e inactividad permanecen vigentes.

4 sept2026v0.7.1CaracterísticasCorreccionesSeguridad24 actualizaciones

Esta versión refuerza el ciclo de vida completo de la implementación, hace que la conciliación de Compose no tenga pérdidas, completa la configuración del servidor remoto y la segmentación CLI, corrige el estado y la administración del correo externo y envía el trabajo de invitación, DNS, enrutamiento de catálogo y experiencia de actualización acumulado desde 0.6.9.

control de fuente

  • Los espacios de trabajo autohospedados pueden poseer y administrar múltiples aplicaciones GitHub

    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 personales y claves SSH por servidor siguen siendo alternativas compatibles (#782).

  • GitHub La instalación de la aplicación es segura para los inquilinos de principio a fin

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

Cuentas y equipos

  • Las invitaciones a organizaciones autohospedadas ahora funcionan para usuarios nuevos

    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

  • Los dominios personalizados de servicio utilizan el flujo de trabajo de aplicación/planificación 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).

Configuración del servidor

  • Los servidores remotos siempre requieren Docker antes de Edge

    Server readiness no longer inherits the control plane's DEPLOY_MODE. Docker y Git se verifican para cada objetivo administrado, mientras que un planificador de dependencias compartido inserta y ordena Docker antes del Edge basado en contenedores en la configuración transmitida. SystemManagery protectores de instalación directa de componentes (#767).

construye

  • openship.json El entorno ahora llega a Dockercompilaciones de archivos de un extremo a otro.

    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 agrega anulaciones por imagen (null hereda el valor correspondiente del proyecto), mientras que el servicio env permanece solo en tiempo de ejecución (#795).

  • BuildKit crea trabajo a partir de instalaciones autohospedadas basadas en Bun

    Docker's reverse h2c session now bypasses Bun's incompatible node:http ruta de actualización manteniendo la sesión BuildKit de Dockerode y el servicio de autenticación de registro. Las compilaciones de composición local que utilizan directivas de sintaxis, montajes de caché, documentos heredocs y otras funciones de archivo Docker exclusivas de BuildKit ya no fallan /session antes de que comience el archivo Docker (#745).

Actualizaciones

  • Las indicaciones de actualización muestran el registro de cambios del producto

    Dashboard and desktop update surfaces now read the matching version from the tagged CHANGELOG.md en lugar de repetir el cuerpo de la publicación GitHub. El panel de actualización nativo mantiene la copia de aviso separada de un registro de cambios desplazable y de tamaño variable, y todas las acciones del registro de cambios abren la página de versión en openship.io en lugar de GitHub (#752).

  • Las implementaciones exitosas ya no vuelven a anunciar actualizaciones 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).

Aplicaciones del catálogo

  • Los puntos finales de aplicaciones de solo puerto están 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. Esto hace que la URL del servidor del asistente y {{publicUrl:…}} sustituciones veraces. Reintentar un borrador fallido reconcilia el enlace de forma idempotente y cambiar a un dominio elimina o restaura solo la asignación propiedad del instalador (#770).

entrega de correo

  • La configuración del correo ahora demuestra la accesibilidad pública antes de declarar el éxito

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

  • El estado del correo ya no trata las respuestas IPv6 de IP falsas como DNS roto

    Synthetic ULA AAAA responses from Clash/sing-box are now unknown, coincidiendo con el comportamiento del registro A existente. Junto con la fila informativa SpamAssassin y la comparación DKIM de cadena dividida normalizada, esto cierra las tres rutas de falso positivo informadas en el n.° 240.

  • El correo web retransmitido mantiene la ruta de entrega dividida correcta

    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.

  • El remitente de la plataforma ahora se repara automáticamente en lugar de quedarse atascado en SMTP 535

    Cached openship@<domain> Las credenciales se reutilizan solo mientras el buzón activo y las filas de reenvío permanecen activas. Una fila eliminada se recrea automáticamente y un transportador ya almacenado en caché gira una vez y vuelve a intentar de forma segura un rechazo de autenticación (#754).

  • El buzón de la plataforma está protegido y reparable.

    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.

  • La configuración de correo funciona con usuarios SSH no 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, y un servidor sin raíz o sudo sin contraseña recibe un rechazo escrito procesable a menos que el montaje del enlace de correo se haya hecho explícitamente escribible para ese inicio de sesión (#756).

Cancelación de implementación

  • La cancelación después de la creación de una imagen ahora detiene todo el trabajador de implementación.

    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.

  • La redistribución espera a que finalice el trabajador real

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

  • Cancellation cannot replace or tear down the live release

    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.

Redactar reconciliación

  • Las ediciones del repositorio no pueden borrar silenciosamente las variables de entorno del servicio

    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.

  • Los proyectos de Local-path Compose materializan sus servicios automáticamente

    project create --local-path ... --type services ahora utiliza el escáner canónico de la API y conserva las filas detectadas inmediatamente. La implementación y la reimplementación también vuelven a leer la misma fuente local a través del reconciliador de tres vías existente, por lo que un proyecto heredado de fila cero se repara automáticamente en lugar de ingresar a una canalización de servicios vacía (#751).

  • Las expresiones de entorno de redacción tienen un significado de sincronización/implementación

    Raw manual syncs preserve ${VAR} procedencia y resolverlo desde el entorno final del proyecto/servicio en el momento de la implementación, mientras que Docker las sincronizaciones CLI normalizadas por Compose llevan un marcador de valor final explícito, por lo que se escapó $$ nunca se expande dos veces (#751).

  • Los fallos del terminal sobreviven a la actualización

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

Interfaz de línea de comandos

  • Los nuevos proyectos e implementaciones pueden apuntar a un servidor SSH registrado

    project create --server <id> almacena el enlace inicial, mientras deploy --server <id> impulsa las cargas de carpetas y Git a través del mismo solucionador de destino con ámbito de organización y verificación previa de implementación que el panel. La respuesta de implementación expone una identificación estable para --watch, project get muestra el objetivo resuelto y una implementación fallida nunca reorienta el proyecto (#763).

30 ago2026v0.6.9Características7 actualizaciones

Esta revisión crítica de seguridad de implementación cierra la propiedad heredada de Docker Compose y el error de enrutamiento. Las pilas no administradas existentes ya no pueden confundirse con una implementación OpenShip ni duplicarse silenciosamente, y una reimplementación normal en el mismo servidor no puede mover un servicio enrutado a un puerto de host diferente.

Implementaciones y enrutamiento

  • Las pilas de Compose existentes nunca se adoptan implícitamente

    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 y le dice al operador que lo importe/adopte, lo elimine o le cambie el nombre. Los contenedores adoptados explícitamente y los contenedores ya rastreados por OpenShip continúan con normalidad.

  • Los puertos de host del mismo servidor permanecen bloqueados durante las redespliegues

    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.

  • Las advertencias de contenedores duplicados requieren evidencia de propiedad

    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.

Redactar reconciliación

  • Los metadatos del analizador heredado no crean una deriva falsa en el repositorio

    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.

Monitoreo

  • Problemas ahora es el espacio de trabajo Monitoreo

    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.

  • Las lecturas de salud reutilizan el observador 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.

  • Las actualizaciones y reexploraciones de la flota continúan en 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 ago2026v0.6.8CaracterísticasSeguridad20 actualizaciones

Los proyectos de Compose ahora se implementan como los servicios que declaran, con sus argumentos de compilación y su entorno dinámico intactos desde la importación hasta la reversión. Los movimientos de instancias pueden ir directamente de una instalación autohospedada a otra sin copiar una clave de cifrado, y el flujo de trabajo del archivo muestra y filtra lo que transportará. Esta versión también refuerza la propiedad de dominio personalizado, la asignación de puerto de host, los límites de credenciales de Git y la recuperación perimetral en Linux y macOS.

transferencia de instancia

  • Mover una instancia directamente, credenciales incluidas

    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 o administrar una contraseña de transferencia (#656).

  • Ver y filtrar la exportación antes de descargarla

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

  • Los archivos con credenciales no se pueden importar medio 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.

Composición y entornos.

  • Los servicios de redacción impulsan sus propias compilaciones

    A project with composePath se materializa en la canalización del servicio en lugar de pasar a una compilación de archivo Docker genérica. Mapa y lista de formas de build.args, argumentos desnudos, y ${...} las expresiones se almacenan por servicio y sobreviven a la sincronización CLI, la reconciliación, la adopción de la migración, la reimplementación de instantáneas y la reversión. Las compilaciones de socket, SSH, por lotes y en la nube de Docker utilizan el mismo solucionador de argumentos, y el registro de comandos de compilación de OpenShip no imprime valores de argumentos (#689).

  • Removing Compose build arguments removes the stored arguments

    An empty args mapa o un eliminado args La clave borra los valores obsoletos y la procedencia de la interpolación, mientras que las instantáneas creadas antes de que existieran los argumentos de compilación permanecen no destructivas durante la reversión (#689).

  • Las compilaciones de Compose no compatibles fallan antes de la implementación

    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.

  • El entorno de composición dinámica se resuelve en el momento de la implementación

    Raw expressions such as postgresql://user:${POSTGRES_PASSWORD:?set it}@postgres:5432/app se evalúan en comparación con las capas del proyecto final, de lanzamiento congelado, en línea y con alcance de servicio. Los requisitos integrados, las claves de transferencia, los valores predeterminados, las expresiones anidadas y los dólares de escape conservan la semántica de Compose; una variable requerida no resuelta hace fallar ese servicio con la clave faltante denominada (#673).

  • Las variables de servicio manual son anulaciones duraderas

    The service Environment tab now owns service-scoped environment rows rather than rewriting the Compose-owned service.environment objeto. Por lo tanto, los valores agregados en la interfaz de usuario sobreviven a un análisis de Compose y a una reimplementación del proyecto. Guardar un secreto no revelado (incluido cambiar el nombre de su clave) conserva su texto cifrado existente en lugar de almacenar la máscara o eliminar el valor.

Implementaciones y enrutamiento

  • Las imágenes de contenedores prediseñadas se pueden rastrear como lanzamientos

    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 sin reconstruir una sola aplicación

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

  • El punto de control de DNS cubre Docker y todas las rutas de redacción.

    Pressing Deploy now shows records for single-app custom domains, service scalar routes, and multi-route Compose endpoints. Multiple hostnames appear together, www se agrupa con su vértice y una vista previa de implementación remota utiliza la dirección pública del servidor seleccionado en lugar de la dirección de esta instancia (#663).

  • La redistribución no puede separar un dominio 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).

  • Los contenedores detenidos no pueden convertir un nombre de host antiguo en otra aplicación

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

  • Reintentar el enrutamiento repara el borde primero

    When openship-edge está detenido o falta, Reintentar enrutamiento lo concilia y lo verifica antes de tocar los vhosts. Un borde irrecuperable devuelve una advertencia procesable inmediatamente en lugar de colgarse hasta que se agote el tiempo de espera de la solicitud de ruta (#693).

  • La eliminación de proyectos ya no bloquea a un oyente OpenResty simple

    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 oyentes, y falla cerrada cuando no se puede probar la propiedad. Las marcas de eliminación ahora funcionan de manera consistente en cadenas de consulta y cuerpos JSON; forceOrphan registra la limpieza del host inconclusa de forma duradera antes de eliminar el proyecto para que el recolector de basura pueda volver a intentarlo de forma segura (#700).

Anfitriones y ventaja

  • Docker la adquisición de la fuente sigue el 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 los montajes de borde utilizan rutas de host físicas

    Bind sources are canonicalized on the machine that owns the Docker daemon, so /var y /etc resolver a sus /private/... targets before Docker Desktop or OrbStack sees them. A healthy-looking edge with stale logical mounts is recreated onto the same vhost, certificate, ACME, and static-data directories (#692).

Seguridad

  • Un directorio de configuración CLI explícito GitHub es un límite de aislamiento

    Fallback token discovery reads exactly the hosts.yml seleccionado por la precedencia CLI de GitHub en Linux, macOS y Windows. si GH_CONFIG_DIR o XDG_CONFIG_HOME está configurado pero falta o no tiene token, OpenShip ya no accede al directorio de inicio de otro usuario y toma prestada esa credencial (#687).

Correo OpenShip

  • SMTP entrante tiene DNS dentro del chroot de Postfix

    Every mail-engine boot now refreshes resolv.conf y los archivos NSS de soporte dentro del spool persistente de Postfix antes de que comience el supervisor. El motor falla al cerrarse si no se puede instalar ningún solucionador, en lugar de iniciar un servicio SMTP que rechaza a todos los remitentes legítimos con 450 Helo Host not found (#686).

Panel de control

  • Los entornos del proyecto se actualizan sin necesidad de actualizar

    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 ago2026v0.6.6CaracterísticasCorreccionesSeguridad27 actualizaciones

El correo aprende a recibir y los secretos de terceros llegan a casa. OpenShip Mail ahora captura, filtra y lee los mensajes entrantes, y un mensaje entrante puede generar una notificación. Junto a él, un único almacén de credenciales con ámbito de organización reemplaza la tabla de tokens DNS única y desbloquea la extracción de imágenes privadas en cualquier host. El catálogo de aplicaciones se puede instalar de un extremo a otro, el registro de auditoría sale de Configuración a su propia página y las cargas dejan de fallar a 1 MB.

Seguridad

  • Las escrituras de trabajos están autorizadas en los propios servidores de destino del trabajo.

    Jobs are instance-wide, so the job:write El permiso (que verifica la membresía de la organización) no es en sí mismo autoridad sobre los servidores en los que se ejecuta un trabajo de comando. Editar y eliminar un trabajo ahora pasa por la misma verificación del servidor de destino que ya se realizó al crear y ejecutar uno, y una denegación es indistinguible de un trabajo que no existe. Reportado externamente; Se agregaron pruebas de regresión. Las instancias autohospedadas con más de un nivel de confianza deberían actualizarse; OpenShip Cloud nunca se vio afectado (la API de Empleos está localOnly).

Credenciales

  • Una tienda para secretos de terceros

    A provider registry (container registries, Cloudflare, and room for what comes next) behind one table, with every secret sealed in a single enc1: sobre en lugar de una columna por campo. Una credencial se verifica con su proveedor. antes se almacena, por lo que un token incorrecto se rechaza donde lo pega en lugar de donde lo necesita una implementación.

  • Las imágenes privadas atraen a todos los hosts

    Registry auth is resolved per image from that store (#581). On a remote host the config goes to a temporary DOCKER_CONFIG directorio (0700, archivo 0600) se elimina ya sea que la extracción tenga éxito o falle, por lo que una extracción nunca edita el propio operador ~/.docker/config.json. Las extracciones locales aún pasan por el propio almacén de credenciales del demonio, que es lo que mantiene un escritorio Docker. credsStore trabajando.

  • Las credenciales DNS se pliegan en él.

    Existing Cloudflare tokens are re-wrapped at boot. A token that cannot be decrypted (a rotated BETTER_AUTH_SECRET) se deja exactamente donde está, y la fila heredada se elimina solo una vez que existe la nueva: una falla en medio del movimiento deja credenciales duplicadas, nunca cero.

  • Las credenciales de Git obtienen su propia pestaña

    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.

correo entrante

  • Se puede leer un buzón

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

  • El filtrado entrante falla cerrado

    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 es una notificacion

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

Correo OpenShip

  • La creación del buzón se ejecuta en el motor, no en el host

    doveadm y chown se ejecutaron en el host, donde no existen, por lo que la creación de un buzón devolvió un 500 (GH-562).

  • El arranque de la base de datos falla estrepitosamente

    The script had no set -e, por lo que un paso fallido aún reportó éxito y dejó un motor medio abastecido con un aspecto saludable (GH-562).

  • Las pantallas de correo se parecen al producto.

    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 aplicaciones

  • Cada aplicación se instala

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

  • verified significa publicado anteriormente

    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 al tiempo real de instalación

    Its bootstrap assumed a readiness it never waited for.

Migración

  • Una selección se resuelve por identidad, no por nombre

    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.

  • La propia pila de OpenShip está excluida, no es un bloqueador

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

  • Dos soluciones a lo que importa un escaneo de vhost

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

Borde

  • Sube por defecto a 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 ahora se envía a http alcance en cada configuración de borde, lo que deja que el valor propio de un proyecto gane dondequiera que se establezca. Los hosts instalados antes de esto se reparan en su lugar y un valor que un operador ajustó por sí mismo nunca se sobrescribe.

Registro de auditoría

  • Su propia pagina

    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á en la URL.

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

  • Los eventos no catalogados están catalogados.

    Events emitted without a taxonomy entry now have one.

Correcciones

  • openship reset-admin-password funciona en una instalación de Compose

    It authenticated with ~/.openship/internal-token, un archivo que la ruta de Compose nunca escribe: el contenedor de API se inicia con el INTERNAL_TOKEN de ~/.openship/compose/.env. Entonces, en un cuadro de redacción el comando acuñado un token aleatorio nuevo, lo envió e informó Unauthorized — el comando lockout-recovery no se podía utilizar exactamente en la instalación que lo necesitaba. El token con el que se ejecuta este cuadro ahora se resuelve en un solo lugar, los lectores nunca acuñan y un root propiedad .env este usuario no puede abrir lo que dice (volver a ejecutar con sudo) en lugar de informar un error de autorización. La misma solución llega al "Restablecer contraseña de administrador" del panel de control. openship doctor (cuya lectura de salud aparecía vacía en cada pila de Compose), y una caja desnuda :80/:443 adquisición, que buscó el token Compose y omitió la importación de los sitios migrados después de detener el proxy del operador.

  • Un restablecimiento de contraseña utiliza un código de 6 dígitos

    Rather than an emailed link.

  • Un despliegue cancelado mantiene su motivo

    The failure message was gated on failed solo, lo que borró el motivo en cada fila cancelada. Pero una cancelación no siempre es su parada: el barrido de arranque se cancela con "Interrumpido por un reinicio del servidor", y una falla parcial reemplazada registra el motivo. Con el motivo descartado, al asistente de instalación solo le quedó imprimir el mensaje genérico "Error de instalación" sobre una fila que decía cancelled.

  • El veredicto de una instalación y su motivo coinciden.

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

  • Verificar aparece solo una vez que existe una fila de dominio

    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.

  • Un compromiso abreviado no es un compromiso nuevo

    POST /deployments toma commitSha como cualquier cosa que envíe la persona que llama (openship deploy --commit 1eeaf76, la herramienta de implementación de MCP, un script de CI) y git comprueba felizmente una abreviatura: el código correcto se envió mientras la fila registraba un nombre que ninguna comparación podía igualar. La verificación de deriva lo comparó con la rama HEAD de 40 caracteres, y dado que ambos lados representan siete caracteres, la página del proyecto anunciaba "Nueva confirmación disponible 1eeaf76... estás implementado en 1eeaf76" - permanentemente, con una redistribución que nunca podría borrarlo. Dos shas ahora nombran el mismo compromiso cuando uno es un prefijo del otro en la abreviatura Floor de git, una referencia que no es un sha en absoluto (una etiqueta, HEAD) se lee como "no puedo decirlo" en lugar de como deriva, y la referencia de una persona que llama se resuelve en el sha completo antes de que algo la almacene o compare, lo que también interrumpe las comprobaciones de confirmación por servicio GitHub rechaza un sha corto y la deduplicación del webhook que ya se está implementando.

11 ago2026v0.6.5CaracterísticasCorreccionesSeguridad73 actualizaciones

Un endurecimiento y liberación de alcance. Los problemas de seguridad reportados se solucionaron (consulte Seguridad a continuación), el canal de control contenedor→host se aprovisiona y se diagnostica de extremo a extremo en lugar de fallar silenciosamente, y OpenShip ahora se instala en cualquier Linux principal y en hosts donde no inicia sesión como root. También agrega openship edge (todo el proxy inverso desde la terminal), límites de recursos reales que respetan la máquina que posee, un shell de producto de correo OpenShip con entrega saliente dividida, correo web reconstruido como una aplicación de catálogo normal y cinco nuevas aplicaciones de un solo clic.

Seguridad

  • Correcciones de seguridad

    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. Se recomienda actualizar.

  • Endurecimiento

    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.

El canal de control del host

  • openship up aprovisiona el canal contenedor → host y le indica cuándo no puede

    When Openship runs in Docker, a handful of operations are genuinely host-level (freeing a foreign proxy off :80/:443, configuración del sistema host, el motor de correo, escritura de la configuración generada por una aplicación de catálogo) y llegan al host a través de SSH en el puente interno. Instalar ahora genera la clave, agrega un restringido from=-fijado authorized_keys línea, verifica que sshd escuche en una dirección a la que pueden llegar los contenedores, abre el puerto en cualquier firewall que ejecute el host y verifica el viaje de ida y vuelta, en lugar de informar el éxito y el error en la primera operación del host semanas después.

  • Sondea cada capa, porque el fallo parece nada.

    This address is host-local, so it traverses filter/INPUT donde un defecto-denegar ufw vidas; Los puertos de contenedores publicados tienen DNAT y lo omiten, que es exactamente la razón por la que el resto de la pila se ve saludable mientras este canal se bloquea. El firewall, la dirección de escucha sshd, la clave y la accesibilidad se analizan y notifican por separado.

  • Una explicación, cinco superficies

    The CLI preflight, the API's boot banner, openship doctor, el banner del servidor del panel y el registro de implementación en el que muere una operación de host se habían dividido en historias diferentes. Ahora leen a partir de un vocabulario compartido, porque cada línea es "su instalación está bien, esta característica no" o "su instalación no funciona", y un operador que lee la incorrecta derriba una caja que funciona o ignora una característica inactiva durante meses.

  • openship update repara un canal no aprovisionado

    An install from before this work, or a raw docker compose instalar, se puede solucionar actualizando, en lugar de volver a ejecutar up y arriesgar el medio ambiente. Una implementación que necesita el canal emite el aviso una vez por implementación, antes del despliegue, en lugar de una vez por servicio.

  • El canal debe ser root, y así lo dice.

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

  • Documentado para instalaciones enrolladas a mano.

    .env.example detalla los cinco pasos (clave, línea restringida de claves_autorizadas, dirección de escucha sshd, regla de firewall, recrear la API porque env_file: se lee en la creación del contenedor) y un nuevo página de solución de problemas camina la reparación.

Cualquier Linux y hosts que no sean root

  • OpenShip se instala en las distribuciones que siempre afirmó tener

    Docker installation was curl get.docker.com | sh en cada Linux, un script que rechaza firmemente a Amazon Linux, AlmaLinux, Oracle Linux y Alpine. Cada sitio de llamadas tenía su propia tabla de administrador de paquetes (había cinco y no estaban de acuerdo), su propia prueba de systemd y su propia lectura de "host fuera de mi lista de permitidos", siempre "nada que hacer". Los datos del host ahora provienen de un detector, los comandos que actúan sobre ellos se encuentran en un módulo y agregar una distribución es un error de compilación en lugar de una falla silenciosa.

  • Un motor Docker en funcionamiento nunca se reemplaza implícitamente

    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.

  • La implementación como usuario no 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 resuelve un diferente $HOME). A un host de comando forzado que no puede informar un uid ya no se le indica que "se conecte como root", que era lo opuesto a su solución.

  • Las cadenas de herramientas de idiomas se instalan por host, no por suposición

    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 en el momento de la construcción.

`openship edge`

  • Todo el proxy inverso, desde la terminal.

    A new top-level command: edge up levanta al apoderado y sirve :80/:443, edge migrate se hace cargo de un nginx/Apache/Caddy existente e importa sus sitios, edge takeover y edge free reclamar los puertos, edge sites enumera lo que se puede importar y edge repair diagnostica por qué no está funcionando (--fix resuelve un conflicto portuario).

  • Dominios, reglas y tráfico sin abrir el panel

    edge domains add app.example.com --port 8080 registra un nombre de host en un puerto y emite un certificado; edge rules gestiona límites de tarifas por ruta, prohibiciones y acceso geográfico/CIDR; y edge traffic, edge analytics y edge logs lea lo que el proxy ya registra. Las operaciones del host son solo Linux; la mitad del plano de control funciona desde cualquier máquina, incluido el escritorio, en cualquier contexto que esté activo.

  • Documentado como referencia y tutorial.

    A new el borde guía para las tareas y un completo referencia de comando.

Límites de recursos

  • Los contenedores autohospedados son ilimitados de forma predeterminada

    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 (sin límite) ahora es el valor predeterminado y cada consumidor prueba un límite antes de aplicar un límite.

  • Una gorra personalizada está limitada por la 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 el socket local y un demonio remoto a través del puente SSH agrupado, recurriendo al sistema operativo cuando no se puede acceder a Docker. La nube no ha cambiado: un espacio de trabajo medido todavía tiene el tamaño de la tabla de niveles.

  • Implementa una verificación previa de la capacidad del objetivo.

    A cap larger than the host can allocate is rejected before any build work starts, with the machine's real numbers in the message.

Correo OpenShip

  • Ejecute la instancia como un producto de correo.

    An instance can present itself as Openship Mail (OPENSHIP_PRODUCT, o un interruptor en Configuración): el carril izquierdo se convierte en el plano de control de correo (las diez pestañas de administración promocionadas a entradas de navegación en tres encabezados, además de las filas de host y configuración que un operador aún necesita) y la navegación de la plataforma está oculta. Esto es solo una presentación, nunca un límite de autorización: el correo web aún se implementa a través de la canalización normal del proyecto, por lo que los puntos finales de la plataforma permanecen activos. La nube es siempre la plataforma completa.

  • Cambiar entre servidores de correo

    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.

  • Los proveedores de retransmisión salientes son identidades reales

    The relay code carried a "ses" | "custom" union, por lo que SendGrid, Mailgun y Postmark perdieron su identidad en el momento en que se guardaron: no se incluye SPF, no hay ida y vuelta en la interfaz de usuario y agregar un proveedor significaba editar un if en el servicio, el generador de DNS y el escáner. Los datos por proveedor ahora son datos que los tres leen, y la entrega dividida (recibir aquí, enviar a través de otra persona) es una configuración de primera clase.

  • "¿El correo realmente sale de este buzón?"

    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.

  • una consola de correo

    Live engine output in the dashboard, so a setup that stalls can be read rather than guessed at.

  • Copias de seguridad que puedes programar

    The mail admin Backup tab gains a real schedule and retention plan, wired to the same pruning the rest of Openship uses.

  • La configuración falla antes y de forma más 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.

correo web

  • Webmail es ahora una aplicación de catálogo normal y corriente

    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.

  • El enlace se almacena, no se analiza a partir de un slug

    The old lookup read webmail-<serverId> salir del slug del proyecto, que el instalador genérico nunca produce y que vinculaba erróneamente cualquier proyecto que alguien llamara "Webmail Prod". Ahora es una clave externa real, anulada (no huérfana) cuando se elimina el proyecto de correo web, con un respaldo heredado que marca la columna la primera vez que resuelve una instalación preexistente.

  • Su propio arranque de imagen y base de datos.

    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 aplicaciones

  • Cinco nuevas aplicaciones con un solo clic

    Meilisearch, Redis, PostHog, Umami and Neon (Postgres), each declaring its internal connection so it can be linked into a project over the internal network.

  • Insignias que te indican lo que estás 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.

  • Actualizaciones del esquema del catálogo

    The published app.schema.json obtiene los campos detrás de lo anterior, y los documentos de referencia y la guía "Agregar una aplicación" se reescribieron en torno a ellos.

Enrutamiento y dominios

  • Una implementación deja de borrar tu vercel.json enrutamiento

    registerRoute reemplaza todo el vhost, por lo que una persona que llama que omitió cleanUrls / redirects / headers No los dejó en paz, los eliminó. Esos campos se construyeron en línea en dos lugares, por lo que una implementación simple no los aplicó ni los conservó, y una redistribución no relacionada borró silenciosamente todo lo que se había instalado en un "Reintento de enrutamiento". Ahora se compilan una vez, en un módulo puro que incluye cada sitio de registro de rutas.

  • Una decisión sobre lo que marca la ventaja

    A single resolver owns the proxy_pass objetivo: un puerto de host de bucle invertido anclado de forma predeterminada (estable durante el reinicio, nunca conectado a Internet), la IP del puente del contenedor como una opción avanzada y un respaldo transparente a la IP del contenedor para un servicio de redacción interno que no publica ningún puerto de host. Seleccionable por instancia, con auto como valor predeterminado.

  • Una redirección de dominio sobrevive a la emisión del certificado

    The redirect installed for a hostname is no longer reverted the moment certbot succeeds, and it no longer re-fires on internal rewrites.

  • IP de clientes reales en el borde

    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.

  • Las reglas de ruta tienen un conjunto de un extremo a otro

    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.

  • Solo tocamos los registros que creamos.

    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

  • Un formulario para agregar 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.

  • Pegue o cargue una clave privada SSH

    ssh_key_path apunta a un archivo en el host API, que es inútil en una instancia remota o VPS donde su clave reside en su propia computadora portátil. Ahora se puede pegar o cargar una clave desde cualquier navegador, almacenarla cifrada en reposo, nunca serializarla nuevamente al cliente y preferirla a la ruta en el disco cuando esté presente.

  • El banner de conexión de la página del servidor se explica solo.

    Reachability, host channel state, and what each one does or doesn't affect, rather than a single red dot.

  • Los valores predeterminados de implementación no se pueden establecer en 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.

Proyectos e implementaciones

  • Cambiar el nombre de un proyecto desde su encabezado

    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.

  • Las acciones del contenedor pasan por una tubería.

    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.

  • La reconciliación y el derribo son más estables

    Record-only deletes, orphan GC scheduling, pending actions and port checks were tightened around the same runtime path.

  • El origen, la compilación y el tiempo de ejecución de un proyecto son tres cosas separadas

    Two boolean flags (hasBuild, hasServer) cada uno representaba dos preocupaciones diferentes, por lo que se podía aceptar un despliegue y luego fallar una etapa más tarde. Un proyecto ahora se describe mediante tres ejes ortogonales: de dónde proviene el código (git, una imagen prediseñada o una carga), cómo se construye (Dockerarchivo, paquete de compilación, estático o nada para compilar) y qué se ejecuta después (web, trabajador o estático), resuelto en un lugar que lee cada etapa. Los proyectos existentes se clasifican exactamente como lo hacían antes.

  • Una aplicación de archivo de repositorio privado Docker se clona nuevamente

    A Dockerfile build runs no buildpack step, so it naturally carried hasBuild=false, y la única puerta que decide si se debe recuperar un token de clonación elimina esa bandera: descartar el token y fallar la clonación en un repositorio privado, aunque el archivo Dockernecesita el repositorio como contexto de compilación. Que el código se obtenga ahora depende sólo de dónde viene, nunca de cómo está construido.

  • Un trabajador es un tipo de implementación de primera clase.

    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 ahora es su propia carga de trabajo: creada como cualquier otra aplicación, se ejecuta como un contenedor que se reinicia siempre sin puerto ni ruta, y verifica si hay un comando de inicio en lugar de un puerto. Elíjalo desde el conmutador Servidor/Trabajador/Estático de un proyecto, o configúrelo workload: worker en openship.json.

Redactar e instalar

  • up conserva tu .env

    A variable you set by hand is kept and marked as yours, instead of being regenerated out of a fixed key list.

  • Un secreto nunca se elimina de una instalación en ejecución

    up detecta que crearía un secreto que ya tiene una instalación existente (lo que dejaría el entorno cifrado indescifrable) y se niega en lugar de reemplazarlo silenciosamente. el reemplazado .env se guarda para su recuperación.

  • Se pueden fijar versiones de imágenes

    An explicit --image-version gana sobre el entorno y la propia versión de la CLI, para el caso en que una versión llega a npm antes de que sus imágenes lleguen al registro.

  • Se rechaza un directorio de datos externo Postgres, no se adopta

    The volume's contents are probed before a cluster is started on top of them.

  • openship doctor y repair cubrir más

    The host channel, an unprovisioned install, and port conflicts, in the same run.

  • La adopción de una pila de Compose ya no vuelve a publicar sus puertos de host

    A migrated 5432:5432 uniría al anfitrión 5432 en el siguiente despliegue y choca con lo que ya lo tenía (a menudo, el propio Postgres de OpenShip), abortando el despliegue. La adopción mantiene únicamente el puerto de contenedores; Se accede al servicio por nombre en la red del proyecto y se vuelve a exponer desde la pestaña Dominios. La advertencia distingue un puerto que se publicó fuera de la caja (la regla de publicación de Docker pasa más allá del firewall del host, por lo que era realmente accesible desde Internet) de uno de solo bucle invertido, para que pueda saber si realmente se abandonó algún alcance externo.

  • stop_signal y stop_grace_period son honrados en la redistribución

    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 SIGKILLeliminado en mitad de la escritura mediante una eliminación forzada inmediata. A container that doesn't opt in still stops the fast way, so there's no added redeploy latency.

Agentes y control de acceso

  • Otorgar a una automatización un shell en un recurso, no en toda la organización

    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) es un shell de host limitado a ese cuadro y una subvención para un proyecto (project:service:write) ejecuta comandos dentro de los contenedores de servicios de ese proyecto, nada más amplio. Cada ejecución se audita con su comando, directorio de trabajo y resultado, y la ejecución del contenedor se rechaza en un tiempo de ejecución que no puede aislarlo.

  • Los agentes de IA obtienen ejecutivos 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.

  • Se puede cambiar el alcance de un editor de acceso y un agente en vivo

    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.

  • Los alcances que siempre podrías aplicar ahora se pueden otorgar

    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.

Escritorio

  • Los despliegues locales están protegidos tras un explícito "próximamente"

    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.

  • Endurecimiento de la carcasa y un actualizador más seguro

    See Security above.

Documentos y sitio

  • Páginas nuevas y reescritas.

    "The edge" guide, the openship edge referencia de comandos, solución de problemas del canal host, una guía reescrita para "Agregar una aplicación" y una referencia del catálogo de aplicaciones, además de notas sobre instalación, actualización y registros/monitoreo.

  • Los documentos obtienen vistas previas sociales

    Generated OG images per page.

  • Una mejor página de registro de cambios

    Entries collapse to headlines and expand to detail, with controls to expand or filter, driven by this file.

Correcciones

  • El inicio de sesión con autenticación cero no hace rebotar un navegador remoto para siempre

    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.

  • La reducción de la retención de correo respeta las copias de seguridad del correo

    Pruning no longer considers a mail engine backup an ordinary project artifact.

  • A migrated container joins the network it's routed on

    A same-server migration attached a container that was never published, leaving it unreachable behind a verified domain.

  • Cancelar una compilación detiene todas las rutas de compilación

    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.

  • Una redistribución de redacción sin operación no se hace cargo de la versión activa

    A redeploy where every service was carried forward unchanged settled without advancing, so it no longer displaces the release that is actually running.

  • Una comprobación de estado almacenada sobrevive al formulario de configuración

    Editing project settings preserved the healthcheck test rather than dropping it, and a NONE La matriz de prueba se lee como deshabilitada en lugar de como un comando.

  • Un vertedero terminado deja de colgar

    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.

  • Un proyecto de archivo Docker no necesita comando

    Projects that rely on the image's own entrypoint deploy without one.

  • Cada nueva cadena se traduce

    The release's new copy landed across all shipped languages, with the parity test extended to the new namespaces.

7 ago2026v0.6.1CaracterísticasCorreccionesBreaking52 actualizaciones

Un gran lanzamiento. Agrega un plano de red completo de servicio a servicio, monitoreo del estado de los contenedores las 24 horas del día y análisis reales con geografía de visitantes e historial de uso, además de un motor de correo en contenedores autónomo, una vista de infraestructura de toda la flota con actualizaciones con un solo clic, un registro de auditoría que puede filtrar y atribuir, alertas de Telegram y un instalador basado en nodos que retira lo último de la clase de fallas de Bun.

Redes de servicio a servicio

  • Ahora cualquier proyecto se puede conectar a otro a través de la red 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>) y se puede elegir como fuente "Usar en un proyecto". Anteriormente, solo se podía acceder internamente a las aplicaciones de catálogo con un bloque de conexión declarado o pilas de redacción multiservicio; un proyecto de aplicación única no tenía ninguna dirección interna. La accesibilidad al mismo límite es automática y el cruce de un límite permanece explícito: un alias solo se vuelve accesible una vez que se vincula a un consumidor a la red. Solo autohospedado y omitido para sitios estáticos (sin puerto de escucha) y aplicaciones alojadas en la nube (que en su lugar se vinculan a través de Público).

  • Dar a un servicio un nombre 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.

  • Un editor de configuración de servicio más 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.

Estado e incidentes de los contenedores

  • OpenShip vigila tus contenedores las 24 horas del día, no solo durante la implementación

    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.

  • Los contenedores rotos te avisan una vez, no 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, o un proyecto deshabilitado nunca activa una falsa alarma.

  • Un servidor inaccesible es una alerta, no una por aplicación

    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.

  • Una pestaña de Salud en cada proyecto, con 30 días de historial 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álisis y uso de recursos

  • Vea de dónde vienen sus 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.

  • Los recuentos de visitantes ahora son números reales, no recuentos de solicitudes

    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.

  • Rutas principales y códigos de respuesta que tienen datos reales detrás

    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.

  • Se conserva el historial de uso, para que pueda ver qué provocó un fallo

    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.

  • Busy domains keep their analytics

    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.

  • Los análisis ya no desaparecen silenciosamente cuando nadie está mirando

    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.

  • La información sobre herramientas de gráficos se puede leer en todos los 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.

Proxy perimetral y inverso

  • Ajuste el proxy inverso por proyecto

    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.

  • Los análisis por país y las reglas nacionales funcionan en el borde de los contenedores

    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.

  • Corregir la identidad del visitante detrás de Cloudflare o un 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 solo en los rangos publicados de Cloudflare como par de conexión.

  • Las reglas por ruta llegan al borde incluso cuando no está en el loopback de la 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.

  • La píldora "Edge ready" coincide con el estado real del 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.

Dominios personalizados y gratuitos

  • Gratis .opsh.io Los dominios solo se dirigen a un servidor cuyo control usted ha demostrado.

    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.

  • Los dominios gratuitos y personalizados ahora funcionan en sitios estáticos

    Adding a free .opsh.io dominio a un proyecto estático utilizado para registrar nada en el borde, por lo que la URL pasó al comodín sin origen detrás; La edición del dominio de un proyecto estático no escribió ningún vhost hasta la próxima implementación. Ambos ahora emiten una ruta real en el instante en que guarda, entregando los archivos creados del proyecto, el mismo comportamiento que ya tenían las aplicaciones proxy.

  • Un certificado que se emitió pero luego tuvo un problema ya no se pierde

    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.

  • Los dominios personalizados no válidos se rechazan en la puerta

    Setting a custom domain to something that isn't a public hostname (localhost, una IP simple, una etiqueta única o un valor con una ruta/puerto/esquema) utilizado para devolver el éxito, generar una fila de dominio pendiente inactivo e incluso escribir un server_name localhost; vhost en el borde compartido. Las rutas de escritura ahora validan los nombres de host personalizados y rechazan los incorrectos, al tiempo que permiten que un proyecto que ya tiene un valor incorrecto lo edite y lo elimine.

  • Editar un dominio gratuito ya no muestra un falso "Acción requerida"

    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.

  • Los redireccionamientos y los límites de carga entran en vigor al guardar

    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.

Correo electrónico

  • El correo se ejecuta como un motor autónomo en lugar de hacerse cargo de su 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 contenedor con su base de datos vmail en un sidecar Postgres, conectado en red al host, por lo que el correo aún ve las IP de los clientes reales y el borde permanece fuera de la ruta de datos del correo. La configuración se reduce a ocho pasos cuyos únicos requisitos previos son Docker y openship edge, y cada parte del estado del correo (cola, maildirs, claves DKIM, configuración) reside en montajes de enlace del host, por lo que la actualización es una extracción y recreación que conserva sus datos. Solo autohospedado.

  • Mail usa el mismo borde y TLS que todo lo demás

    Mail setup no longer stands up its own host OpenResty and certbot on the side. The certificate for mail.<domain> se emite a través del borde abierto compartido, la misma ruta que toma el TLS de todos los demás dominios, y ahora se registra para renovación como cualquier otro dominio: un certificado de correo en un borde contenedorizado (sin temporizador de certbot de host) solía caducar ~90 días después de la instalación, de forma silenciosa; una renovación fallida ahora genera una notificación.

  • Los servidores de correo configurados antes de la contenedorización siguen 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.

Infraestructura remota

  • Vea cada borde administrado y contenedor de correo en un solo 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.

  • Actualizar, reparar o instalar un contenedor sin tocar un caparazón

    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.

  • Actualice automáticamente su infraestructura remota al actualizar

    A new instance-wide toggle lets the control plane update every remote edge and mail container automatically when you upgrade Openship (its APP_VERSION avanza), por lo que la infraestructura de su flota rastrea la versión que está ejecutando sin barrido manual. Está del lado del servidor, por lo que también funciona en el escritorio, a diferencia de la actualización automática de la aplicación de escritorio, y está desactivado de forma predeterminada. Solo autohospedado.

  • La detección de deriva se mantiene actualizada por sí sola

    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.

  • Las cajas heredadas ya no se marcan como rotas

    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 migración

  • Los sitios migrados mantienen el límite de carga y los tiempos de espera bajo los cuales se ejecutaron

    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.

  • La adopción de una pila ya no vuelve a publicar los puertos internos

    A compose service that published a container port on a random host port (a single-part ports: entrada, p.e. el 5432 de una base de datos (la fuente nunca estuvo realmente expuesta) ahora no se expone durante la adopción en lugar de volver a publicarse en el destino, por lo que una migración no expone innecesariamente los servicios internos ni choca con lo que ya tiene un puerto de host. El puerto todavía se muestra en el asistente para que pueda enrutarlo y el tráfico de servicio a servicio sigue resolviendo por nombre a través de la red compartida. Solo autohospedado.

  • El asistente le indica qué variables de entorno no se transfirieron

    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.

  • No más nombres de host fantasmas en el asistente de importación

    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 auditoría

  • Vea exactamente lo que cambió su asistente de IA

    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.

  • Desactive la auditoría y controle cuánto tiempo se conserva

    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.

  • Una verdadera barra de filtro sobre el registro.

    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.

  • La paginación del registro ya no salta ni repite filas

    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.

Notificaciones

  • Enviar alertas a 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.

  • La configuración de notificaciones autohospedada elimina los botones que nunca pueden activarse

    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 y empaquetar

  • OpenShip ahora se instala y actualiza en Node, nunca en un Bun global

    El curl | sh y los instaladores de PowerShell descargan una carga útil CLI autónoma y verificada por sha256 que se ejecuta en Node: usan su sistema Node 22+ si tiene uno y, de lo contrario, venden un Node 22 oficial de nodejs.org en ~/.openship, y te migran silenciosamente desde cualquier instalación anterior de Bun global sin tocar tu propio Bun. openship update toma el mismo camino: volver a descargar la carga útil verificada, actualizar el tiempo de ejecución primero, para que una actualización que eleve el piso del nodo se recupere a sí misma en lugar de romperse. Esto retira la clase de bloqueo Bun-vs-ssh2 que podría eliminar operaciones SSH remotas.

  • El servidor de correo se envía como imagen 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 con la API, el panel y las imágenes de borde, por lo que ya no es necesario crear un motor de correo autohospedado desde el origen.

  • openship up ahora funciona bajo Docker sin raíz en lugar de fallar crípticamente

    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 ejecutar (#372).

Implementaciones y redacción

  • Una implementación en funcionamiento nunca se registra como fallida

    Build output that carried a raw NUL byte or a broken Unicode character (as a failed docker exec hace cuando derrama su flujo multiplexado, encabezados de marco y todo) hizo que la escritura del registro fallara y OpenShip leyó mal esa escritura rechazada porque la implementación en sí falló: una implementación en vivo y en ejecución fue marcada como fallida y sus contenedores derribados, mientras que la vista de implementación permaneció bloqueada en "Implementación". Los registros de compilación almacenados ahora se desinfectan y tienen un tamaño limitado, la escritura del resultado elimina cualquier registro o blob de error Postgres que se rechace en lugar de perder el estado, y el evento terminal que cierra la transmisión en vivo siempre se activa.

  • Su URL de acceso y sus puertos de dominio personalizados sobreviven a una nueva implementación

    A project's deploy target is now stored durably on the project itself (a new server_id columna) en lugar de vivir solo en los metadatos volátiles de la última implementación. Antes, una instantánea nueva o parcial podía perder ese enlace, hacer una regresión silenciosa del proyecto a una implementación local, eliminar los puertos de sus dominios personalizados (un 502) y restablecer la URL de acceso a localhost:3000; Los proyectos existentes alojados en el servidor se reponen para que esto no pueda afectarlos en la próxima redistribución. Un dominio personalizado verificado también se conserva en lugar de eliminarse o borrarse incluso cuando el conjunto de puntos finales de una implementación lo omite. Solo autohospedado.

  • Una instalación de dominio gratuito ahora tiene un objetivo de implementación

    A box set up with a free .opsh.io El dominio podría finalizar la incorporación sin servidores en la lista y sin nada en qué implementar, porque el registro de la fila local "Este servidor" colgaba de un paso de arranque que esa ruta nunca se ejecuta. El cuadro ahora materializa su propia fila de destino de implementación cuando los servidores aparecen por primera vez, cuando se conecta a OpenShip Cloud y al restablecer el administrador. Adjuntando un gratis .opsh.io El dominio a un proyecto más tarde ya no necesita una nueva implementación primero, ya que cada implementación ahora prepara la casilla para responder a la verificación de propiedad. Solo autohospedado.

  • Los dominios de servicio respetan su límite de carga y configuración 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.

  • Las URL del servicio de aplicaciones de catálogo se resuelven por puerto y nunca están en blanco

    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="", o un 127.0.0.1 que dentro de un contenedor apunta al propio contenedor). Cada puerto ahora se resuelve de forma independiente, un servicio de solo puerto vuelve al alcance real de la caja. http://host:port, y un {{publicUrl:…}} El token que aún no se puede resolver se deja sin configurar, por lo que se aplica el valor predeterminado de la imagen, con una advertencia fuerte en el registro de implementación en lugar de un espacio en blanco silencioso.

  • La advertencia de enrutamiento le indica cuándo el borde es el 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 actualización: esta versión supera las versiones de imagen de correo y de borde fijado. En el modo autohospedado, abra la nueva vista Infraestructura para actualizar el borde de cada servidor y el contenedor de correo en la imagen fijada, o active la actualización automática en toda la instancia para que el plano de control lo haga en cada actualización.

31 jul2026v0.5.0CaracterísticasCorrecciones25 actualizaciones

La reversión se reconstruye para que realmente restaure una versión, además de una ronda de correcciones en la integración de MCP y los dominios personalizados.

Revertir

  • Revertir cualquier versión, en cada proyecto

    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.

  • Una versión restaurada vuelve 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.

  • Revertir pilas de composición por servicio

    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.

  • Los sitios estáticos revierten sus archivos

    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.

  • La restauración nunca interrumpe la versión en la que estás

    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.

  • El historial de reversión se adapta al 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.

  • La configuración se movió junto a las copias de seguridad.

    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.

  • Establece la retención mientras aún estás eligiendo el 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 es en su proyecto (archivos creados para un sitio estático, imágenes en caso contrario) en lugar de hablar de imágenes de cualquier manera.

  • El panel Avanzado del asistente dice lo que contiene

    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.

  • Cambiar la configuración de retención se aplica a las versiones existentes

    It used to be frozen onto each deployment as it was created, so turning on instant rollback did nothing for anything already deployed.

Correcciones encontradas al reconstruir la reversión

  • Las versiones anteriores no se pudieron implementar ni restaurar en absoluto

    A release whose configuration snapshot predated the "production paths" setting crashed the deploy pipeline outright. This affected plain redeploys too, not just rollback.

  • Ya no se rechaza una restauración por falta de configuración de compilación

    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.

  • Registry-image-only projects can deploy again

    A stack adopted from a Docker migration has no git repository and needs none, but deploys were refused for not having one.

  • Compose implementa un registro de qué servicio ejecutó qué imagen

    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.

  • Un campo de historial de reversión borrado ya no significa "no conservar nada".

    An empty value now falls back to the default instead of purging every restorable release.

  • Se puede acceder a Docker fuera de Docker escritorio

    Local deploys honor DOCKER_HOST (y una ruta de socket explícita) en lugar de asumir /var/run/docker.sock, para que funcionen Colima, Rancher Desktop, Podman y rootless Docker.

Nota de actualización: esta versión elimina un no utilizado artifact_retained_at columna de la tabla de implementación por servicio. Nada lo leyó ni escribió.

MCP

  • Flujos de implementación guiados

    The MCP server now ships a prompt catalog (deploy-from-git, deploy-a-folder, install-catalog-appy una descripción general de la orientación) para que un cliente de IA siga la secuencia de herramientas correcta en lugar de realizar ingeniería inversa a partir de una lista plana. Sus herramientas de escritura ahora llevan cuerpos de solicitud escritos de un extremo a otro (proyectos, implementaciones, dominios, webhooks, notificaciones, conexiones, aplicaciones) y cada mensaje apunta a github.com/oblien/openship/issues cuando un cliente encuentra un error en la plataforma.

  • Los tokens con alcance enumeran las herramientas adecuadas

    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, por lo que un token con alcance no vio nada con qué funcionar.

Dominios personalizados

  • www es su propio dominio, no un apego al suyo

    "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 de la misma operación, sin vigilancia: a www que aún no apuntaba al servidor falló después the apex had already succeeded, and the apex was reported as broken. Adding a domain with the switch on also showed you only the apex's DNS record, so www nunca se resolvió, su certificado nunca pudo emitirse y cada implementación reintentó un nombre de host que había sido configurado para fallar. Ambos nombres de host ahora obtienen su propio registro DNS, su propio botón Verificar, su propio certificado y su propio error.

  • Redirigir un dominio a otro

    Any domain can now answer a 301 (or 302) to another domain of the same project, set on the domain's card. www lo usa por defecto (www.example.com → example.com), y la dirección es tuya para girarla o apagarla. Los movimientos de dominio antiguo a dominio nuevo funcionan de la misma manera. La ruta y la cadena de consulta se conservan, el host de redireccionamiento aún obtiene su propio certificado y se rechaza un destino fuera del proyecto (o un redireccionamiento que se repetiría).

  • Verificar mantiene el registro cuando falla

    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.

  • Una ejecución finalizada deja de informarse como fallida

    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.

  • Dos dominios en un servidor ya no pelean por los certificados

    Certificate issuance is serialized per server, not just per hostname. www hizo que dos dominios pendientes fueran el caso normal, y una verificación manual podría colisionar con el reintento en segundo plano que funciona en el hermano: ambos ejecutaron certbot, ambos querían el mismo puerto de desafío y uno falló con un error que se leía como un problema de DNS.

  • El registro A muestra la IP de su 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.

  • Guía correcta de DNS autohospedado

    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 jul2026v0.4.7CaracterísticasCorrecciones7 actualizaciones

La historia de autohospedaje de CLI está finalizada, las migraciones remotas Docker se vuelven confiables y un lote de correcciones llega al plano de control para una versión más estable.

Interfaz de línea de comandos

  • Una instalación finalizada abre el panel de control, no el asistente de configuración

    Bare openship (y la fuente openship-dev) ahora reconoce una instalación de Compose Docker (el valor predeterminado en Linux). Volver a ejecutar después de la configuración administra la pila en ejecución en lugar de guiarlo nuevamente a través del nombre/correo electrónico/dominio desde cero.

  • Panel de control Iniciar / Detener / Reiniciar la unidad real

    On a compose install these now run docker compose up -d / restart / down y leer el estado real de la pila, en lugar de apuntar a una unidad systemd que nunca se instaló (que informó "detenida" para una pila en buen estado).

Migraciones y control remoto Docker

  • El puente SSH → Docker ya no se bloquea ni produce un error falso en un servidor en buen estado.

    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 en una nueva conexión cuando un canal se abre muerto. Contribuido por @jbermudez00 (#271).

correo

  • La configuración del servidor de correo funciona desde la aplicación de escritorio

    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 fallo en la instalación.

Correcciones

  • La conexión autohospedada de GitHub es de token primero

    A remote (VPS) instance pastes an access token inline in the Library, with no gh auth login pistas; la ruta de la CLI de gh ahora es solo de escritorio, donde pertenece.

  • El asistente de implementación llega directamente a la configuración

    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.

  • El plano de control deja de incluir un servicio fantasma

    The self-managed "Openship" project no longer shows a bogus public openship servicio (y sus extraviados openship-openship.opsh.io ruta) que no coincidía con ningún contenedor y decía "Detenido" para siempre.

27 jul2026v0.4.0CaracterísticasCorreccionesSeguridad8 actualizaciones

Una solución de seguridad para el borde, migraciones que se comportan como un proyecto de repositorio nativo y un lote de correcciones de enrutamiento/confiabilidad.

Seguridad

  • Los hosts HTTPS no enrutados se rechazan, no se realizan servicios cruzados

    The edge now owns a 443 servidor predeterminado que rechaza cualquier nombre de host que no enrute (uno que usted eliminó, nunca agregó o simplemente señaló la IP del cuadro). Antes de esto, dicha solicitud no llegaba al primer host virtual cargado y se atendía. el certificado y el backend de otra aplicación. Se aplica automáticamente en la siguiente implementación, tanto en el borde simple como en el contenedor. Crítico: consulte el aviso en la aplicación.

Migraciones

  • Un proyecto migrado ahora es un proyecto de repositorio nativo

    A migrated compose stack redeploys like any repo project: it reclones and reconstruye build: servicios y tira image: unos, en lugar de fallar en una etiqueta de compilación congelada (404 no such image). La imagen en ejecución solo se reutiliza una vez, en el momento del corte.

  • Todo el conjunto es el plan de implementación.

    The migrate screen lists every repo compose service, not just running containers, so a service with no container (e.g. redis, o una aplicación que no estaba activa) se crea/extrae y se enruta como el resto, con su entorno y ruta editables en la tarjeta.

  • Las bases de datos reutilizadas permanecen accesibles

    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 nombre, exactamente como una implementación nativa.

  • Un servicio migrado informa el contenedor como realmente se ejecuta

    Service state is read live from the host and matched by identity (label → openship-<slug>-<svc> nombre → ID de seguimiento → redactar etiquetas), por lo que se adoptó un contenedor OpenShip en su lugar (las etiquetas de su ventana acoplable todavía nombran el proyecto anterior) ya no muestra "Detenido" mientras atiende tráfico. El registro de cada ejecución ahora termina con el contenedor, el estado y la coincidencia de cada servicio.

Correcciones

  • El estado del servicio nunca se adivina a partir de la base de datos.

    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 — o, en Inicio, iniciar un duplicar container beside the running one. A crash-looping container now reads Reiniciando en lugar de un "En ejecución" verde y se lee un host inalcanzable Desconocido en lugar de hacer eco del último estado de implementación.

  • Eliminar una ruta nunca exige incorrectamente 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.

  • Eliminar un servicio no se puede bloquear

    Runtime teardown is time-bounded, so a slow or unreachable server no longer strands the delete before the record is removed.

22 jul2026v0.3.0CaracterísticasCorreccionesSeguridad13 actualizaciones

Compilaciones nativas de Apple Silicon, compatibilidad directa con la configuración de implementación de otras plataformas y un lote de correcciones de confiabilidad y autohospedaje.

Descargas

  • Aplicación de escritorio nativa de Apple Silicon (arm64)

    MacOS now ships separate brazo64 e intel x64 dmgs (tanto integrados como con suma de comprobación SHA-256 en CI), por lo que los Apple Silicon Macs se ejecutan de forma nativa en lugar de bajo Rosetta. Windows (x64) y Linux (AppImage) no cambian.

Implementar · detección de pila

  • Implementa repositorios ya configurados para otra plataforma, tal cual

    The stack detector now reads railway.toml/railway.json y vercel.json (comandos de compilación/instalación/inicio/salida, marco y enrutamiento) y los pliega sobre su propia detección. Un repositorio que ya le dice a Railway o Vercel cómo compilarlo se implementa aquí de la misma manera, sin reconfiguración. Cada fuente de configuración se ejecuta a través de un registro de analizador compartido (sin mayúsculas y minúsculas especiales por fuente).

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

Autohospedaje

  • Se implementa en su propio servidor de forma predeterminada

    A self-hosted instance targets the server it runs on, never Openship Cloud, unless you explicitly choose cloud.

  • Los controles de salud funcionan cuando el avión de control está en contenedores.

    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 se instala en distribuciones más nuevas

    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.

Interfaz de línea de comandos

  • openship stop en realidad se detiene

    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.

Fiabilidad y correcciones

  • Los cuerpos de solicitud JSON con formato incorrecto ahora regresan 400, no 500.
  • Cloud static-output path is confined

    The Pages output path resolves through one shared, sandboxed resolver so a build can't escape its output dir.

  • Escaneo de DNS de correo detecta registros DMARC duplicados.
  • Los metadatos de descubrimiento de OAuth se entregan correctamente detrás de una URL pública.
  • Flujos ejecutivos SSH cerrar limpiamente en el tiempo de espera en lugar de gotear.
  • Se ha producido un problema con el despliegue de Laravel. dispositivo de prueba fuera de un vulnerable laravel/framework (CRLF email advisory)

    A fixture only, never a shipped dependency.

22 jul2026v0.2.2CaracterísticasCorrecciones12 actualizaciones

Las aplicaciones y los trabajos crecen, un servidor autohospedado ahora puede comunicarse con GitHub por sí solo, las copias de seguridad obtienen un hogar real y un lote de correcciones de confiabilidad de eliminación/inicio de sesión/base de datos.

Aplicaciones

  • Configuración de la aplicación del día 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.

  • Asistente de instalación limpia por aplicación

    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 es una aplicación de primera clase

    It appears in the catalog alongside Convex and n8n and hands off to the mail wizard. The rest of the catalog shows as Próximamente (atenuado, no instalable) para esta versión.

Empleos

  • Las copias de seguridad automáticas aparecen en Trabajos

    (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

  • Conectar GitHub en un servidor

    Each self-hosted server now authenticates to GitHub on its own, from a dedicated GitHub pestaña: inicie sesión con un código de dispositivo (como gh), pegue un token, genere una clave SSH para agregarla a su cuenta o use el registro automático de solo lectura por repositorio implementar claves. Las credenciales se almacenan cifradas y exactamente el mismo panel de conexión se reutiliza dentro del flujo de implementación, por lo que una credencial faltante se puede solucionar con un solo clic en mitad de la implementación. Los clones de repositorios privados ahora funcionan sin que su escritorio esté en línea.

Copias de seguridad

  • Copias de seguridad rediseñadas

    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.

nube

  • Límite de proyecto por usuario

    Openship Cloud enforces a hard cap on projects per user (env CLOUD_MAX_PROJECTS_PER_USER, predeterminado 2), tanto en la creación como en la carga/aseguración de carpeta. El alojamiento propio no está medido.

Fiabilidad y pulido

  • Las eliminaciones nunca se atascan

    Project deletion shows a real Eliminando estado, y cuando el desmontaje de la fuente no se puede completar, obtienes una limpieza "Eliminar del almacenamiento" opción que descarta el registro inmediatamente (GC recupera los recursos sobrantes más adelante). La eliminación atómica, todo o nada, sigue siendo la predeterminada.

  • Solución de inicio de sesión en el escritorio

    The login redirect now lands on the same loopback host the session cookie was minted on (localhost ⇄ 127.0.0.1), por lo que el panel ya no se abre sin cookies y lo devuelve a /login.

  • Puesta en marcha de base de datos integrada

    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.

  • Tematización más tranquila y 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 acción y un ícono distinto por mosaico de "lo que se configura".

20 jul2026v0.2.0CaracterísticasCorrecciones11 actualizaciones

Una versión de gran funcionalidad y refuerzo en todo el flujo de implementación, el catálogo de aplicaciones, el enrutamiento, los servidores, los trabajos y la cadena de herramientas de compilación.

Implementar

  • Rediseñado "¿Dónde quieres desplegarte?" step

    Unified page-style header with the Continuar acción alineada con la columna de configuración, y una selector de servidor colapsado y con capacidad de búsqueda (con un "Agrega tu propio servidor" en línea).

  • Corrección de la cadena de herramientas del administrador de paquetes

    Pnpm/yarn are now enabled via corepack en cada ruta de compilación (nube, archivo Dockergenerado, host básico, preparación del espacio de trabajo de monorepo, compilación local en la nube). Correcciones pnpm: not found en el despliegue.

Aplicaciones

  • Catálogo de aplicaciones de un solo clic con pestañas de categorías y búsqueda

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

  • Tarjeta de inicio "Aplicaciones" actualizada; Las tarjetas de catálogo muestran logotipos de marcas reales.

Enrutamiento y dominios (única fuente de verdad)

  • Dominios personalizados en proyectos basados en servicios 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 rediseñada (pestañas, accesibilidad en vivo, banderas 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.

Empleos

  • Ganancias en la página de empleos buscar + un vistazo barra lateral del filtro de estado (en ejecución/fallido/programado/deshabilitado), se muestra una vez que existen trabajos personalizados.

Equipo y espacio de trabajo

  • Invitar miembro

    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.

Agregar servicio

  • El OpenShip Cloud La pestaña de imagen muestra una CTA "Conectar a OpenShip Cloud" cuando la instancia no está vinculada y el conmutador de fuente tiene un contraste más claro.

Otro

  • Docker flujo de migración, copias de seguridad por proyecto/servicio, comprobaciones de conectividad unificadas, localización en árabe (RTL), página de hoja de ruta de marketing y pulido de ventanas de escritorio (macOS recuadro de semáforo).