← Journal des modifications

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.

1 version
6 nov.2026v0.9.11CaractéristiquesCorrectifsSécurité31 mises à jour

Assistants et bureau

  • Connexion au Codex sur les instances hébergées

    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.

  • Récupération de compte de bureau

    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.

  • Code Claude sur macOS

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

  • Enquêtes et questions

    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.

  • Configuration de l'espace de travail de l'assistant

    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.

Déploiements, routage et sécurité

  • Composer des mises à jour de commandes

    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.

  • Échecs d’application de l’environnement

    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.

  • Changements d'environnement statiques

    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.

  • Comportement statique 404

    Add an explicit SPA fallback setting to shared routing controls, the API and openship.json. Gardez la solution de secours SPA activée par défaut ; le désactiver renvoie de vraies réponses 404 et utilise 404.html lorsqu'il est disponible.

  • Composer un inventaire périphérique

    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.

  • Analyses du référentiel privé

    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.

  • Importations Docker parquées

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

  • Limites des hôtes cloud

    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.

  • Examens de sécurité conditionnels

    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.

  • Conflits de suppression de base de données

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

Catalogue de courrier et d'applications

  • Gestion Fail2ban

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

  • Expéditeurs d’alias directs

    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.

  • Configuration de l'écriture d'application

    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.

  • Vérification de l'actualisation de la sécurité

    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.

  • Images Supabase

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

  • Préparation de RabbitMQ

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

Tableau de bord, facturation et documentation

  • Restauration du thème

    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.

  • Retours à la caisse

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

  • Pannes de passerelle

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

  • Analyses du premier déploiement

    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.

  • Formulation de démarrage rapide

    Remove an abrupt line break in the setup description.

Notes de mise à niveau

  • Mettez à jour l'API (y compris toutes les répliques), le tableau de bord et l'application de bureau ensemble. Ce correctif n'ajoute aucune nouvelle migration de base de données du plan de contrôle.
  • Si une ancienne installation de bureau affiche déjà uniquement l'utilisateur local et n'a aucune identité authentifiée enregistrée, utilisez Retour à la configuration, Continuer avec le cloud et connectez-vous une fois. Cela préserve les données existantes et enregistre le propriétaire pour une récupération future.
  • Appliquez les modifications apportées à la stratégie d’expéditeur d’alias direct en mettant à jour l’image du moteur de messagerie géré ainsi que le plan de contrôle. Les politiques de messagerie SQL personnalisées et natives de l'hôte restent gérées par l'opérateur.
  • Redéployez un conteneur de site statique généré existant après avoir modifié son paramètre de secours SPA. Les sites existants conservent le comportement SPA jusqu'à ce qu'ils soient explicitement modifiés.
  • 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.