Remove Deprecated Fields, Values, and Outdated Documentation#2642
Merged
samsinsane merged 1 commit intopremake:masterfrom Mar 16, 2026
Merged
Remove Deprecated Fields, Values, and Outdated Documentation#2642samsinsane merged 1 commit intopremake:masterfrom
samsinsane merged 1 commit intopremake:masterfrom
Conversation
Jarod42
approved these changes
Mar 16, 2026
samsinsane
approved these changes
Mar 16, 2026
Member
samsinsane
left a comment
samsinsane
left a comment
There was a problem hiding this comment.
LGTM, @nickclark2016 merge when you're ready. My comments aren't blocking, so feel free to ignore them.
nickclark2016
force-pushed
the
5.0-remove-deprecations
branch
from
ec3f4b0 to
d169d28
Compare
Jarod42
approved these changes
Mar 16, 2026
samsinsane
approved these changes
Mar 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Deprecated fields, values, and outdated docs.
How does this PR change Premake's behavior?
Will break all scripts relying on deprecated functionality.
Anything else we should know?
Preparation for 5.0. A follow on PR will remove the
gmakelegacyexporter.Did you check all the boxes?
closes #XXXXin comment to auto-close issue when PR is merged)You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!