## Summary
- Remove `expiryDate` from the public API (OpenAPI spec, create request, frontend form)
- Backend auto-calculates expiry as `eventDate + 7 days` in the service layer
- Clean up all related frontend/backend tests (~400 lines removed)
## Test plan
- [ ] Backend unit + integration tests pass
- [ ] Frontend unit + E2E tests pass
- [ ] Creating an event no longer requires/shows expiry date field
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The expiry date is no longer user-facing: it is removed from the API
(request and response) and the frontend. The backend now automatically
calculates it as the event date plus 7 days. The expired banner and
RSVP-bar filtering by expired status are also removed from the UI,
since expiry is purely an internal data-retention mechanism.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
nitrix
merged commit 2a6a658df9 into master2026-03-09 21:33:43 +01: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
expiryDatefrom the public API (OpenAPI spec, create request, frontend form)eventDate + 7 daysin the service layerTest plan
🤖 Generated with Claude Code