feat(backend): Mark setPasswordCompromised and unsetPasswordCompromised as stable (#7504)

Author: octoper

.changeset/curly-hornets-argue.md

@@ -0,0 +1,5 @@
+---
+'@clerk/backend': patch
+---
+
+Dropping the `__experimental_` prefix from `setPasswordCompromised` and `unsetPasswordCompromised` and marking them as stable

integration/testUtils/usersService.ts

@@ -237,7 +237,7 @@ export const createUserService = (clerkClient: ClerkClient) => {
       } satisfies FakeAPIKey;
     },
     setPasswordCompromised: async (userId: string) => {
-      await clerkClient.users.__experimental_setPasswordCompromised(userId);
+      await clerkClient.users.setPasswordCompromised(userId);
     },
   };
 

packages/backend/src/api/endpoints/UserApi.ts

@@ -452,7 +452,7 @@ export class UserAPI extends AbstractAPI {
     });
   }
 
-  public async __experimental_setPasswordCompromised(
+  public async setPasswordCompromised(
     userId: string,
     params: SetPasswordCompromisedParams = {
       revokeAllSessions: false,
@@ -466,7 +466,7 @@ export class UserAPI extends AbstractAPI {
     });
   }
 
-  public async __experimental_unsetPasswordCompromised(userId: string) {
+  public async unsetPasswordCompromised(userId: string) {
     this.requireId(userId);
     return this.request<User>({
       method: 'POST',