Possibly because the latest release of sage-installer is more recent than the latest release of sage, and it wouldn’t be an efficient use of the team’s time to go through and update versions in composer files when you can just run composer update?
Time? I could make that PR in 5 minutes. If Sage 9 is out of date, maybe the docs should warn that you need to run additional commands to not get out of date dependencies if you follow the guide.
Would you need to choose no preset to rerun the latest Tailwind preset?
Tailwind is massively popular, and if you follow the Sage install guide you’ll end up with a beta release, which seems like a pretty big issue to me.