The JSON.stringify issue has been resolved, sorry for the inconvenience.

A change was rolled out to Clerk's frontend SDKs that caused the results of calling JSON.stringify on Clerk's core resource objects from the frontend to return snake_case keys instead of camelCase keys (for example, within a client component). If your code was relying on the format for the keys of stringified Clerk resource objects, this was a breaking change.

While we marked the affected service as the Frontend API, the API itself was not impacted, only SDKs.