@meshmakers/octo-services 3.4.380 → 3.4.410

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meshmakers/octo-services",
-  "version": "3.4.380",
+  "version": "3.4.410",
   "peerDependencies": {
     "@angular/common": "^22.0.0",
     "@angular/core": "^22.0.0",

package/types/meshmakers-octo-services.d.ts

@@ -52753,12 +52753,12 @@ declare class CommunicationService {
     deployPipelineDefinition(tenantId: string, adapterRtId: string, adapterCkTypeId: string, pipelineRtId: string, pipelineCkTypeId: string, pipelineDefinition: string | null): Promise<void>;
     /**
      * Enables or disables debug capture for a pipeline via the dedicated debug
-     * endpoint (`PATCH /pipeline/{id}/debug`). Unlike a pipeline (re)deploy —
-     * which force-enables debugging on every deploy — this persists the flag
-     * EXACTLY as requested and re-pushes the running adapter without
-     * force-enabling, so both enable and disable take effect immediately.
-     * `appliedToRunningAdapter` is false when the owning adapter is offline (the
-     * flag is still persisted and applies on the next deploy).
+     * endpoint (`PATCH /pipeline/{id}/debug`). This is the ONLY way debug capture
+     * is toggled (AB#4364): deploying a pipeline pushes the persisted flag as-is
+     * and never changes it. The endpoint persists the flag exactly as requested
+     * and re-pushes the running adapter, so both enable and disable take effect
+     * immediately. `appliedToRunningAdapter` is false when the owning adapter is
+     * offline (the flag is still persisted and applies on the next deploy).
      */
     setPipelineDebugging(tenantId: string, pipelineRtId: string, enabled: boolean): Promise<SetPipelineDebugResultDto | null>;
     /**