← Журнал изменений

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 выпуск
6 нояб.2026v0.9.11ОсобенностиИсправленияБезопасность31 обновлений

Помощники и рабочий стол

  • Вход в Кодекс на размещенных экземплярах

    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.

  • Восстановление учетной записи рабочего стола

    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.

  • Клод Код на macOS

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

  • Расследования и вопросы

    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.

  • Настройка рабочего места помощника

    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.

Развертывания, маршрутизация и безопасность

  • Создание обновлений команд

    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.

  • Окружающая среда применяет сбои

    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.

  • Статические изменения окружающей среды

    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.

  • Статическое поведение ошибки 404

    Add an explicit SPA fallback setting to shared routing controls, the API and openship.json. Оставьте резервный вариант SPA включенным по умолчанию; его отключение возвращает реальные ответы 404 и использует 404.html когда доступно.

  • Составьте краевой инвентарь

    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.

  • Сканирование частного репозитория

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

  • Припаркованный импорт Docker

    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.

  • Границы облачного хоста

    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.

  • Условные проверки безопасности

    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.

  • Конфликты удаления базы данных

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

Каталог почты и приложений

  • Управление фейл2баном

    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.

  • Прямые отправители псевдонимов

    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.

  • Настройка записи приложения

    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.

  • Проверка обновления безопасности

    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.

  • Супабазные изображения

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

  • Готовность RabbitMQ

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

Панель управления, выставление счетов и документация

  • Восстановление темы

    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.

  • Возврат кассы

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

  • Сбои шлюза

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

  • Аналитика первого развертывания

    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.

  • Формулировка быстрого старта

    Remove an abrupt line break in the setup description.

Примечания к обновлению

  • Обновите API (включая все реплики), панель мониторинга и настольное приложение вместе. Этот патч не добавляет новой миграции базы данных уровня управления.
  • Если более старая версия настольного компьютера уже отображает только локального пользователя и не имеет сохраненной аутентифицированной личности, используйте «Назад к настройке», «Продолжить с облаком» и войдите в систему один раз. Это сохраняет существующие данные и записывает владельца для будущего восстановления.
  • Примените изменения в политике отправителей с прямым псевдонимом, обновив образ управляемого почтового механизма, а также плоскость управления. Пользовательские политики SQL и собственные почтовые политики хоста остаются под управлением оператора.
  • Повторно разверните существующий созданный контейнер статического сайта после изменения его резервной настройки SPA. Существующие сайты сохраняют поведение SPA до тех пор, пока оно не будет явно изменено.
  • 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.