Repository navigation
Releases
Releases Β· coollabsio/coolify
v4.7.5
Fixed
- Crashed the
Keys & Tokens>API Tokenspage with a 500 error for a token with scopes stored in an unexpected format - Failed connection to SFTP backup storages on an IPv6 address, and a connection error without the network reason
- The error now shows the network reason, for example
Connection refusedorConnection timed out
- The error now shows the network reason, for example
v4.7.4
Fixed
- Kept the records of failed database backups forever
- The daily database cleanup deletes failed database backups that are older than 60 days
- Missing production runtime variables in preview deployments when the variable has no preview variable
- A preview gets these production runtime variables again, except when
PR deployment accessis public. The deployment log lists each variable that a preview does not get
- A preview gets these production runtime variables again, except when
v4.7.3
Added
- An
Exportmenu on the vulnerability lists of a resource, of a server (Security>Vulnerabilities), and of the teamSecuritypage, to copy the list as a Markdown table or download it as CSV or JSON- The export contains the rows that the list shows, with its tab, search, and filters, from all pages
- The finding lists can also copy the vulnerability IDs
Fixed
- Broken links in backup notifications of the instance database and of service databases
- They link to
Settings>Backupand to the service page
- They link to
- Denied root team owners and admins to change and download the instance backup on
Settings>Backup(#12503, #12505) - Vulnerability scans of large images that stopped with a Syft or Grype timeout
- The default Grype time limit is 10 minutes. Set the
Syft time limit, theGrype time limit, and theScanner CPU limiton theVulnerabilitiespage of a server, or withimage_scan_syft_timeout,image_scan_grype_timeout, andimage_scan_cpusin the server image scanning API - The
Scanner CPU limitand theScanner memory limitoffer only values that the server has. The API refuses higher values
- The default Grype time limit is 10 minutes. Set the
v4.7.2
Security
- Restricted the
RedeployandStopactions of an application destination to the servers that the application runs on
Changed
- Names in the top breadcrumb, which now link to their page
- The section name, such as
Servers, opens the list page of the section - The project, environment, resource, server, storage, source, destination, and tag names open their own page
- The arrow next to a name still opens the switch list
- The section name, such as
Fixed
- Closed root account setup window right after a fresh install, so the first account could not be created on the
Registerpage - Image scans of large images that stopped because the scanner ran out of memory
- The scanner frees memory sooner when it gets close to its limit. Set a higher limit with
Scanner memory limiton theVulnerabilitiespage of a server, or withimage_scan_memory_mbin the server image scanning API. The default stays 1 GB
- The scanner frees memory sooner when it gets close to its limit. Set a higher limit with
- Missing scanner disk usage on the
Image Scanningpage of a server and in thescanner_disk_used_bytesAPI field- The
Delete scanner databutton also stays hidden now after the scanner data is deleted
- The
- The
Nightlyupdate channel was hard to find, because only theChannellist inSettings>Updatesnamed it (#12492)- On the
Stablechannel,Settings>Updatesshows a hint aboutNightly. The upgrade dialog shows the update channel and links toSettings>Updates
- On the
v4.7.1
Added
- The reason of a failed image scan in a
Show error logsection on theSecuritypage and in the Laravel log- The error log shows the failed step, its exit code, and the end of the command output. Only users who can change the resource or server see it
Fixed
- Failed image scans on self-hosted instances, because the scanner templates were missing from the Coolify image
- Ignored custom container labels and wildcard domains in maintenance mode (#12498)
- With editable container labels, maintenance mode uses the Traefik router rules and the Caddy site addresses of the labels
- Showed an error on the
Vulnerabilitiespage - Showed warning callouts in the accent color instead of yellow when a custom theme is active
v4.7.0
Breaking Changes
- Cancelled the older queued webhook deployments of an application by default when a newer push arrives, so only the latest commit is built (#10921, #7678)
- It works per application, pull request and server
Advanced>Deploymentandis_auto_cancel_queued_deployments_enabledin the applications API turn it off- Manual, API, restart and rollback deployments are never cancelled
- An opt-in setting,
is_auto_cancel_building_deployments_enabledin the API, also stops an older webhook deployment that is still building, a deployment that started to replace containers always finishes cancel_previous(none,queuedorbuilding) on/api/v1/deployand the MCPdeploytool cancels the older webhook, API and MCP deployments, the default isnone
- Limited the cloud provider token API to team admins and owners
- Other members get
403
- Other members get
- Moved the Resend sender to the new
resend_from_addressandresend_from_namefields, API clients must use the new fields- A migration copies the current values
Security
- Applied the limits of API tokens to more permission checks
- A message explains when a token limit blocks a change
- Built team invitation links from the instance URL instead of the request host, when no instance domain is set
- Checked that members with access grants can use the selected server and the team credentials
- A new, cloned or migrated resource needs a server that the member can use, the localhost server needs an instance admin
- Server lists show only the servers that the member can use
- Team private keys, GitHub Apps, Gitea Apps and new S3 storages of backup schedules need write access on the whole team, also through the API
- A message explains when write access on the whole team is needed
- Checked the deploy permission before a deploy through the API creates a preview or changes its image tag
- Ended terminal sessions when access to the server is lost
- Enforced fixed SSH connection options on every connection, also for health checks
- Generated new SSH keys as Ed25519 and validated private keys more strictly
- Hardened SMTP and terminal connections
- SMTP hosts are validated, and Coolify connects only to the checked address
- The error message explains why an SMTP host is refused
- Limited the server data in the application, service, and database API responses to tokens that cover the whole team
- Removed the server details from the response of the
get_serviceMCP tool - Kept personal data and credentials out of audit events
- The audit events of a deleted user are anonymized
- Kept stored private keys out of the browser
- Kept the Sentinel token out of process arguments
- Sentinel reads it from an env file
- Limited API clients that keep failing to 30 failed requests per minute for one token or IP
- More failed requests get
429,API_FAILED_REQUEST_RATE_LIMITsets the limit - The team of the token gets one notification a day when the token reaches the limit
- More failed requests get
- Pinned the SSH host key of a server on the first connection, the team gets a notification when it changes
SSH_HOST_KEY_CHECKINGsets the mode:warn,enforceoroff
- Pinned the SSH host keys of Git hosts across deployments
- Coolify shows the published host keys of GitHub, GitLab and Bitbucket
- Restricted preview changes, rollbacks and repository URL changes
- Opening a preview, changing its pull request URL, Git type or Docker tag, or choosing a commit through the API needs write access, a deploy token can only redeploy an existing preview
- A rollback goes only to a listed rollback image or a successful production deployment
- A new
git_repositoryof an application is validated like in the UI - The
docker_tagof/api/v1/deployis validated like in the preview API
- Validated webhook URLs, limited DNS lookups and tightened the authorization of team resources
Added
- A list view on the new resource page
- A
Not usedlabel on the TLS certificates of the Traefik proxy page, and aDelete unusedbutton that deletes them in one step (#12447)- A certificate is unused when no route and no resource on the server uses its domain
- Traefik renews every certificate in
acme.jsonuntil you delete it and restart the proxy
- API endpoints and MCP tools that manage image scanning and read the scan results
GETandPATCH /api/v1/servers/{uuid}/image-scanning,GET /api/v1/vulnerabilitiesandGET /api/v1/{applications|databases|services}/{uuid}/vulnerabilities- The MCP tools are
get_vulnerabilitiesandmanage_image_scanning
- A
Run in a shelloption on scheduled tasks, so containers withoutsh, such as distroless or scratch images, can run them (#8244)- Turn it off to split the command into arguments and run it directly
- The API and the MCP tools set it too
- A separate notification sender in the instance email settings
- Team notifications through the instance email settings, the S3 connection error alert and the channel disabled alert use it
- Account emails keep the default sender
- The
emailsartisan command no longer exists
- A
Skip TLS certificate verificationsetting on S3 storages, for endpoints with a self-signed or private CA certificate (#9762, #4402)- It applies to the connection test, backups, restores and the deletion of old backups
- The S3 storages API sets it with
skip_tls_verification - Browsers that download files from the storage must still trust the certificate
- A star button on servers and resources for quick access on the dashboard
- The button is after the status in the top bar
- A
UI scaleoption in the appearance settings - Automatic update notifications, the root team gets one when an automatic update starts, fails or finishes
- A manual upgrade that fails before the upgrade script starts shows the error in the upgrade modal
- A warning when the Docker Compose file of an application is in a subdirectory of the base directory, with a button that moves the directory of the file into the base directory (#9525)
- Coolify runs Docker Compose in the base directory, so relative paths such as
build.context: ..resolve from there
- Coolify runs Docker Compose in the base directory, so relative paths such as
- Container image vulnerability scanning, opt-in for each server and each application
- Syft and Grype run on your server, and no data goes to a third party
- Each resource gets one security status and version recommendations, with an optional deploy gate for each application
- The team
Securitypage and the notifications show the results
- Forgejo and Codeberg in the Gitea App source
- A
Providerlist fills in the Gitea.com or Codeberg URLs - Webhooks accept the
X-Forgejo-*headers
- A
- Gitea App endpoints in the API and the MCP tools,
GET /gitea-appsandPOST /applications/private-gitea-app(#12459)gitea_app_uuidsets the source when you create or update an application
- GitHub Deployments sync, each deployment and preview reports to GitHub Deployments with links to the log and the environment
- It needs a private GitHub App with
Deployments: write
- It needs a private GitHub App with
- One email provider list with None, SMTP and Resend, more than one named SMTP server with its own sender, and SMTP templates for common providers
Rotate keyon private keys, which replaces a key on all servers that use it- Coolify adds the new key to
authorized_keys, can undo the rotation, and removes the old key - A server delete can remove the key from
authorized_keys - Coolify deletes unused SSH key files every hour
- The button shows only when a server uses the key
- Coolify adds the new key to
- Server usage in the server table of the dashboard on mobile
- SFTP, FTPS and WebDAV backup storages for database and volume backups, with downloads, retention and restores
- SFTP restores and downloads need a host key that an admin saved with a validation
- The finish time of recent deployments on the dashboard
- The logo and name of the resource on the resource creation screen
- The Orbit service template, a self-hosted workspace for teams with tasks, docs, chat and an MCP server for AI clients
- Valkey as an image of the Redis database type
- A new step of a new Redis database asks for Redis or Valkey
- Global search accepts "new valkey"
Changed
Import Backupfrom the resource menu to anImport backupbutton on theBackupspage of databases and services (#11818)- The button opens the import in a dialog
- Old
Import Backuplinks open theBackupspage
- Maintenance mode to its own
Maintenancepage of applications and services, and you must confirm the toggle - The data retention of unsubscribed teams on Coolify Cloud from 30 to 60 days
- The cleanup saves the deleted users to
cloud-deleted-users.csvon the backups disk
- The cleanup saves the deleted users to
- The default image of new Redis databases to
valkey/valkey:9-alpine- Existing databases keep their image
- The default images of new databases to PostgreSQL 18, MongoDB 9, MySQL 9.7, MariaDB 12.3 and ClickHouse 26.8
- Existing databases keep their image
- The default images on the new resource page to Supabase PostgreSQL 17.11.0.018 and PostGIS 18-3.7-alpine
- The notifications of scheduled jobs that keep failing, to the first failure and then at most once a day
- This covers scheduled tasks, database backups, storage backups and Docker cleanup
- The first successful run after a failure sends one "works again" notification to the failure channels
- A database backup whose S3 upload keeps failing also notifies at most o...
v4.6.0
Breaking Changes
- Require the new
deleteability, orroot, for every delete through the API and the MCP server, an API token withwritealone can no longer delete resources, environment variables, storages, backups, scheduled tasks or tags, or detach a tag
Security
- Harden the CI workflows
- Require every action to be pinned to a full-length commit SHA, with an Actions setting on GitHub that enforces it
- Lock every action and the actions it calls to a commit in
.github/workflows/actions.lock, together with the IDs of its owner and repository, which a commit SHA alone does not check - Require every workflow to use the lockfile, with an Actions policy on GitHub that enforces it
- Keep the Docker Hub credentials and the CDN token in the
releaseenvironment, which only the branches that release can use - Run without the GitHub Actions cache, layer caches and cached tool binaries, so no run restores what another run wrote
- Grant every job the least permissions it needs and state the reason for every write permission
- Keep the tokens that delete images in the
cleanupenvironment, which onlymaincan use - Fix every finding of jactionlint pedantic
- Refuse to update, force-push or delete the git tag of a release, with a tag protection rule on GitHub
- Refuse to delete or force-push
main,next, release and maintenance branches, with branch protection rules on GitHub - Hide locked environment variable values in the resource lists of
GET /api/v1/resourcesandGET /api/v1/projects/{uuid}/{environment}, like the other endpoints already do - Require an instance admin to disable the API, or to enable or disable the MCP server, through the API
- Route only the Reverb WebSocket path
/app/through the domain of the Coolify dashboard, the generated Traefik and Caddy configurations no longer expose the Reverb HTTP API under/apps - Require the
deployability for the registry check and the registry logout of the API and the MCP server, like the registry login - Keep the file names of PostgreSQL init scripts inside the init script directory
- Protect archive branches from updates, deletions and force-pushing, with branch protection rules on GitHub
Added
- Limit a team member or an API token to selected projects, environments or resources, with the access levels read, read sensitive, deploy, write, delete and root, where a higher level includes the lower ones
- Give an API token access to the whole team or to selected projects, environments or resources, a token never gets more access than its owner and stops working when its owner loses that access
- Set the access of a member when you invite them, or later with a preset (viewer, developer, operator or full access) or per scope
- Show members and tokens limited to some scopes only the projects, environments, resources, deployments and search results they can access, and keep them out of the team-wide pages and API endpoints
- Set a member back to read-only to clear their grants and revoke their API tokens
- See a summary of the access of every member under their email in the members list
- Choose the update channel of an instance on the update page: stable, preview with betas and release candidates, nightly with a warning that breaking changes are possible, or a custom image such as
pr-1234 - Publish prereleases from
nextand the release branches, tagged like4.6.0-beta.1, and the movingpreviewtag - Publish a nightly version twice a day, tagged like
4.6.0-alpha.0.20261026.1, with the movingnightlytag and the nightly channel of the CDN, fromnextor from the release branch while one is in progress - Keep the updates of the old channel after a switch to a more stable channel, until the stable release of the installed version is out
- Install the newest preview or nightly version with
install.sh --previeworinstall.sh --nightly, which also switches the update channel of the instance - Switch the update channel from the command line with
php artisan app:update-channel - Manage DNS records, integration tokens and secret managers through the API and the MCP server
- View, create, replace and release the Cloudflare DNS records of the domains of applications and services
- Create the DNS records of the domains that
PATCH /applications/{uuid}andPATCH /services/{uuid}add, when exactly one zone with automatic DNS manages them, like the Domains page does - List, update, rotate and delete integration tokens, sync their DNS zones, and create Cloudflare tokens with DNS and tunnel capabilities
- Set, remove and import the secret manager of applications, services and databases, key names are listed and values are never returned
- Add the MCP tools
manage_dns,manage_integration_tokens,manage_secret_managerandmanage_cloudflare_tunnel
- Edit the description, permissions, access and expiry of an API token, its value stays the same
- Pause and resume an API token, a paused token cannot authenticate to the API or the MCP server
- Roll an API token to replace its secret and keep its description, permissions, access and expiry
- Clone private repositories from custom Git hosts over HTTPS with a username and a password or access token, set on the Source page or through the API, instead of a token in the repository URL
- Open the console of the main process of a container from the terminal, next to the shell, for containers that keep stdin open, such as game servers and REPLs, with the last 200 log lines and a command box that sends whole lines to the process
- Keep the stdin of a Docker image application open with
-ior-itin its custom Docker options, so its terminal can open the console - Send the logs of a server to Amazon CloudWatch Logs with the Docker
awslogslog driver as a log drain - Include the commit SHA, branch and message in deployment emails, with an opt-in setting of the email notifications
- Filter a table by clicking a type, status, server, source or role value in a row, and sort it by clicking a column header, also the projects and servers of the dashboard
- Show the Compose default of an empty environment variable in the developer view
- Add the Hi.Events one-click service
- Attach an SBOM attestation to every image, which lists every package of the image
- Publish the image of every pull request from a branch of this repository as
ghcr.io/coollabsio/coolify:pr-<number>, so a change can be tried before it is merged - Build
maintwice a day when it changed and move themaintag on ghcr.io to it, versioned like4.5.0.20261028.1, to test fixes before their patch release - Add OCI labels to the image, such as its version, commit, creation date, license and base image, instead of the labels it took over from its serversideup/php base image
- Copy the labels of the image to the annotations of its index, ghcr.io reads the description and the license of an image of several platforms from there
- Send a reminder email with a recovery link to the admin who started a subscription checkout on Coolify Cloud and did not finish it
Changed
- Replace the release process,
RELEASE.mddescribes it- Keep the Coolify versions in
release.json,stable.coolifyformainand the maintenance branches andpreview.coolifyfornextand the release branches - Pin the helper, Sentinel and Traefik versions in
upstream.jsoninstead ofversions.json, the CDN writesversions.jsonfrom it - Release from
main,next, release branches such asrelease/v4.6and maintenance branches such asv4.xandv4.4.x - Select the stage and the version with
scripts/release.sh, which offers the versions the branch allows and preselects the bump the commits need - Publish the version a push of
release.jsonsets, unless it is published already, instead of a reviewed draft release - Move
latestandpreviewto their place among all published tags, so a release of an older version never moves a tag back - Plan the version, the releases, the moving tags and the nightlies with
scripts/plan-version.sh, which also reports what a push publishes - Take the release commit back before the push with
scripts/undo-release.sh
- Keep the Coolify versions in
- Take the Coolify version from the image alone, the upgrade script removes
COOLIFY_VERSIONfrom.env - Compress the image layers with zstd instead of gzip, it compresses better and compresses and decompresses faster, pulling needs Docker Engine 23.0 or later and Coolify requires 24.0
- Fetch the Fleet Metrics of all servers at the same time, with one SSH command per server instead of one per metric, so the page loads 10 to 19 times faster with 1 to 10 servers in our benchmark
- Move the helper image to coollabsio/coolify-helper, which releases it
- Bump the SQLite image to
3.54.1-v0.2.0with SQLite 3.54.1, which lets any user ID write the database files, so a connected application no longer has to run as65532or root- Replace the user ID note on the connect page with a warning that a bind mount opens the database files to every user on the host
- Streamline the CDN
- Sync every channel with the install and upgrade scripts and the compose files of the commit it releases, instead of the copies in
other/nightly - List the Coolify, helper, Sentinel and Traefik versions of every channel in
/coolify/versions.json, older instances keep reading itscoolifyandtraefikkeys - Add a preview channel for the betas and release candidates
- Sync it with
scripts/sync-cdn.shinstead ofphp artisan sync:cdn, from the release workflow whenlatestorpreviewmoves and from the nightly workflow - Open a pull request for the stable channel and push the preview and nightly channels directly
- Clear the Cloudflare cache of the CDN with
scripts/sync-cdn.sh --purge
- Sync every channel with the install and upgrade scripts and the compose files of the commit it releases, instead of the copies in
- Rework the CI workflows for the new release process
- Build each platform once and publish exactly th...
v4.5.3
Fixes
- Kept the Dockerfile
HEALTHCHECKof existing applications. Since v4.5.1, the Coolify healthcheck replaced it. - Fixed Docker Compose builds that failed with "required variable is missing a value" when a required variable was set only for runtime. (#12363)
- Fixed Railpack builds that failed when they started at the same time as another build.
- Removed orphaned SSH connection processes that collected on the Coolify host.
- Fixed server validation, which now continues over SSH when the Hetzner API call fails.
- Stopped retries of HTTP requests that timed out after they were sent, so the same action did not run two times.
- Fixed MCP tokens with the
read:sensitivepermission, which did not see the commands and configuration of applications and databases.
Improvements
- Updated the Coolify helper image to 1.0.19.
Full Changelog: v4.5.2...v4.5.3
v4.5.2
Fixes
- Fixed pull request previews that existed before the upgrade breaking on redeploy. They keep the production values they were first deployed with. New previews use only their own variables.
- Fixed 503 errors from Traefik during the first rolling update after you saved application settings. The retry proxy labels from v4.5.1 were removed, so the proxy labels are the same as in v4.5.0.
- Fixed SSH connections that stayed open and used up memory on the server when another process held the multiplexing socket.
- Fixed S3 backups that failed when the MinIO client fell back to S3v2 signing. Requests now always use S3v4, and failed uploads are tried again.
- Improved MySQL and MariaDB restores. They use the restore options of newer client versions, check the backup before they change the database, and stop with a clear message for unsupported content (#12352).
- Custom database configuration and custom Docker options of standalone databases are now shown only to team admins and owners, and to API tokens with sensitive read access (#12353).
- Application commands and configuration are now shown only to team admins and owners, and to API tokens with
read:sensitiveaccess. - The service configuration form now uses the same role permissions as the environment variables page. Users who cannot manage the service environment see its fields as read-only (#12356).
- Finish events of background tasks now apply only to servers and services of their own team (#12355).
- API tokens with the
writeability can now set manual webhook secrets. - Pushover notifications no longer write the message payload to the log.
What's Changed
- fix(database-import): improve MySQL and MariaDB restore handling by @andrasbacsai in #12352
- fix(databases): show custom configuration only to admins by @andrasbacsai in #12353
- fix: scope finish events of background tasks to their team by @andrasbacsai in #12355
- fix(services): align service configuration form with role permissions by @andrasbacsai in #12356
Full Changelog: v4.5.1...v4.5.2
v4.5.1
Breaking Changes
- Removed the "Remove from Coolify only" service delete option. A normal delete now works when the server is unreachable, and the services API rejects
delete_from_coolify_onlywith 422. - Removed the Highlight log drain because the service ended. Coolify stops its running containers.
Features
- (Self-hosted only) Limited first root account registration to ten minutes after Coolify starts. Restart Coolify to open the window again.
- Let team owners and admins require 2FA for all team members.
- Skipped the Compose image build when the images match the build inputs, so runtime-only changes no longer rebuild.
- Added a four-color custom theme dialog with presets and share codes.
- Let admins drag project and server zones on the canvases.
- Reworked the dashboard layout and showed live CPU and memory in the server table.
- Synced metric chart tooltips across charts and added local or UTC tooltip times.
- Made live refresh a toggle for every metrics and analytics range.
- Added compact traffic metrics with scaled latency units.
- Replaced native number spinners with a branded stepper.
- Moved the file browser container picker to a header dropdown.
- Added
# coolify:flag directives (literal,buildtime,runtime) to the developer view of environment variables (#12349). - Added a "Use path-style URLs" setting to S3 storages for providers that need virtual-hosted-style URLs.
Improvements
- Stopped 502 errors during rolling updates with proxy retries and a configurable drain time (#8627).
- Made metrics faster with one Sentinel SSH command and Sentinel-side bucketing (#12300).
- Stopped syncing file storages on every Compose parse.
- Made canvas pan and zoom faster.
- Added a confirmation when you clone with volume data, and stopped the source while data is copied.
- Verified helper downloads by SHA256 and updated Docker CLI, Compose, Buildx, and Railpack.
- Updated Sentinel images to 1.1.3.
- Updated Laravel to 12.70.1, the PHP image to v5.0.3, and Nginx to 1.31.8.
- Hid container tooling user agents in traffic analytics by default (#12335).
- Added a DNS menu to the domains toolbar.
- Explained what 100% CPU means in chart tooltips.
- Retried connection failures of idempotent HTTP requests, including Cloudflare API calls.
- Updated Fluent Bit for log drains from 2.0 to 5.1, and restarted running drains when their files change.
- Fetched Sentinel analytics dashboards of all servers at the same time.
- Validated new cloud servers automatically when they are running.
Fixes
- Security: enforced resource permissions for stored secrets and hid locked and admin-only secrets in forms, Compose, and the API.
- Security: closed holes in server transfer import, claim, and archives.
- Security: blocked PostgreSQL restore scan bypasses and stopped restores on SQL errors (#12333).
- Security: enforced GitHub App webhook signatures in the local environment.
- Security: limited system-wide Gitea sources to instance admins and source app lists to the current team.
- Security: hid database URLs in API create responses without sensitive access (#12297, fixes #11190).
- Security: scoped database backup API endpoints to the database type (#12279).
- Security: used the Cloudflare client IP for API allow-lists and audit logs (#12301).
- Wrote the generated Compose file after the image build (#12331).
- Wrote regular deployment files when the repository has symlinks (#12324).
- Prevented Git fetches from hanging (#12321, fixes #10316).
- Read the Compose file from Git objects and from Git submodules (#12320, fixes #11018).
- Allowed safe percent-encoded repository paths (#12319).
- Stripped paths and ports from
COOLIFY_FQDNin env files (#12245, fixes #9649). - Used SSH user registry credentials for host image pulls (#12216, fixes #12205).
- Rebuilt when a build secret value changed.
- Replaced the Dockerfile
HEALTHCHECKwhen the healthcheck was enabled (#10974). - Kept the healthy new container when a rolling update failed late (#12253).
- Stopped false pending changes (#11101, #12284).
- Found the current rollback image for containers with any name (#12296).
- Reported a failed application stop (#11063).
- Parsed mode suffixes in long-form bind targets.
- Created one Compose service on repeated submits and rejected Compose without services (#11078).
- Skipped the PORT mismatch warning when readonly labels were disabled (#10941).
- Deployed previews with their own environment variables (#12325).
- Kept custom preview domains on redeploy (#6536).
- Built the PR commit on manual Bitbucket preview redeploys (#10806).
- Keyed preview Docker tags by preview ID and stopped the DNS poll from re-queuing sync jobs.
- Kept open preview volumes out of stale Compose volumes (#10855).
- Kept locked variables and their preview copies locked with their values (#12299).
- Kept omitted values and flags when patching env variables through the API (#12240, fixes #9977).
- Included Infisical imported secrets (#12267).
- Regenerated proxy labels when the API changed exposed ports (#12334, fixes #11074).
- Saved
is_auto_deploy_enabledfor Docker image and Dockerfile apps created by the API (#12339). - Wrote file storage content to the server on API PATCH (#12248, fixes #11759).
- Accepted API settings that the UI can change (#11092).
- Showed only permitted MCP tools and actions in help and hints (#12295).
- Kept privileges in PostgreSQL backups (#12244).
- Signed S3 uploads with the storage region (#12264).
- Saved removed databases in the backup list (#11548) and explained dumps that stopped without an error (#11549).
- Identified the instance database backup by ID.
- Used the instance URL in volume backup notifications (#12285).
- Kept the proxy status current and stopped auto-start during proxy restarts.
- Validated servers without a proxy (#11048) and explained Docker Engine version check failures (#11089).
- Blocked server migration when the target proxy is not running.
- Replaced wedged SSH multiplexing masters (#12241, fixes #10077, #11130).
- Proxied realtime and terminal WebSockets on the dashboard port (#11707).
- Kept new images during Docker cleanup (#11069) and skipped scheduled cleanups during deployments (#12183).
- Removed orphaned legacy realtime containers.
- Kept a detected public IP when the other IP family's lookup timed out (#12275).
- Quoted root credentials in the installer
.env(#12276) and kept operator SSH keys that mention coolify (#12278). - Reported a failed manual update check (#12266).
- Passed the cloudflared Access service token to the terminal SSH (#12312).
- Browsed files in containers without a shell (#12305).
- Trimmed Telegram bot tokens and chat IDs (#12323).
- Showed the server timezone in scheduled task help (#10904).
- Listed production, staging, and development environments first (#12317).
- Hid deleted resources on the environment page after the redirect.
- Showed held-back package updates separately.
- Fixed the filtered tag count in pagination.
- Recreated the Mosquitto password file on each start (#11691).
- Updated the Reactive Resume template to v6 (#12282).
- Fixed server online status (#12289), disk detection (#12315), chart density (#12281), and loading on slow servers in metrics.
- Fixed checkbox clicks in confirmation dialogs (#12338).
- Fixed the database image picker (#12337) and server IDs in the new resource wizard (#12327).
- Floated listbox panels over modals (#11529) and fell back to the default for invalid theme colors (#12287).
- Fixed sidebar, tooltip, canvas, chart, list, and Compose loading issues in the UI.
- Kept member API tokens when a member is promoted (#12342).
- Returned
success: falseon API access denied responses (#12343). - Documented database and resource list responses in OpenAPI, and stopped requiring both
environment_nameandenvironment_uuidon create endpoints (#10449). - Allowed environment variable references in image tags (#10642).
- Kept quoted values when saving the developer view of environment variables (#10406).
- Reported Compose files with no parsed services during deployments.
- Stopped containers again while they restart past their restart limit (#10761).
- Showed container logs that contain invalid UTF-8 (#10628).
- Fixed terminal connections that closed with "Missing required tokens" when the session cookie name was custom.
- Updated breadcrumb names after a rename (#12341).
- Showed why Hetzner, DigitalOcean, and Vultr API requests fail, stopped duplicate Hetzner create requests, and deleted unsaved VPS instances.
- Recreated database TCP proxies that run an outdated configuration.
- Skipped Git LFS downloads when Git LFS is disabled (#10360).
- Kept the base directory in new repository applications (#10319).
- Kept saving applications with unchanged legacy build commands.
- Used the owner/repo slug for GitHub API calls with SSH repository URLs (#10175).
- Showed GitHub App errors when loading repositories (#10174).
- Fixed terminal authentication when a sibling subdomain sets another XSRF-TOKEN cookie.
- Added an Axiom edge domain setting to log drains, so EU datasets work.
- Hid out-of-stock and deprecated Hetzner server types, or showed them as disabled.
- Let password managers autofill the confirmation password (#9963).
- Checked out short commit SHAs with shallow clones (#9926).
- Replaced the clone suffix instead of adding one for each clone (#9976).
- Kept port-suffixed
SERVICE_URLandSERVICE_FQDNvariables in sync with the domain (#9877). - Returned logs of stopped containers through the API, like the UI.
- Renamed the old Security labels to Keys & Tokens.
What's Changed
- fix(api): hide DB URLs in create responses without sensitive access by @andrasbacsai in #12297
- fix(deployments): strip paths and ports...