Repository navigation
Complete 2.6.0 docs and fix release ordering and Windows journal locking - #19
Merged
Merged
Conversation
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.
Complete the 2.6.0 documentation and fix release workflow races: Maven preparation could validate POMs before regeneration finished, and concurrent journal reads/updates could fail on Windows. Git output now uses explicit UTF-8 decoding so non-ASCII paths and diagnostics remain correct under JDK 17 with a non-UTF-8 default charset.
Validation of the final changes:
The added Windows x64/JDK 17 CI job covers the default Windows charset/runtime combination; local VM results establish ARM64/JDK 21 coverage.