[bpamiri]

Release prep for the 0.6.2.4 candidate, as #29 did for 0.6.2.3. Nothing is tagged or published until the Wheels release owner's go (FORK.md "Release").

• pom.xml version 0.6.2.4 (the Windows file/product version follows ${project.version}).
• install-validation.yml default version 0.6.2.4.
• FORK.md:
  • "Next queue" becomes the 0.6.2.4 queue: row 16 = build(deps): dependency updates #30, the dependency updates ported from upstream security: remediate Maven dependency CVEs (#156) cybersonic/LuCLI#157.
  • Compatibility is unchanged: Wheels 4.1.x stays at max 0.6.2.2.
  • A new empty Next queue is added.
• CHANGELOG.md unchanged: fork entries stay under Unreleased, as for 0.6.2.3.

The branch has wheels @ b046b44 (#30) merged in, so the diff is only these three files.

Next, after merge: release.yml publish=false (dry run), then install-validation.yml source=candidate, then the A/B against Wheels.

🤖 Generated with Claude Code

[github-actions]

Unit Tests (ubuntu-latest, Java 21)

 65 files   65 suites   2m 24s ⏱️
783 tests 777 ✅ 6 💤 0 ❌
788 runs  782 ✅ 6 💤 0 ❌

Results for commit f84cc60.

[github-actions]

Integration Tests (ubuntu-latest, Java 21)

78 tests   78 ✅  2m 9s ⏱️
14 suites   0 💤
 1 files     0 ❌

Results for commit f84cc60.

[bpamiri]

rev1-r3 review @ f84cc60: APPROVE

The diff against wheels (b046b44, which includes #30) is exactly the release prep: three files, +15/-3.

• pom.xml: 0.6.2.3 → 0.6.2.4.
• install-validation.yml: the version default 0.6.2.3 → 0.6.2.4. No other 0.6.2.3 reference remains outside CHANGELOG and the FORK.md history.
• FORK.md:
  • A new "0.6.2.4 queue" section has base v0.6.2.3 (350ded0; the tag resolves there). It gets row 16: build(deps): dependency updates #30, the upstream security: remediate Maven dependency CVEs (#156) cybersonic/LuCLI#157 port, described as in build(deps): dependency updates #30 (Jackson 2.18.11, JLine 3.30.15, and tomcat-embed-core 9.0.121 / commons-lang3 3.18.0 via dependencyManagement).
  • The compatibility line is unchanged: 4.1.x stays at max 0.6.2.2.
  • It notes that row 16 drops out on a rebase onto an upstream release containing security: remediate Maven dependency CVEs (#156) cybersonic/LuCLI#157.
  • "Next queue" now bases on v0.6.2.4.
  • Leaving row 16 out of "Approved patch mapping" is consistent with 0.6.2.3: that table only maps the 0.6.2.1 base-assembly cherry-picks.

The branch merges wheels in and is up to date. CI: Build, Unit Tests and Integration Tests pass on ubuntu, macOS and Windows; APT Install Smoke is skipped. MERGEABLE. Nothing is published by this PR; tagging follows the Release section after the release owner's go.