Revert "feat: upgrade to Gestalt 8" #5270
Merged
Conversation
This file contains 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
This reverts commit 7f47891.
jdrueckert
added
the
Type: Chore
github-actions
bot
added
the
Type: Improvement
jdrueckert
added a commit
that referenced
this pull request
Aug 3, 2024
jdrueckert
added a commit
that referenced
this pull request
Aug 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reverts #5267
We currently do not have an explicit dependency of modules on specific engine versions.
Modules implicitly depend on the latest engine build.
With this PR already merged, it is not possible to build and release modules without the associated required gestalt 8 upgrade module changes.
Reverting this to first publish those pre-gestalt-8-upgrade module versions.
Afterwards we can merge the engine PR for the gestalt 8 upgrade again and then the associated module PRs for the gestalt 8 upgrade according to the module dependency chain (Inventory first, then Behaviors and Furnishings in arbitrary order)