3 nov.2026v0.9.9CaractéristiquesCorrectifsSécurité27 mises à jourCopier le lien
Sécurité
Dépendances d'authentification
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.
Compatibilité OAuth et connexion
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.
Approbation de la connexion au cloud
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.
Identité du client et limites
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.
Isolement du serveur
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 crypté
Require TLS for authenticated mail delivery, including verified STARTTLS on submission ports. Refuse a plaintext fallback when the server cannot provide the required encryption.
Catalogue Umami
Update the PostgreSQL image to 2.20.2 and verify the catalog's configuration remains compatible.
Avis de sécurité et maintenance de l'hôte
Correctifs hôtes examinés
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.
Entretien 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.
Préférences consultatives
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.
Déploiements et prise en charge des hôtes
Rédiger un examen des sources
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.
Constructions Git épinglées
Fetch a requested commit even when it is outside the cloned branch. Improve submodule preparation and credential handling across local and remote build paths.
Récupération de bord
Preserve unreadable virtual-host configurations during cleanup, and avoid identifying similarly named application containers as the OpenShip edge.
Hôtes de la grande famille
Use pacman for Arch/Manjaro package preparation and component version checks instead of Debian commands.
Nouvelles données GeoIP
Refresh and validate the country database before creating release tags, with a scheduled refresh workflow for ongoing updates.
Vérification de la version
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.
Cloud, facturation et email
Récupération de paiement
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.
Escalade du provisionnement
Send exhausted provisioning failures to support once, retaining the recovery context without duplicate escalation.
E-mails clients
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.
Conseils sur le forfait cloud
Update the public plan descriptions and Hobby plan guidance, and make plan-selection hints more compact in the dashboard.
Assistants et tableau de bord
Découverte de modèles connectés
List models through the connected assistant runtime and MCP, keeping connection setup and agent selection consistent.
Agents sur serveurs Cloud payants
Prepare and run agents on an existing paid instance while preserving host access checks, profiles and sign-ins.
Activité d'outil compact
Keep routine assistant lookups inline, with detailed previews available when useful instead of expanding every tool result into a card.
Domaines et références
Simplify domain actions and plan guidance. Use consistent referral wording across the dashboard and website, and place referral code entry below the plan controls.
Notes de mise à niveau
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)paires de comptes avant la mise à niveau depuis Better Auth 1.6.- Remplacer l'auteur
container:références d'espace de noms avecservice:<name>pour un service dans la même pile. Les montages de liaison d'hôte sont désactivés par défaut. Les opérateurs d'instances auto-hébergées de confiance peuvent explicitement activerOPENSHIP_ALLOW_HOST_BIND_MOUNTS=true; Les montages d'hôtes cloud restent restreints. - SMTP authentifié doit prendre en charge TLS/STARTTLS vérifié. Configurez un point de terminaison de soumission compatible TLS si le point de terminaison précédent acceptait uniquement la livraison en texte brut.