Skip to content

Complete 2.6.0 docs and fix release ordering and Windows journal locking - #19

Merged
perNyfelt merged 3 commits into
mainfrom
fix/2.6-release-readiness
Nov 15, 2026
Merged

perNyfelt merged 3 commits into
mainfrom
fix/2.6-release-readiness

Conversation

@perNyfelt

@perNyfelt perNyfelt commented Nov 15, 2026 •

Copy link
Copy Markdown
Member

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.

  • Document existing-bundle properties, digest requirements, snapshots, behaviour changes and diagnostics; update plugin snippets to 2.6.0. The project version already is 2.6.0-SNAPSHOT. Keep the release heading in progress until publication.
  • Order module-mode Maven preparation after planned POM generation and bundling after Maven preparation. Document caller-managed ordering in advanced mode. Assert task presence before checking order and cover configuration-cache reuse.
  • Read journal snapshots through NIO with delete sharing. Retry any FileSystemException during atomic replacement on Windows, with 1.27 seconds of total backoff and no dependency on localized reason text. Atomic replacement is preserved; persistent locks leave the original journal unchanged and clean up temporary files. Persistent Windows failures propagate after the bounded retry; filesystem failures on other platforms propagate immediately.
  • Repeat concurrent journal updates five times; test temporary target locks, persistent target locks and a temporary file held open during replacement. Run the full combined-release test class in Windows CI.
  • Add a JDK 17/ISO-8859-1 regression for UTF-8 Git paths, guard diagnostics and stderr; it reproduced the decoding failure before the fix.

Validation of the final changes:

  • macOS ARM64, JDK 17: charset and combined release tests passed; 41 passed, three Windows-only tests skipped. Charset tests run with ISO-8859-1.
  • Ubuntu ARM64, JDK 17: forced execution of the same tests with --rerun-tasks passed; 41 passed, three Windows-only tests skipped. Build locale/encoding was UTF-8; the charset test JVM used ISO-8859-1.
  • Windows 11 ARM64 VM, JDK 21 with compilation targeting Java 17 through a temporary init script: all 44 selected tests passed (combined release tests plus two module-ordering tests), including all concurrency repetitions and three lock tests.
  • git diff --check passed.

The added Windows x64/JDK 17 CI job covers the default Windows charset/runtime combination; local VM results establish ARM64/JDK 21 coverage.

@perNyfelt
perNyfelt merged commit 46749a2 into main Nov 15, 2026
6 checks passed
@perNyfelt
perNyfelt deleted the fix/2.6-release-readiness branch November 15, 2026 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant