17 oct.2026v0.9.3CaractéristiquesCorrectifs25 mises à jourCopier le lien
Automatisation du déploiement et aperçus
Déplacer les variables de commande dans l'environnement
Review literal environment assignments in install, build and start commands, then migrate them into encrypted project or service settings. Conflicts and concurrent edits stop the migration before partial changes are saved. Import and saved settings share the same parser and guidance.
Préparer automatiquement la sortie du framework
Next.js standalone monorepos and Nuxt builds retain their required workspace dependencies, public/static assets and selected Node or Bun runtime. Managed direct-server defaults start from the configured app directory; explicit custom commands retain their working directory.
Examiner les anciens montages manuels du cache
Detect duplicate package/framework cache mounts and offer configuration migration only after a successful build proves managed cache support for those paths. Existing volume data is retained. Build logs report observed cache reuse and build-time comparisons.
Détecter les problèmes de configuration plus tôt
Pre-install checks identify missing app roots and environment examples; command-variable, standalone startup and duplicate-mount guidance explains what needs attention without exposing variable values.
Activer GitHub aperçus des demandes d'extraction
Same-repository, non-draft pull requests can deploy their exact commit into a separate preview environment with preview-only variables, isolated volumes and per-service URLs. Production variables are not copied. Forks and unsafe shared-storage configurations are excluded.
Récupérer les opérations du cycle de vie de prévisualisation
Durable coordination handles repeated webhooks, controller restarts and retryable close/merge cleanup. Optional GitHub comments update one existing comment, alongside the existing deployment Checks. Whole-instance transfers preserve preview ownership; individual project imports clear preview automation that cannot safely transfer.
Utiliser l'automatisation du SDK
Configure and list previews, inspect or migrate manual cache mounts, and move command variables through the shared validated project operations.
Travailleurs, planificateurs et restauration
Configurer les rôles sans reconstruire l'application Web
Apps & Services → Configure roles can add or change workers and singleton schedulers on active single-app self-hosted Docker deployments. The normal deployment engine reuses the verified image and frozen environment while preserving the web container and unchanged replicas. The API, SDK and CLI expose the same operation. Cloud, bare, static, cluster and multi-service targets are outside this editor's scope.
Voir et inspecter les processus en arrière-plan
Runtime roles appear in project service views and topology, with role/replica log selection and retry states. Health monitoring includes worker and scheduler failures instead of observing only the foreground container.
Gardez les suggestions de rôles indépendantes
Framework scans expose matching presets at the selected app root. Only presets competing for the same declared slot exclude one another; explicit roles, including an empty list, retain precedence. Suggestions do not automatically enable background processes.
Récupérer les transferts de rôles interrompus
Persist exact container identities and ownership before replacement, predecessor shutdown and publication. Startup and deployment reconciliation either finish a published handover or safely restore its predecessor; uncertain cleanup remains pending before conflicting work.
Protéger les images actives et restaurées
Retained role replicas keep their required image artifacts protected during configuration changes and release cleanup.
Restaurer avec précision l'environnement Compose gelé
Rollback preserves encrypted deployment snapshots without confusing literal redaction-like values with missing secrets. Incomplete legacy snapshots fail clearly rather than borrowing mutable current service settings.
Surveillance, caches et stockage du cloud
Évitez les analyses de surveillance coûteuses
Cloud hosts using fuse-overlayfs skip Docker's full storage inventory, which can exhaust daemon memory. Host totals remain measured; unavailable detailed project storage stays unknown.
Afficher l'utilisation de la RAM invitée
Use verified guest counters instead of hypervisor process memory and overhead. Older guests receive a bounded, read-only memory sample; stream teardown releases the executor.
Gardez les métriques partielles utiles
Missing disk or memory fields in a live frame retain the latest measured value for that metric, with its measurement time. Purchased capacity is never substituted for measured consumption.
Limiter le nettoyage du cache Cloud
Collect only owned, idle project-worker caches and stop before Docker Engine's global builder prune. Cache reuse, worker GC, existing build concurrency and user-configured resource limits are unchanged. Cloud builds require their isolated BuildKit executor instead of silently falling back to the embedded builder. Existing legacy daemon state and autonomous Docker GC remain separate host-maintenance concerns.
Accepter les systèmes de fichiers sans totaux d'inodes fixes
Unsupported or zero inode totals mean unknown availability rather than confirmed exhaustion. Real free-space and supported inode-exhaustion checks still protect deployment admission.
Domaines et entrée
Acheminer les domaines personnalisés vérifiés lors du premier déploiement
Single-app domains without a saved destination use the verified serving port through the shared route planner. Explicit endpoints and service-group destinations retain their ownership instead of selecting a sibling service.
Évitez les ports hôtes secondaires éphémères
Secondary loopback publications use the existing allocator and the target host's ephemeral-range checks.
Gérer diverses applications d'accès à Cloudflare
Accounts containing launcher or other domain-less applications no longer crash managed ingress setup. Inventory and write receipts are validated while overlap and foreign-resource ownership protection remain enforced.
Clarifier la disponibilité des périphéries
Documentation explains edge failure behavior and recovery responsibilities for deployed applications.
Webmail
Résoudre les ID de message exacts pour les actions
Thread reads, deletion, labels and flags validate exact IMAP envelope identities instead of trusting substring search matches. Literal percent sequences remain unchanged, stale UID hints are rejected, and missing or refused operations no longer report success.
Mettre en cache correctement les actifs de l'application
Fingerprinted assets receive immutable caching while application HTML is revalidated.
Servir des actifs précompressés
Negotiate available Brotli or gzip files with appropriate content types, encoding and cache headers.