[Bug] Report: Deployment "HEAD" Links Always Point to Latest Commit

[usama-mashood]

Error Message and Logs

When deploying from a branch in Coolify, all previous deployments automatically update their HEAD reference to the latest commit of that branch.

This causes several issues:

1. The commit label (e.g., HEAD → dynamic_hwcode_polo) in past deployments changes to reflect the newest commit, not the one actually deployed.

2. Clicking the commit link on any old deployment opens the latest branch commit on GitHub, instead of the commit that was deployed at that time.

3. Even for a deployment showing HEAD → dynamic_hwcode_polo, if a new commit is pushed to GitHub, clicking that HEAD link opens the newest commit, not the original version.

This behavior makes it impossible to track which specific commit was deployed, breaking historical accuracy.

Steps to Reproduce

Steps to Reproduce

1. Deploy branch main at commit A.
2. Push a new commit (commit B) to the same branch.
3. Deploy again (creating a new deployment for commit B).
4. Observe:
   • Both deployments now show HEAD → commit B.
   • Clicking the commit link from either deployment opens commit B on GitHub, even for the first deployment that used commit A.
5. Push another commit (commit C) without deploying it.
6. Click on the HEAD →commit B link in any deployment — it opens commit C instead of the deployment’s actual version.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.434

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

• The issue occurs across multiple deployments from the different version.
• It also happens even if the new commit is not deployed — the HEAD link still opens the latest commit on GitHub.
• This breaks deployment history tracking and makes it difficult to confirm which code version was deployed.
• Please hide server information (like IP addresses and environment details) in the deployment view to avoid exposing infrastructure data.