fix: BLS-Datenimport als Hintergrundjob gegen HTTP 504
Deploy Development / deploy (push) Successful in 1m10s
Build Test / pytest-backend (push) Successful in 5s
Build Test / lint-backend (push) Successful in 1s
Build Test / build-frontend (push) Successful in 24s

Prüfung und Apply laufen serverseitig, die UI pollt nur noch den Status.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
LarsandCursor committed 2026-09-12 14:57:13 +02:00
1 parent 8e964509d7
commit a07a668de2
6 files changed
+281 -35

No files matched your search

+2 -1
View File
@@ -21,7 +21,7 @@ MODULE_VERSIONS = {
"caliper": "1.0.1",
"activity": "1.2.1", # Legacy CSV import: activity_entries feature enforcement
"nutrition": "1.1.0", # BLS mapping, items, day marks, import policy
"bls": "1.0.0",
"bls": "1.0.1",
"photos": "1.0.0",
"insights": "1.3.0",
"prompts": "1.1.0",
@@ -44,6 +44,7 @@ CHANGELOG = [
"BLS 4.0 Stammdaten (dynamische Attribute, Upsert über bls_code)",
"Lernendes FDDB-Mapping ohne KI, änder- und löschbar",
"Optionale nutrition_items, Import-Policy, Fasten-/Lücken-Marken",
"BLS-Import als Hintergrundjob (kein Proxy-504)",
],
},
{