diff --git a/.github/workflows/install-validation.yml b/.github/workflows/install-validation.yml
index f685235..3c368a8 100644
--- a/.github/workflows/install-validation.yml
+++ b/.github/workflows/install-validation.yml
@@ -16,7 +16,7 @@ on:
version:
description: Expected candidate version
required: true
- default: '0.6.2.2'
+ default: '0.6.2.3'
type: string
permissions:
diff --git a/FORK.md b/FORK.md
index 5874655..21d9efd 100644
--- a/FORK.md
+++ b/FORK.md
@@ -75,10 +75,10 @@ authentication is configured. Clients that resolve
`localhost` only to `::1` need `127.0.0.1` (documented). A second loopback connector
on `::1` is a possible follow-up, not part of this release.
-## Next queue (unreleased)
+## 0.6.2.3 queue
Base: the shipped fork release `v0.6.2.2` (`b3c01ce`). Everything above carries forward.
-No release is tagged for this queue yet; tagging needs the Wheels release owner's go.
+Candidate prepared 2026-10-08. It is tagged only after the Wheels release owner's go (see Release).
| Order | Change | Purpose |
|---|---|---|
@@ -103,6 +103,14 @@ today's LuCLI. Only then does a Wheels build pin a LuCLI with row 8: before #398
strict argument parsing rejects the marker (`toArgv()` turns it into `--__lucliMcpCall`), so
every MCP `tools/call` would fail.
+Compatibility (row 8): a Wheels build must handle `__lucliMcpCall` before it pins 0.6.2.3.
+Wheels develop does (wheels-dev/wheels#3980). Wheels 4.1.x (v4.1.2 pins 0.6.2.1) does not,
+so 4.1.x stays at **max 0.6.2.2** unless #3980 is backported.
+
+## Next queue (unreleased)
+
+Base: the shipped fork release `v0.6.2.3`, once tagged. Empty.
+
## Approved patch mapping
Stable patch IDs (original → assembled); a differing ID below is only diff
diff --git a/pom.xml b/pom.xml
index 1d31dab..37a2fcc 100644
--- a/pom.xml
+++ b/pom.xml
@@ -6,7 +6,7 @@
org.lucee
lucli
- 0.6.2.2
+ 0.6.2.3
LuCLI