5.0 Stable Milestone

[nickclark2016]

We are closing in rapidly on 5.0 stable. The remaining outstanding issues that must be addressed before 5.0 are as follows:

Dependency Updates:

• curl
• libzip
• lua
• luashim
• luasocket
• mbedtls
• zlib (Update zlib to 1.3.2 #2662)

Bugs

• Path Encoding Issues Path encoding issues on Windows #1153 - Solved by Fix path encoding issues (#1153) #2654
• UTF8 on MinGW - characterset "Unicode" doesn't work properly on MINGW #2659

Features/Improvements

• VS 2026 slnx output improvements - Improve slnx format output #2653
• UTF8 Documentation - Documentation improvements around UTF-8 support #2658

If there are any other outstanding issues/PRs that should be targeted for 5.0, please link them below for discussion and potential inclusion.

[nickclark2016]

Added #2637 to the release

[betonamu-jin]

Please make a beta-9 before the official stable 5.0 release. beta-8 doesn't include the PR to generate compile_commands.json.

[nickclark2016]

Go pull the latest binaries from actions if you need it today.

[betonamu-jin]

Go pull the latest binaries from actions if you need it today.

Even if you released beta-9 today, it would take days or weeks for MSYS2 to update mingw-w64-premake (which is still at 5.0beta6-2 right now). And if the 5.0 stable release requires weeks or months to be ready, its arrival on MSYS2 will be delayed even further.

I can download it from CI, but I want my friends to be able to install all dependencies directly from pacman on MSYS2.

[nickclark2016]

We are not the ones that manage the premake release on MSYS2. Even if we were to release beta9, there's no guarantee that the next MSYS2 cycle would pick it up (they haven't picked up beta7 or beta8). We are likely about a month out from stable (at least a release candidate), so I see no point in releasing a beta9.

@samsinsane would appreciate your thoughts here as well

[betonamu-jin]

We are not the ones that manage the premake release on MSYS2. Even if we were to release beta9, there's no guarantee that the next MSYS2 cycle would pick it up (they haven't picked up beta7 or beta8). We are likely about a month out from stable (at least a release candidate), so I see no point in releasing a beta9.

@samsinsane would appreciate your thoughts here as well

If you release beta-9, I can submit a PR to ask the MSYS2 team to upgrade to beta-9. They will not agree to build against the unreleased latest Git code of Premake.

[samsinsane]

would appreciate your thoughts here as well

I agree with what you've said so far. I really don't see the logic behind another beta release. If something is bugged in the next release it won't matter if it's a beta or the stable release, we'll get a fix up and we'll do another release at some point.

[mercury233]

The fix in #2667 is necessary because os.writefile_ifnotequal is also used internally within the program and relies on its return value. However, I need help with designing tests.