RELEASE-NOTES-v0.17.0.md

1sigil-mcp now requires the Sigil 0.18 runtime

3This release moves sigil-mcp onto the 0.18 runtime. It carries no new features and

4no behaviour changes: the version jump exists to state a runtime requirement that

50.16.5 already had but did not declare. Sigil 0.18 renamed the stdlib module

6`(sigil env)` to `(sigil dotenv)`, and sigil-mcp imports it for `load-env-file!`.

7Because no 0.17.x runtime provides `(sigil dotenv)`, this code cannot run on one.

9Pin `sigil-mcp` at `^0.17` only if your project runs on Sigil 0.18 or newer. If you

10are still on a 0.17 runtime, stay on the 0.16 line, which v0.16.6 restores to a

11working state.

13## Changes

15- Declares the real runtime floor: the package manifest now says `sigil: "^0.18"`

16 instead of the inaccurate `^0.16` inherited from 0.16.5.

17- No source changes. The `(sigil env)` to `(sigil dotenv)` migration itself landed

18 in 0.16.5; this release only versions it honestly.

20## Upgrade notes

22The failure mode this release prevents is quiet, so it is worth stating plainly.

23Building sigil-mcp 0.16.5 against a 0.17 runtime SUCCEEDS. Dependency resolution

24exits 0, the build exits 0 and prints a bundle summary, and the resulting binary

25then dies at startup:

27 $ sigil build apiary -c release --backend bytecode --force

28 Bundle created: build/release/bin/apiary

29 74 modules, 2.1 MB

30 $ ./build/release/bin/apiary --version

31 Error loading entry module (apiary main): module-import: library not found: (sigil dotenv)

33Nothing in the build output is false. It simply is not about whether the program

34runs. Verify an upgrade by running the binary, not by reading the build log.

36Consumers on Sigil 0.18 or newer should move their pin from `^0.16` to `^0.17`.

37Consumers still on a 0.17 runtime should pin `^0.16` and take v0.16.6.