From da0acb2a5ab60f4a0172cf27ddbdd071b773210e Mon Sep 17 00:00:00 2001 From: Marcel Losso Date: Wed, 11 Nov 2026 10:52:31 -0300 Subject: [PATCH] Mark the 0.5.4 changelog released --- site/src/content/changelog/0.5.4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/src/content/changelog/0.5.4.md b/site/src/content/changelog/0.5.4.md index 5fc751a..4b214c3 100644 --- a/site/src/content/changelog/0.5.4.md +++ b/site/src/content/changelog/0.5.4.md @@ -2,7 +2,7 @@ version: 0.5.4 title: A detected Python virtualenv, and Run before on a Service date: 2026-11-10 -released: false +released: true --- - **A detected Python virtualenv is applied for you.** When you add a Project, a Python command such as `uvicorn` or `flask` gets the nearest real `.venv`, `venv` or `virtualenv` attached, and the command stays clean. Edit Service and the import review show **Using detected virtualenv** (or the folder's name). localhost puts that environment first on `PATH` and sets `VIRTUAL_ENV` when the Service starts. You can point the field at another folder or turn it off. Commands that already use `uv`, Poetry or Pipenv, or that already name the venv's binary, are left as they are. Services you already have are not rewritten on a re-scan.