v2.1.1
A patch release fixing two multi-tenant issues surfaced in a real @payloadcms/plugin-multi-tenant install. No breaking changes — plain single-tenant installs are unaffected.
Fixed
- Customer search is now tenant-scoped. The
/api/reservation-customer-searchendpoint (used by the reservation customer picker) restricts results to the selected tenant — read from the tenant cookie — whenever the customers collection carries the multi-tenanttenantfield. This prevents picking a customer from another tenant, which would otherwise fail on save with a tenant mismatch. Plain single-tenant installs are unaffected (no tenant field / no cookie ⇒ no scoping). - Flexible-duration reservations can be saved from the admin UI. The reservation
endTimefield was unconditionally read-only, which contradicted thecalculateEndTimevalidation that requires a user-suppliedendTimeforflexible-duration services.endTimeis now editable; forfixed/full-dayservices it is still auto-computed and overwritten on save.