Relaticle

Fixes

Chat: Scope custom-field writes to the action’s tenant on approval (#320)

Action approvals run through the /chat/actions/* routes, which bypass Filament’s panel middleware and therefore leave no tenant context. Without one, the custom-fields TenantScope no-ops and saveCustomFields() iterates every tenant’s field definitions — writing custom-field value rows across all tenants (cross-tenant data leak) and, at scale, exceeding the request timeout (504). PendingActionService::approve() now sets the tenant context from the action’s team before executing the write and restores the prior context afterward, so the override never outlives the call.

Full Changelog: https://github.com/relaticle/relaticle/compare/v3.3.2…v3.3.3