Repository navigation
FsLangMCP 0.20.0
This release ships the changes for the recent v0.16.0 reports #320–324, rechecked against v0.19.0 before implementation. It remains a pre-1.0 release, not the 1.0 contract freeze.
Changes for the recent issues
- #320: Standalone script checks.
checkaccepts.fsxpaths andscope="script", resolves SDK/FSI references, NuGet#rand relative#loadclosure, and does not execute the script body. - #321: Bounded, optionally grouped diagnostics. Keep complete verdict/count evidence while returning occurrence counts and bounded additional locations.
maxDiagnosticscontrols the row cap; individual diagnostics remain the default. Oversized diagnostic payloads expose truncation explicitly. - #322: Precise constructor mismatch context. Diagnostics can include the compiler-resolved fully qualified type and constructor range when syntax and semantic evidence identify it precisely. Ambiguous cases are not guessed.
- #323: Correct public value signatures.
fcs_public_apirenders module values askind="value"andname: type, including mutable, function-valued and partially applied bindings. Actual functions keep callable signatures. - #324: Existing behavior verified. The severity-floor behavior already worked in 0.19.0. A real FS3520 regression now checks
infoCount,belowSeverityFloorCount,diagnosticsNoteand recovery withseverity="all"; no extra severity fields were needed.
Maintenance
The release also includes the already-merged behavioral-test hardening and legacy type-at-position/Python smoke fixes (#326), clearer running-versus-installed version fields in issue templates (#325), deadline/pagination harness fixes (#316), and reviewed runtime dependency, test-tooling and documentation updates since 0.19.0.
Draft PR #328 is not included in this release.
Upgrade
dotnet tool update --global FsLangMcp --version 0.20.0
fslangmcp --bootstrap-toolsRestart existing MCP server processes after updating so clients use the new binary. Bootstrap installs the external-tool versions pinned by this release. Script checks resolve references but do not evaluate script bodies. Constructor context is intentionally conservative; the diagnostic response budget measures serialized payload characters, not model tokens or the outer MCP envelope.
Full changelog · Changes since 0.19.0
Release validation follow-up
Fixed a test-only deadline-injection ordering race exposed during release CI. The forced response expiry now belongs to its intended request; production timeout and strict retry behavior are unchanged.