@spiffcommerce/core 32.2.7-beta.fe525a16-f209-5cb8-95bc-b269e8ebcfcc → 32.3.0-beta.0b8f2e31-be99-5e83-b9f9-3c0530b9e37e

package/CHANGELOG.md

@@ -14,6 +14,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `Fixed` for any bug fixes.
 - `Security` in case of vulnerabilities.
 
+## [32.3.0] - 08-10-2025
+
+## Added
+
+- Added the new global function `deleteBundle` which takes a bundle id string and deletes the marks the bundle as deleted on the server.
+
 ## [32.2.6] - 08-10-2025
 
 ## Fixed

package/dist/index.d.ts

@@ -2365,6 +2365,8 @@ interface GetNewWorkflowOptionsBase extends GetWorkflowOptionsBase {
 }
 interface GetWorkflowFromIntegrationProductOptions extends GetNewWorkflowOptionsBase {
     integrationProductId: string;
+    quantity?: number;
+    recipient?: any;
     type: "integration";
 }
 interface GetWorkflowFromExternalProductOptions extends GetNewWorkflowOptionsBase {
@@ -2563,7 +2565,7 @@ declare const getOverrideThemeConfiguration: (overrideThemeConfigurationId: stri
 declare const getBundleThemeConfiguration: (bundleId: string) => Promise<ThemeInstallConfigurationGraphQl | undefined>;
 declare const getTransactionThemeConfiguration: (transactionId: string) => Promise<ThemeInstallConfigurationGraphQl | undefined>;
 /**
- * Marks the Bundle with the provided id as deleted. The Bundle's data will still persist on the server and as such it is still safe to keep a reference to this object,
+ * Marks the Bundle with the provided id as deleted. The Bundle's data will still persist on the server and as such you can still retrieve it directly via id,
  * but it will no longer be visible in list/feed queries and it can no longer be converted into an Order.
  */
 declare const deleteBundle: (id: string) => Promise<void>;