Hello, thank you for bringing this to our attention! We have investigated the issue reported in 6000.4 and can confirm that a fix has been implemented in version 6000.6.0a5 and all subsequent releases.Regarding a backport to previous versions: after careful evaluation by the team, we have decided not to backport this specific fix. The systems involved have diverged significantly, making a direct backport exceptionally complex. Attempting to force this fix into the previous versions carries an extremely high risk of introducing regressions and ripple effects that could compromise the stability for all users.If this issue is severely impacting your project, we recommend upgrading to 6000.6.0a5 or a newer release to take advantage of the fix. Thank you for your understanding, and please feel free to reach out if you have any questions!