From 9021ab01a700db4a74d066a1ad6855e778a3efa0 Mon Sep 17 00:00:00 2001 From: aitbc1 Date: Fri, 27 Mar 2026 22:35:11 +0100 Subject: [PATCH] fix: correct poetry lock command syntax MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit POETRY LOCK COMMAND FIX: Remove invalid --no-update option Issue Fixed: ❌ The option "--no-update" does not exist ❌ poetry lock --no-update failing with invalid option Root Cause: - --no-update option doesn't exist in poetry lock command - Incorrect command syntax causing poetry lock to fail Solution Applied: ✅ Changed poetry lock --no-update to poetry lock ✅ Uses correct poetry lock command syntax ✅ Still regenerates lock file when needed ✅ Follows poetry documentation properly Impact: - Security scanning workflow now works correctly - Poetry lock file regeneration succeeds - Dependencies install properly after lock sync - No more invalid option errors This resolves the poetry command syntax issue that was preventing the security scanning workflow from handling out-of-sync poetry.lock files correctly. --- .gitea/workflows/security-scanning.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitea/workflows/security-scanning.yml b/.gitea/workflows/security-scanning.yml index ca1db4fc..f5284f40 100644 --- a/.gitea/workflows/security-scanning.yml +++ b/.gitea/workflows/security-scanning.yml @@ -92,7 +92,7 @@ jobs: $POETRY_CMD install --no-root else echo "poetry.lock is out of sync, regenerating..." - $POETRY_CMD lock --no-update + $POETRY_CMD lock echo "Installing dependencies with updated lock file..." $POETRY_CMD install --no-root fi