← Registro de cambios

v0.9.11

Recommended update for Desktop sign-in recovery, assistant connections, repository scans and deployment reliability. Includes every change merged into main since 0.9.10, with mail administration improvements and clearer runtime security updates.

Lanzamiento de 1
6 nov2026v0.9.11CaracterísticasCorreccionesSeguridad31 actualizaciones

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.