Relock monorepo pins to ^0.21
A caret pin is a RANGE WITH AN UPPER BOUND: ^0.20 means >=0.20.0 <0.21.0, which the 0.21.0 runtime does NOT satisfy. The sigil: field is a different thing -- a MINIMUM, no upper bound -- so bare "0.20" there stays correct and only the dependency pins move.
Monorepo packages are not independently versioned; they advance in lockstep with the toolchain. Standalone libraries are NOT touched: sigil-http, sigil-json, sigil-tls, sigil-crypto and the rest version on their own cadence, and requesting ^0.21 of them asks for something that has never existed.
Found via kiln, the only repo in the estate whose pipeline greps deps.log and promotes an unmet-constraint warning to a failure. Every other repo emits the same warning under sigil test and passes, so the skew was estate-wide and visible in exactly one place.
Verified per repo: deps install reports ZERO unmet constraints.
Known limitation, recorded rather than hidden: ^0.21 excludes 0.22 in turn, so this recurs on the next toolchain bump. A minimum form (>=0.20) was measured working -- zero warnings, build ok, suite green -- and deferred by David 2026-09-02 in favour of matching the estate's existing spelling.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P6mPymR1ZBRV1nuyDpBxDF
package.sgl | 2 +-
sigil.lock | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)package.sglmodified
(package name: "sigil-markdown" version: "0.9.5" sigil: "^0.17" sigil: "0.20" description: "Markdown and frontmatter parser" url: "https://codeberg.org/sigil/sigil-markdown" license: "BSD-3-Clause"sigil.lockmodified
(package name: "sigil-stdlib" url: "codeberg:sigil/sigil" ref: "^0.9.0" sha: "54f66e8ec446b65b75ab6f12454d2c0aa269f2c0" sha: "0123d3fc7d2dd37e5c27e9fade7d11b817deb21a" package-selector: "sigil-stdlib" version: "0.9.1") version: "0.9.2"))