Diego ImbertandClaude Opus 5 d3ae20be67 fix(datatables): lock the fork copy at finalization, and order cleanup's registry write after its settings row ...

- Fork finalization holds the copy's database lock from its availability check to the commit.
- Cleanup removes the registry entry in its own transaction, in a task of its own, instead of on a
  second connection; a rename migrates reservations after its settings rewrites, so both take the
  settings rows before the registry.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-18 15:48:37 +02:00

..

examples

fix: enrich OTEL log records with per-request LogContext (#8812)

2026-04-13 21:50:50 +00:00

src

fix(datatables): lock the fork copy at finalization, and order cleanup's registry write after its settings row

2026-09-18 15:48:37 +02:00

tests

fix: skip instance group members that are not email addresses (#11128)

2026-09-15 09:45:10 +02:00

Cargo.toml

feat: guest JWT entry for embedded apps (#10954)

2026-09-05 10:23:37 +00:00