Jeroen UbbinkandClaude Sonnet 4.6 feb76bc89d fix: persist and propagate key constraints from Lightning invoices ...

LightningInvoice had no columns for balance_limit, balance_limit_reset,
or validity_date. SQLModel silently dropped these constructor kwargs, so
create_api_key_from_invoice always produced an unconstrained key.

Add the three columns to LightningInvoice with a migration, and wire them
through to the ApiKey in create_api_key_from_invoice, matching the pattern
already used in the child key creation path.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-06-03 14:58:40 +02:00

..

__init__.py

change dir 'router' -> 'routstr'

2025-08-09 14:55:26 -03:00

admin.py

add api key creation date

2026-06-01 23:27:26 +02:00

db.py

fix: persist and propagate key constraints from Lightning invoices

2026-06-03 14:58:40 +02:00

exceptions.py

remove and clean up redundant logs

2026-05-01 23:07:43 +02:00

log_manager.py

Optimize dashboard analytics pipeline and clean UI data flow

2026-03-13 15:54:59 +08:00

logging.py

remove and clean up redundant logs

2026-05-01 23:07:43 +02:00

main.py

better handling invoice payment

2026-05-28 20:09:48 +02:00

middleware.py

do not logs redundant infos

2026-05-01 16:23:30 +02:00

not_found.py

update not found proxy

2026-05-14 15:40:49 +02:00

settings.py

configure payment

2026-05-09 00:00:18 +02:00

usage_analytics_store.py

Use per-metric top-model selection for usage mix

2026-03-13 15:55:29 +08:00

version.py

display correct commit

2026-05-16 19:10:45 +02:00