From 7e7f491749deaa2f1db6ac9eac2dd92ef32a757b Mon Sep 17 00:00:00 2001 From: Andras Bacsai <5845193+andrasbacsai@users.noreply.github.com> Date: Tue, 3 Nov 2026 17:33:55 +0100 Subject: [PATCH] fix(ui): open the unsaved bar for update channel and healthcheck type changes Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 2 ++ .../project/shared/health-checks.blade.php | 11 ++++---- .../views/livewire/settings/updates.blade.php | 25 +++++++++++-------- 3 files changed, 23 insertions(+), 15 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index db14d94977..4883ed923a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -17,6 +17,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), - Handle an existing Cloudflare DNS record with a different IP when Coolify adds the DNS record of a new domain automatically. Coolify now replaces the record when it created the record and no other resource uses it. Otherwise it opens the **Configure DNS** dialog, where you can replace the record, and the domain shows the conflict instead of "Not checked" - Add the Cloudflare DNS record automatically, or open the **Configure DNS** dialog, also when you edit a domain to a hostname in a connected Cloudflare zone, for example when you change a generated domain to your own domain. Before, Coolify did this only when you added a new domain. This applies to the **Domains** pages, the application and service application settings, and the service application API - Save deployments started through the MCP server as MCP deployments, not as API deployments. The deployment list shows them with the **MCP** source and filter, and the API and MCP deployment data have a new `is_mcp` field. The deployments to additional servers keep the source of the main deployment, and the audit log records actions that MCP tools do through the API as MCP events +- Save the update channel in **Settings > Updates** when you select **Preview** or **Nightly**. Before, the "Save changes" bar did not open for these channels, so the change was lost when you refreshed the page +- Save the healthcheck **Check type** when it is the only change. Before, the "Save changes" bar did not open when you changed only the check type, for example from **Container command** back to **HTTP request** ## [v4.6.0] - 2026-11-02 diff --git a/resources/views/livewire/project/shared/health-checks.blade.php b/resources/views/livewire/project/shared/health-checks.blade.php index d298963454..fddc288e43 100644 --- a/resources/views/livewire/project/shared/health-checks.blade.php +++ b/resources/views/livewire/project/shared/health-checks.blade.php @@ -40,12 +40,12 @@ @endif
-
- @if ($healthCheckType === 'http') +
@@ -77,7 +77,8 @@ helper="Leave empty when the response body does not need to contain specific text." />
- @else +
+
@@ -88,10 +89,10 @@ + required x-bind:required="$wire.healthCheckType === 'cmd'" />
- @endif + diff --git a/resources/views/livewire/settings/updates.blade.php b/resources/views/livewire/settings/updates.blade.php index 6a096081be..49dc757d8e 100644 --- a/resources/views/livewire/settings/updates.blade.php +++ b/resources/views/livewire/settings/updates.blade.php @@ -18,7 +18,8 @@
- - @if ($update_channel === 'custom') +
- @else - - @endif +
+ - @if ($update_channel === 'nightly') - +
+ Nightly builds are untested builds of the next version. Things can break at any time and breaking changes are possible, including database changes a stable release does not expect. Back up first and use nightly only on an instance you can rebuild. After switching back to stable, the instance keeps getting the nightlies of its version until that version is released as stable. - @elseif ($update_channel === 'custom') - +
+
+ The image installs only when you upgrade to it here, and automatic updates pause until you switch back to a channel. Pull request builds are untested and can include database changes a later release does not expect. - @endif +