@omnibase/core-js 0.9.2 → 0.9.3

package/dist/esm/models/TenantsUpdateRoleRequest.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/TenantsUpdateTenantUserRoleRequest.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/TenantsUpdateTenantUserRoleRequest.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/TenantsUpdateTenantUserRoleResponse.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -20,7 +20,7 @@ export interface TenantsUpdateTenantUserRoleResponse {
      * @type {string}
      * @memberof TenantsUpdateTenantUserRoleResponse
      */
-    message?: string;
+    message: string;
 }
 /**
  * Check if a given object implements the TenantsUpdateTenantUserRoleResponse interface.

package/dist/esm/models/TenantsUpdateTenantUserRoleResponse.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -15,6 +15,8 @@
  * Check if a given object implements the TenantsUpdateTenantUserRoleResponse interface.
  */
 export function instanceOfTenantsUpdateTenantUserRoleResponse(value) {
+    if (!('message' in value) || value['message'] === undefined)
+        return false;
     return true;
 }
 export function TenantsUpdateTenantUserRoleResponseFromJSON(json) {
@@ -25,7 +27,7 @@ export function TenantsUpdateTenantUserRoleResponseFromJSONTyped(json, ignoreDis
         return json;
     }
     return {
-        'message': json['message'] == null ? undefined : json['message'],
+        'message': json['message'],
     };
 }
 export function TenantsUpdateTenantUserRoleResponseToJSON(json) {

package/dist/esm/models/UpdateTenantUserRole200Response.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/UpdateTenantUserRole200Response.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/V1ArchiveAllResponse.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -20,31 +20,31 @@ export interface V1ArchiveAllResponse {
      * @type {Array<string>}
      * @memberof V1ArchiveAllResponse
      */
-    archiveErrors?: Array<string>;
+    archiveErrors: Array<string>;
     /**
      * List of successfully archived items
      * @type {Array<string>}
      * @memberof V1ArchiveAllResponse
      */
-    archivedItems?: Array<string>;
+    archivedItems: Array<string>;
     /**
      * Success message
      * @type {string}
      * @memberof V1ArchiveAllResponse
      */
-    message?: string;
+    message: string;
     /**
      * Total number of archived items
      * @type {number}
      * @memberof V1ArchiveAllResponse
      */
-    totalArchived?: number;
+    totalArchived: number;
     /**
      * Total number of errors
      * @type {number}
      * @memberof V1ArchiveAllResponse
      */
-    totalErrors?: number;
+    totalErrors: number;
     /**
      * Warning message if there were errors
      * @type {string}

package/dist/esm/models/V1ArchiveAllResponse.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -15,6 +15,16 @@
  * Check if a given object implements the V1ArchiveAllResponse interface.
  */
 export function instanceOfV1ArchiveAllResponse(value) {
+    if (!('archiveErrors' in value) || value['archiveErrors'] === undefined)
+        return false;
+    if (!('archivedItems' in value) || value['archivedItems'] === undefined)
+        return false;
+    if (!('message' in value) || value['message'] === undefined)
+        return false;
+    if (!('totalArchived' in value) || value['totalArchived'] === undefined)
+        return false;
+    if (!('totalErrors' in value) || value['totalErrors'] === undefined)
+        return false;
     return true;
 }
 export function V1ArchiveAllResponseFromJSON(json) {
@@ -25,11 +35,11 @@ export function V1ArchiveAllResponseFromJSONTyped(json, ignoreDiscriminator) {
         return json;
     }
     return {
-        'archiveErrors': json['archive_errors'] == null ? undefined : json['archive_errors'],
-        'archivedItems': json['archived_items'] == null ? undefined : json['archived_items'],
-        'message': json['message'] == null ? undefined : json['message'],
-        'totalArchived': json['total_archived'] == null ? undefined : json['total_archived'],
-        'totalErrors': json['total_errors'] == null ? undefined : json['total_errors'],
+        'archiveErrors': json['archive_errors'],
+        'archivedItems': json['archived_items'],
+        'message': json['message'],
+        'totalArchived': json['total_archived'],
+        'totalErrors': json['total_errors'],
         'warning': json['warning'] == null ? undefined : json['warning'],
     };
 }

package/dist/esm/models/V1CheckPermissionRequest.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/V1CheckPermissionRequest.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/V1CheckPermissionResponse.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -20,7 +20,7 @@ export interface V1CheckPermissionResponse {
      * @type {boolean}
      * @memberof V1CheckPermissionResponse
      */
-    allowed?: boolean;
+    allowed: boolean;
 }
 /**
  * Check if a given object implements the V1CheckPermissionResponse interface.

package/dist/esm/models/V1CheckPermissionResponse.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -15,6 +15,8 @@
  * Check if a given object implements the V1CheckPermissionResponse interface.
  */
 export function instanceOfV1CheckPermissionResponse(value) {
+    if (!('allowed' in value) || value['allowed'] === undefined)
+        return false;
     return true;
 }
 export function V1CheckPermissionResponseFromJSON(json) {
@@ -25,7 +27,7 @@ export function V1CheckPermissionResponseFromJSONTyped(json, ignoreDiscriminator
         return json;
     }
     return {
-        'allowed': json['allowed'] == null ? undefined : json['allowed'],
+        'allowed': json['allowed'],
     };
 }
 export function V1CheckPermissionResponseToJSON(json) {

package/dist/esm/models/V1ConfigHistoryItem.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -27,13 +27,13 @@ export interface V1ConfigHistoryItem {
      * @type {string}
      * @memberof V1ConfigHistoryItem
      */
-    createdAt?: string;
+    createdAt: string;
     /**
      * Configuration ID
      * @type {string}
      * @memberof V1ConfigHistoryItem
      */
-    id?: string;
+    id: string;
     /**
      * Parse error if configuration is invalid
      * @type {string}
@@ -45,13 +45,13 @@ export interface V1ConfigHistoryItem {
      * @type {string}
      * @memberof V1ConfigHistoryItem
      */
-    updatedAt?: string;
+    updatedAt: string;
     /**
      * Configuration version
      * @type {string}
      * @memberof V1ConfigHistoryItem
      */
-    version?: string;
+    version: string;
 }
 /**
  * Check if a given object implements the V1ConfigHistoryItem interface.

package/dist/esm/models/V1ConfigHistoryItem.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -16,6 +16,14 @@ import { ModelsStripeConfigurationWithIDsFromJSON, ModelsStripeConfigurationWith
  * Check if a given object implements the V1ConfigHistoryItem interface.
  */
 export function instanceOfV1ConfigHistoryItem(value) {
+    if (!('createdAt' in value) || value['createdAt'] === undefined)
+        return false;
+    if (!('id' in value) || value['id'] === undefined)
+        return false;
+    if (!('updatedAt' in value) || value['updatedAt'] === undefined)
+        return false;
+    if (!('version' in value) || value['version'] === undefined)
+        return false;
     return true;
 }
 export function V1ConfigHistoryItemFromJSON(json) {
@@ -27,11 +35,11 @@ export function V1ConfigHistoryItemFromJSONTyped(json, ignoreDiscriminator) {
     }
     return {
         'config': json['config'] == null ? undefined : ModelsStripeConfigurationWithIDsFromJSON(json['config']),
-        'createdAt': json['created_at'] == null ? undefined : json['created_at'],
-        'id': json['id'] == null ? undefined : json['id'],
+        'createdAt': json['created_at'],
+        'id': json['id'],
         'parseError': json['parse_error'] == null ? undefined : json['parse_error'],
-        'updatedAt': json['updated_at'] == null ? undefined : json['updated_at'],
-        'version': json['version'] == null ? undefined : json['version'],
+        'updatedAt': json['updated_at'],
+        'version': json['version'],
     };
 }
 export function V1ConfigHistoryItemToJSON(json) {

package/dist/esm/models/V1ConfigHistoryPagination.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -20,37 +20,37 @@ export interface V1ConfigHistoryPagination {
      * @type {boolean}
      * @memberof V1ConfigHistoryPagination
      */
-    hasNext?: boolean;
+    hasNext: boolean;
     /**
      * Whether there is a previous page
      * @type {boolean}
      * @memberof V1ConfigHistoryPagination
      */
-    hasPrev?: boolean;
+    hasPrev: boolean;
     /**
      * Current page number
      * @type {number}
      * @memberof V1ConfigHistoryPagination
      */
-    page?: number;
+    page: number;
     /**
      * Items per page
      * @type {number}
      * @memberof V1ConfigHistoryPagination
      */
-    perPage?: number;
+    perPage: number;
     /**
      * Total number of configurations
      * @type {number}
      * @memberof V1ConfigHistoryPagination
      */
-    total?: number;
+    total: number;
     /**
      * Total pages
      * @type {number}
      * @memberof V1ConfigHistoryPagination
      */
-    totalPages?: number;
+    totalPages: number;
 }
 /**
  * Check if a given object implements the V1ConfigHistoryPagination interface.

package/dist/esm/models/V1ConfigHistoryPagination.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -15,6 +15,18 @@
  * Check if a given object implements the V1ConfigHistoryPagination interface.
  */
 export function instanceOfV1ConfigHistoryPagination(value) {
+    if (!('hasNext' in value) || value['hasNext'] === undefined)
+        return false;
+    if (!('hasPrev' in value) || value['hasPrev'] === undefined)
+        return false;
+    if (!('page' in value) || value['page'] === undefined)
+        return false;
+    if (!('perPage' in value) || value['perPage'] === undefined)
+        return false;
+    if (!('total' in value) || value['total'] === undefined)
+        return false;
+    if (!('totalPages' in value) || value['totalPages'] === undefined)
+        return false;
     return true;
 }
 export function V1ConfigHistoryPaginationFromJSON(json) {
@@ -25,12 +37,12 @@ export function V1ConfigHistoryPaginationFromJSONTyped(json, ignoreDiscriminator
         return json;
     }
     return {
-        'hasNext': json['has_next'] == null ? undefined : json['has_next'],
-        'hasPrev': json['has_prev'] == null ? undefined : json['has_prev'],
-        'page': json['page'] == null ? undefined : json['page'],
-        'perPage': json['per_page'] == null ? undefined : json['per_page'],
-        'total': json['total'] == null ? undefined : json['total'],
-        'totalPages': json['total_pages'] == null ? undefined : json['total_pages'],
+        'hasNext': json['has_next'],
+        'hasPrev': json['has_prev'],
+        'page': json['page'],
+        'perPage': json['per_page'],
+        'total': json['total'],
+        'totalPages': json['total_pages'],
     };
 }
 export function V1ConfigHistoryPaginationToJSON(json) {

package/dist/esm/models/V1ConfigHistoryResponse.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -22,13 +22,13 @@ export interface V1ConfigHistoryResponse {
      * @type {Array<V1ConfigHistoryItem>}
      * @memberof V1ConfigHistoryResponse
      */
-    configs?: Array<V1ConfigHistoryItem>;
+    configs: Array<V1ConfigHistoryItem>;
     /**
      * Pagination information
      * @type {V1ConfigHistoryPagination}
      * @memberof V1ConfigHistoryResponse
      */
-    pagination?: V1ConfigHistoryPagination;
+    pagination: V1ConfigHistoryPagination;
 }
 /**
  * Check if a given object implements the V1ConfigHistoryResponse interface.

package/dist/esm/models/V1ConfigHistoryResponse.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -17,6 +17,10 @@ import { V1ConfigHistoryPaginationFromJSON, V1ConfigHistoryPaginationToJSON, } f
  * Check if a given object implements the V1ConfigHistoryResponse interface.
  */
 export function instanceOfV1ConfigHistoryResponse(value) {
+    if (!('configs' in value) || value['configs'] === undefined)
+        return false;
+    if (!('pagination' in value) || value['pagination'] === undefined)
+        return false;
     return true;
 }
 export function V1ConfigHistoryResponseFromJSON(json) {
@@ -27,8 +31,8 @@ export function V1ConfigHistoryResponseFromJSONTyped(json, ignoreDiscriminator)
         return json;
     }
     return {
-        'configs': json['configs'] == null ? undefined : (json['configs'].map(V1ConfigHistoryItemFromJSON)),
-        'pagination': json['pagination'] == null ? undefined : V1ConfigHistoryPaginationFromJSON(json['pagination']),
+        'configs': (json['configs'].map(V1ConfigHistoryItemFromJSON)),
+        'pagination': V1ConfigHistoryPaginationFromJSON(json['pagination']),
     };
 }
 export function V1ConfigHistoryResponseToJSON(json) {
@@ -39,7 +43,7 @@ export function V1ConfigHistoryResponseToJSONTyped(value, ignoreDiscriminator =
         return value;
     }
     return {
-        'configs': value['configs'] == null ? undefined : (value['configs'].map(V1ConfigHistoryItemToJSON)),
+        'configs': (value['configs'].map(V1ConfigHistoryItemToJSON)),
         'pagination': V1ConfigHistoryPaginationToJSON(value['pagination']),
     };
 }

package/dist/esm/models/V1CreateCheckoutRequest.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/V1CreateCheckoutRequest.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/V1CreateCheckoutResponse.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -20,13 +20,13 @@ export interface V1CreateCheckoutResponse {
      * @type {string}
      * @memberof V1CreateCheckoutResponse
      */
-    sessionId?: string;
+    sessionId: string;
     /**
      * Stripe Checkout Session URL
      * @type {string}
      * @memberof V1CreateCheckoutResponse
      */
-    url?: string;
+    url: string;
 }
 /**
  * Check if a given object implements the V1CreateCheckoutResponse interface.

package/dist/esm/models/V1CreateCheckoutResponse.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -15,6 +15,10 @@
  * Check if a given object implements the V1CreateCheckoutResponse interface.
  */
 export function instanceOfV1CreateCheckoutResponse(value) {
+    if (!('sessionId' in value) || value['sessionId'] === undefined)
+        return false;
+    if (!('url' in value) || value['url'] === undefined)
+        return false;
     return true;
 }
 export function V1CreateCheckoutResponseFromJSON(json) {
@@ -25,8 +29,8 @@ export function V1CreateCheckoutResponseFromJSONTyped(json, ignoreDiscriminator)
         return json;
     }
     return {
-        'sessionId': json['session_id'] == null ? undefined : json['session_id'],
-        'url': json['url'] == null ? undefined : json['url'],
+        'sessionId': json['session_id'],
+        'url': json['url'],
     };
 }
 export function V1CreateCheckoutResponseToJSON(json) {

package/dist/esm/models/V1CreatePortalRequest.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/V1CreatePortalRequest.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/V1CreatePortalResponse.d.ts

@@ -2,7 +2,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/esm/models/V1CreatePortalResponse.js

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.2
+ * The version of the OpenAPI document: 0.9.3
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).