@dgp1130 Kindly review and merge.

We should probably add a test for the changed behavior as well, but that can come in a separate PR, no need to hold up this one for it.

@alan-agius4 Is this fix published and available to run the builds?

@srinivasreddyp, the release is ongoing. We have a large number of packages, multiple versions to publish, and a wide variety of end-to-end tests which take some time to run before we can be confident in a release.

12.2.16 was just published which should contain the fix for users on v12.
The v13 release is still in progress, I'll post an update here when it lands.
Users on v11 shouldn't be affected by this bug.

@srinivasreddyp, the release is ongoing. We have a large number of packages, multiple versions to publish, and a wide variety of end-to-end tests which take some time to run before we can be confident in a release.

12.2.16 was just published which should contain the fix for users on v12. The v13 release is still in progress, I'll post an update here when it lands. Users on v11 shouldn't be affected by this bug.

Thank you for the update, we are on 12.

v13.2.1 just landed and has the same fix.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}