@faable/auth-sdk 2.7.74 → 2.7.75

package/dist/api/types.d.ts

@@ -19577,7 +19577,7 @@ export interface operations {
                     roles?: string[];
                     /** @description `auto` adds the user directly if they already exist in the tenant and only falls back to a ticketed invite when the email is unknown. `invite` always issues a ticket + email regardless of whether the user exists. */
                     mode?: "auto" | "invite";
-                    /** @description Where `/invite-verify` redirects the invitee after a successful accept. Must be at an origin of one of this tenant's client callbacks or `callback_hostnames`. */
+                    /** @description Where the invitee goes once in: `/invite-verify` redirects there after a successful accept, and it is the button of the "you were added" email (otherwise your auth domain). Must be at an origin of one of this tenant's client callbacks or `callback_hostnames`. */
                     redirect_uri?: string;
                     /** @description The user who is inviting, when you call on their behalf with a machine token. Shown in the invite email. Must be a user of this tenant; defaults to the token's own user. */
                     inviter_user_id?: string;

package/dist/version.js

@@ -9,13 +9,13 @@
 // login pages could not import the SDK at all. Same pattern as auth-js.
 //
 // The sentinels MUST stay byte-identical to the `from` values in `.releaserc`.
-export const version = "2.7.74";
+export const version = "2.7.75";
 // Short git SHA of the released commit. The version dates a build; this names
 // the exact tree, so a canonical log line or an audit entry leads straight to
 // `git show <sha>`. Deliberately NOT hex: an unreleased build (dev, a local
 // link) cannot be mistaken for a real commit — auth only records values that
 // look like a SHA, and this one never will.
-export const commit = "7e26e4b";
+export const commit = "4ba33ed";
 // What this SDK writes in `x-faable-client`. Exported for a consumer that
 // builds a strategy on its own (outside `FaableAuthApi`) and still wants the
 // token request attributed — a bare `authClientCredentials` stamps only what

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@faable/auth-sdk",
-  "version": "2.7.74",
+  "version": "2.7.75",
   "author": "Marc Pomar <marc@faable.com>",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/spec/openapi.json

@@ -3,7 +3,7 @@
   "info": {
     "title": "@faablecloud/auth",
     "description": "Auth Platform made by Faable. Manage Users and Roles",
-    "version": "2.59.2",
+    "version": "2.60.0",
     "license": {
       "name": "private",
       "url": "https://faable.com/docs/platform/privacy-policy"
@@ -36815,7 +36815,7 @@
                   },
                   "redirect_uri": {
                     "type": "string",
-                    "description": "Where `/invite-verify` redirects the invitee after a successful accept. Must be at an origin of one of this tenant's client callbacks or `callback_hostnames`."
+                    "description": "Where the invitee goes once in: `/invite-verify` redirects there after a successful accept, and it is the button of the \"you were added\" email (otherwise your auth domain). Must be at an origin of one of this tenant's client callbacks or `callback_hostnames`."
                   },
                   "inviter_user_id": {
                     "type": "string",