[Bug]: Rollback fails with shallow clone enabled, and doesn't actually rollback when disabled (docker compose setup)

[tjausm]

Error Message and Logs

Step 1: Shallow clone enabled (default)

Deploying works fine. Making changes and redeploying works fine. When attempting to rollback:

Starting deployment of tjausm/coolify-rollback-issue:main-d0c888ko8c8wwgk4owckck08 to localhost.
Preparing container with helper image: ghcr.io/coollabsio/coolify-helper:1.0.12
----------------------------------------
Importing tjausm/coolify-rollback-issue:main (commit sha 0558df0868dc8219734305e16b3225d074827853) to /artifacts/us8c48koo8wkg40swkkoggcc.
========================================
Deployment failed: Command execution failed (exit code 128): docker exec us8c48koo8wkg40swkkoggcc bash -c 'cd /artifacts/us8c48koo8wkg40swkkoggcc && git log -1 0558df0868dc8219734305e16b3225d074827853 --pretty=%B'
Error: fatal: bad object 0558df0868dc8219734305e16b3225d074827853
========================================
Gracefully shutting down build container: us8c48koo8wkg40swkkoggcc

Step 2: Shallow clone disabled

Workaround: deselect shallow clone in advanced options. Rollback now "completes":

Starting deployment of tjausm/coolify-test:main-d0c888ko8c8wwgk4owckck08 to localhost.
Preparing container with helper image: ghcr.io/coollabsio/coolify-helper:1.0.12
----------------------------------------
Importing tjausm/coolify-test:main (commit sha 329ffddc2e50212daaace057b06660bb96d4f37b) to /artifacts/ncwc0k08ss0ggoco4skkgc0w.
Added 2 ARG declarations to Dockerfile for service app1.
Service app2: All required ARG declarations already exist.
Pulling & building required images.
Adding build arguments to Docker Compose build command.
Removing old containers.
Starting new application.
New container started.
Gracefully shutting down build container: ncwc0k08ss0ggoco4skkgc0w

But it does not actually rollback - it redeploys the latest image. Container logs indicate the newest version is actually running instead of the rolled-back version.

Older images are available (confirmed via docker images -a in the Coolify terminal, rollback limit set to 20).

Steps to Reproduce

1. Setup repo via GitHub app with docker compose
2. Deploy
3. Make a change (e.g. update version in Dockerfile), commit, deploy
4. Attempt to rollback
5. We get bad object error
6. Disable shallow clone in project -> advanced settings
7. attempt to rollback
8. It just deploys the newest image again

Example Repository URL

https://github.com/tjausm/coolify-rollback-issue

Coolify Version

4.0.0-beta.463

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04.3 LTS

Additional Information

No response

[coderabbitai]

🔗 Related PRs

#6869 - fix(git): handle Git redirects and improve URL parsing for tangled.sh and other Git hosts [merged]
#7460 - fix: prevent cleanup exceptions from marking successful deployments as failed [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!