Release v1.1.2 - #19
Merged
Merged
Conversation
feat: import server.properties and open server data in Explorer
fix: prevent stale CLI output behind home TUI screens
Keep imported server.properties managed by server.env
Fix Explorer false errors and keep settings failures visible
Keep repository text files in LF on Windows and WSL
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
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 changes
v1.1.2 adds import of a distributed
server.propertiesfrom Server settings or the CLI. Managed values are converted toserver.env, additional entries go intoCUSTOM_SERVER_PROPERTIES, and the previous data file is backed up. Server folders and persistent data can now be opened in Windows Explorer.The release also keeps Docker errors visible in the TUI, fixes Explorer's empty error dialog and stale screen transitions, and enforces LF checkout for text files on Windows and WSL.
Validation
The release branch has passed CI on PRs #14–#18. The main-targeting
testcheck must pass before merge. The tag-triggered Release workflow will rerun syntax, ShellCheck, locale, and specification tests before publishing the archive and SHA-256 file.