Skip to content

Release v0.4.1

Choose a tag to compare

@github-actions github-actions released this 27 Oct 22:49
· 39 commits to master since this release
2dda4f1

Ashlar 0.4.1

A patch release for the GitHub blockers brick. No public API changes.

Fixed

  • github.blockers 1.2.0 re-reads mergeability that GitHub had not computed yet. When GitHub answers mergeable: null for an open pull request, the brick reads it up to two more times, two seconds apart, before it reports mergeability as unknown. In the 25 October dogfood run, all four "unknown" answers were this case, and they hid three merge conflicts and one branch behind its base. A re-read that fails keeps the first answer. Merged and closed pull requests are not re-read.

Changed

  • The MCP brick host's package README carries an ownership line for the official MCP Registry. Correction: 0.4.1 can't be listed. The registry matches names case-sensitively, and this line spells the GitHub account in lowercase. 0.4.2 fixes it.

Also in this release

  • The "what is blocking this PR?" accuracy study: 44 pull requests, then 100 pull requests across 10 public repositories. See docs/benchmarks/blockers-accuracy.md.
  • The token benchmark's official GitHub MCP server arm, plus Haiku 5.5 and local qwen3:4b runs.
  • github.blockers now dogfoods on Ashlar's own pull requests and release tags.

Upgrading

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

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 40582413546 from the release commit 2dda4f1d, on which every lane group of the readiness gate ran and passed. A 0.4.1-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.1 (linux/amd64 and linux/arm64, index sha256:d7b31de2…) and ghcr.io/ianfrelinger/nexo-api:0.4.1 (linux/amd64).