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

..

core

fix: persist and propagate key constraints from Lightning invoices

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

nostr

display commit if node not aligned with release tag

2026-05-01 16:47:34 +02:00

payment

enforce fee calculation

2026-05-16 23:13:47 +02:00

upstream

revert sse refactoring

2026-06-02 13:58:43 +02:00

__init__.py

chore: update version/readme; minor auth logging and settings usage

2025-09-08 10:53:41 +01:00

algorithm.py

strict fallback

2026-05-06 00:46:42 +02:00

auth.py

prevent zero balance token

2026-06-01 22:47:09 +02:00

balance.py

refactor(balance): remove unreachable cashu-refund-by-hash endpoint

2026-05-28 10:25:25 -05:00

lightning.py

fix: persist and propagate key constraints from Lightning invoices

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

proxy.py

passing through tee get requests

2026-05-19 10:53:59 +08:00

wallet.py

prevent zero balance token

2026-06-01 22:47:09 +02:00