createEvent never called logAdminAction, even though the frontend's audit-log page (shipped in 1.10.0) already lists event_created as a filterable action — only updateEvent/deleteEvent actually logged. Event creation is now logged at every return path, including the legacy pre-migration retry branches.
Added a "Back to dashboard" link to Admin → Audit log, matching the existing back-link pattern used on the Cashup page.
Version bumped to 1.10.3.
Test plan
Backend Jest suite (21 tests) passes
Reviewed the diff against the existing event_updated/event_deleted logging pattern for consistency
Note: this doesn't backfill audit entries for events created before this fix — only new events going forward will show up.
## Summary
- `createEvent` never called `logAdminAction`, even though the frontend's audit-log page (shipped in 1.10.0) already lists `event_created` as a filterable action — only `updateEvent`/`deleteEvent` actually logged. Event creation is now logged at every return path, including the legacy pre-migration retry branches.
- Added a "Back to dashboard" link to Admin → Audit log, matching the existing back-link pattern used on the Cashup page.
- Version bumped to 1.10.3.
## Test plan
- [x] Backend Jest suite (21 tests) passes
- [x] Reviewed the diff against the existing `event_updated`/`event_deleted` logging pattern for consistency
Note: this doesn't backfill audit entries for events created before this fix — only new events going forward will show up.
https://claude.ai/code/session_01CSWFWQsjTc9GyffPiXEDQT
createEvent never called logAdminAction, even though 1.10.0 already
listed event_created as a filterable action on the audit-log page —
only updateEvent/deleteEvent actually logged. Event creation is now
logged the same way, at every return path including the legacy
pre-migration retry branches.
Also adds a "Back to dashboard" link to Admin -> Audit log, matching
the existing back-link pattern on the Cashup page.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CSWFWQsjTc9GyffPiXEDQT
Registrations can be cancelled two ways: DELETE /:id (owner or admin,
already logged registration_cancelled) and PUT /:id (staff+, status
change endpoint) — the latter was silently unlogged. Since PUT /:id
is staff-only, any transition into 'cancelled' there is inherently a
staff-initiated cancellation, so it's now logged the same way.
Audited all six categories promised in the 1.10.0 changelog entry
(refunds, donation assign/unassign, manual registrations,
staff-initiated cancellations, event create/update/delete, settings
changes) against their actual logAdminAction call sites and route
wiring — this was the only other gap found.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CSWFWQsjTc9GyffPiXEDQT
joshua
merged commit 97faff1c89 into main2026-08-28 14:49:25 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
createEventnever calledlogAdminAction, even though the frontend's audit-log page (shipped in 1.10.0) already listsevent_createdas a filterable action — onlyupdateEvent/deleteEventactually logged. Event creation is now logged at every return path, including the legacy pre-migration retry branches.Test plan
event_updated/event_deletedlogging pattern for consistencyNote: this doesn't backfill audit entries for events created before this fix — only new events going forward will show up.
https://claude.ai/code/session_01CSWFWQsjTc9GyffPiXEDQT