← Registro de cambios

v0.5.0

Rollback is rebuilt so it actually restores a release, plus a round of fixes across the MCP integration and custom domains.

Lanzamiento de 1
31 jul2026v0.5.0CaracterísticasCorrecciones25 actualizaciones

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.