Fix for version file for launcher + increment to next major release #4672
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.
This quick-fixes Terasology/Index#16 and should let the launcher identify newer Omega zips from Jenkins, as the
versionInfo.properties
is again attached from a slightly updated path then retrieved during the Omega zip making.Goes with Terasology/Index#17
Additionally I think we're overdue for bumping the engine version to the next major, considering the next release will include the major upgrade to Gestalt v7, that definitely deserves a bump.
If no objections we should also adjust the current milestone accordingly: https://github.com/MovingBlocks/Terasology/milestones/45/edit
And I think #4509 should probably be closed as complete as part of that? I know there are still leftovers floating around, but that core issue seems to deserve its finished status 👍
Omega fix confirmed with https://jenkins.terasology.io/teraorg/job/Nanoware/job/Omega/job/develop/34/