Hi Jinwoo, Thanks that makes sense to include this fix into the release.
Sai On 9/12/2026 10:18 AM, Jinwoo Hwang via dev wrote:
Hi Sai, Thank you for your help and testing efforts with RC1 and RC2. We really appreciate the time and feedback you have provided throughout the release process. The reason for RC3 is that a security vulnerability was identified at the last minute and needed to be addressed before the release could proceed. As a result, we cut RC3 to incorporate that fix. Thank you again for your support and for helping validate the release. Best regards, Jinwoo Hwang (he/him/his) SAS® Research and Development http://JinwooHwang.com<http://jinwoohwang.com/> From: Sai Boorlagadda <[email protected]> Date: Saturday, September 12, 2026 at 12:39 PM To: [email protected] <[email protected]> Subject: 2.0.3 RC3 Why? Hi Jinwoo, Could you please share why a new RC3 was cut? We were aware of the RC1 issue, and RC2 had already received two +1s, so I am not sure what triggered the creation of RC3. Understanding the cause would be very helpful for the community as we test RC3. Thanks, Sai
