I have no idea if upgrading from 115 to 128 is broken like it is going from 127 to 128. Maybe follow the same steps as release to be safe idk.
The portable builds are fully portable, the profile directory is inside the browser folder. It does not touch appdata at all.
Notable bugs:
The 32 bit build is built with --disable-sandbox. With the sandbox enabled under Vista, the browser fails to open multiple processes which breaks the browser. The 64 bit build is fine. Considering Mypal68 globally disables the sandbox, I don't think it's that bad. If this really is a big issue then please pr a fix.
Changes on top of the previous 128.2.0rc build:
New ESR (orange) icons are included.
New color schemes are included, ESR (orange), and Plasmafox (pinkish-purple)
Added the ability to enable/disable the r3dfox theme's drag space.
All new r3dfox features from 130.x:
Moving the profile folder should not break extensions anymore.
r3dfox is now compiled with accessibility services included again.
Accessibility is disabled by default for more security and performance, however there is now a GUI option for enabling/disabling it.
There are no more blacklisted ports, except for 0.
Beacon web tracking is disabled. (beacon.enabled is set to false)
Translucent design works with light mode now.
Haven't tested on XP (OCAPI) nor have I extensively stability tested.
Please let me know what bugs or issues you encounter with it.