v0.17.2

A project that depends on sigil-nrepl was quietly getting two different Sigil runtimes in the same build. sigil-nrepl v0.17.1 pinned sigil-repl at "^0.19", and a caret has an upper bound, so sigil-repl resolved to 0.19.4 while everything else in the same tree resolved to 0.21.0. Two monorepo checkouts, one build, no warning. This release removes that upper bound, and a consumer now resolves a single runtime.

Measured on a scratch consumer pinning sigil-nrepl "^0.17", before and after:

    before   sigil-repl  ref "^0.19"   -> v0.19.4   (c9719987)
             plus                         v0.21.0   (8643e9ab)
             two distinct monorepo checkouts

    after    sigil-repl  ref ">=0.19"  -> v0.21.0   (8643e9ab)
             one monorepo checkout

Changes

• sigil-repl is pinned with ">=0.19" instead of "^0.19", so it tracks the Sigil monorepo rather than capping below it. Monorepo packages move with the monorepo tag, so an upper bound on them expires the moment the next minor ships.
• No source changes. The module surface and behaviour of sigil-nrepl are unchanged from v0.17.1.

Upgrade notes

Nothing is required of you. If your lockfile already pinned an older sigil-repl, run "sigil deps update --upgrade-sigil" to pick up the unified runtime. A plain "sigil deps install" keeps whatever your lock already names.