Might provide a full run-down on what Sansani (Steel OS 3) will bring to the table soon, and I might share plans for a further, 4th major release of Steel OS, likely to be called Steel OS 4, but will be referred to as "Waterfall", the codename for that specific major version (4.0). 

All I can confirm about Steel OS 4 for now is (1) it will be based off of an advanced 64-bit adaptation of the 32-bit Steel32 technology (basically things like the kernel, services, etc.), (2) has a very good chance of retaining whatever ends up as Sansani's default visual style, and (3) will likely get at least 2 service releases, as service releases work differently by incrementing part of the version number, making SR-2 identify the system as Steel OS 4.2 (as a member of my Discord server joked that the brand new computer they got came with a copy of Steel OS 4.20) 

For example, an SR-2 release of Steel OS 1.2 would identify as Steel OS 1.22, but an SR-1 release for Sansani would identify as Steel OS 3.1, that is if you use the same version reporting software to grab the software version, as an SR-1 release of Sansani would still be badged as Steel OS 3, just with "SR-1" added to system identification in some areas, e.g. installation/recovery media).

Official Knowledge Base

Knowledge Base article ID 000001

Affected systems: Steel OS 1.0 (potentially), Steel OS 1.2 RTM (potentially), Steel OS 1.73 (potentially), Steel OS 2.0, Steel OS 2.3, Steel OS 2.51
Affected component: Shutdown
Solution: Shut down via the "Force Stop Now" or "Terminate" menu option.
Note: Sansani had this issue, but she had it patched (in build 3.0.2552)

Overview

A few days ago, while using various versions of Steel OS, I encountered an issue with shutting down. When I went to shut down normally, the system would automatically act like a key was hit, proceeding the reboot the system without any key input. I had previously run into the issue when using Sansani, specifically when I installed all installables on her, but I patched this bug over on her field of the Steel OS development and support already. I thought that was the end of it, as I thought it had been patched after the bug-filled Steel OS 2.0 Beta 2 Build 997 (which had a further issue where clicking "Restart" would soft-lock the OS, thus meaning that Steel OS 2.0 Build 997 is the closest Steel OS has ever gotten to Windows Longhorn levels of being unstable).

Well, fast-forward a few days, when I was screwing around in Steel OS 2.0 and a modded copy of Steel OS 2.3. Guess what happened when I went to click "Shut Down"? That's right, the issue appeared AGAIN. I did a thorough bug test of Steel OS 1.2 prior to this so that Steel OS 1.2 SR-1 could have the most streamlined experience of Steel OS 1.2, and the bug didn't show up. This bug likely will pop up when you change enough system settings (it could be even just down to the cursor, as various cursor schemes aren't well-maintained), but a known patch exists - Dump the old "hit a key to restart" and replace it with a restart button (this existed in pre-release versions of Steel OS 1.0), and this has already been added to Sansani, but will have to be added into the SR-1 releases of Steel OS 1.2, 2.3, and 2.51. It will not be patched in other versions, as any non-Sansani and non-mentioned-just-above-this-line-of-text version is both out-of-service and no longer in development.

Solution

Don't worry, this will be patched in the next set of bug patches for 1.2, 2.3, and 2.51, and will be clearly seen in the next released Sansani Hagane (Steel OS 3, but remember, the 2023-07-08 devlog post!!) build.

Summary

An issue exists in most pre-Steel64 versions of Steel OS where if enough changes away from the stock configuration of the respective version are made, it may cause the system to auto-reboot on shutdown.