Release v0.4.2

Ashlar 0.4.2

A patch release so the official MCP Registry can list the MCP brick host. Apart from the version number, only the host's server.json and package README change. There are no code changes and no public API changes.

Fixed

• The MCP brick host's registry name now uses the GitHub account's exact capitals: io.github.IanFrelinger/ashlar. The registry matches names case-sensitively and refused 0.4.1's lowercase name, so 0.4.1 can't be listed. 0.4.2 carries the corrected name in .mcp/server.json and in the package README line the registry checks.
• server.json names NuGet by its v3 index, https://api.nuget.org/v3/index.json, the only address the registry accepts for NuGet packages, and uses the current schema, 2025-12-11. Neither change alters what an MCP client runs.

Upgrading

• MCP host: dnx Ashlar.Mcp.Server.Host@0.4.2 --yes
• PR blockers Action: uses: IanFrelinger/Ashlar/actions/pr-blockers@v0.4.2
• Packages: move your Ashlar.* pins to 0.4.2.
• Operator image: ghcr.io/ianfrelinger/nexo-cli:0.4.2

The source is the same as 0.4.1's, so moving from 0.4.1 is optional.

Defaults

Nothing changes by default. As since 0.3.0, the AirGapped and SecureWorkstation profiles refuse disallowed egress by default. SecureWorkstation's ASHLAR_EGRESS_MODE=report break-glass is unchanged, and AirGapped ignores it.

Release artifacts

• Built and published by release run 40628831317 from the release commit 85ab5261 on release/0.4.2, a branch cut from v0.4.1. Every lane group of the readiness gate ran and passed on that commit. A 0.4.2-rc1 rehearsal ran the same publish and post-push checks against nuget.org first.
• The packages, symbols, nuget-publish-manifest.json and a .sha256.txt per package are attached below.
• Images: ghcr.io/ianfrelinger/nexo-cli:0.4.2 (linux/amd64 and linux/arm64, index sha256:e143323c…) and ghcr.io/ianfrelinger/nexo-api:0.4.2 (linux/amd64).