Twig conflict

Hello. Thank you for the great plugin. The last update caused the conflict between Upstream plugins and Data Tables generator (we use free and pro version). WP informed about the technical issue and allowed to work only one plugin (Upstream or Data Tables Generator). “Plugins load order” plugin with moving of Data Tables Generators to the bottom of order temporary decides some issues but not all of them.
After contact with the Upstream team, it was found that the problem is caused by the conflict between the Twig library used by UpStream and Data Tables Generator. Data Tables generator uses an old version of the library, released in 2017 while Upstream uses the version 1.38.4. Unfortunately, both versions can’t run together. Support recommended informing Supsystic team about the update to new version of this library.

Below you may find the error message generated by WP 5.2:
Error details
===================================
Error type E_ERROR in raw 56 of file …/wordpress_5/public_html/wp-content/plugins/upstream/vendor/twig/twig/src/Lexer.php.

Message: Uncaught TypeError: Argument 1 passed to Twig\Lexer::__construct() must be an instance of Twig\Environment, instance of Twig_Environment given, called in …/wordpress_5/public_html/wp-content/plugins/data-tables-generator-by-supsystic/vendor/Twig/Environment.php on line 650 and defined in …/wordpress_5/public_html/wp-content/plugins/upstream/vendor/twig/twig/src/Lexer.php:56
Stack trace:
#0 …/wordpress_5/public_html/wp-content/plugins/data-tables-generator-by-supsystic/vendor/Twig/Environment.php(650): Twig\Lexer->__construct(Object(Twig_Environment))
#1 …/wordpress_5/public_html/wp-content/plugins/data-tables-generator-by-supsystic/vendor/Twig/Environment.php(750): Twig_Environment->tokenize(Object(Twig\Source))
#2 …/wordpress_5/public_html/wp-content/plugins/data-tables-generator-by-supsystic/vendor/Twig/Environment.php(447): Twig_Environment->compileSource(Object(Twig\Source))
#3 …/wordpress_5/public_html/wp-content/plugins/

Could you include fix of this issue in next update of the plugin? We really need it daily in our work.

Thank you