# Restarting a space does not pulls last version **URL:** \ **Category:** Beginners\ **Created:** [February 25, 2025, 10:20am UTC](https://discuss.huggingface.co/t/restarting-a-space-does-not-pulls-last-version/142838 "2025-02-25T10:20:13Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\ **Post date:** [February 25, 2025, 12:43pm UTC](https://discuss.huggingface.co/t/restarting-a-space-does-not-pulls-last-version/142838/2 "2025-02-25T12:43:02Z")
Maybe. Ongoing issue. > [@Hugging Face Space Keeps Using an Old Commit Despite Redeploys](https://discuss.huggingface.co/t/hugging-face-space-keeps-using-an-old-commit-despite-redeploys/139695): > > Description I’m running a FastAPI app in a Docker Space on Hugging Face, and I’m experiencing an issue where my Space keeps using an old commit, even after pushing new commits and triggering a redeploy. Steps Taken I have committed and pushed multiple updates: git add . git commit -m "Trigger redeploy" git push origin main I even removed all remote files and pushed a fresh commit: git rm -r \* git commit -m "Remove all remote files" git push origin main Checked my commit history, and the … --- _[View the full topic](https://discuss.huggingface.co/t/restarting-a-space-does-not-pulls-last-version/142838)._