Skip to content

v2.24.1

Choose a tag to compare

View all tags
@nokhodian nokhodian released this 05 Oct 13:47
· 66 commits to main since this release
v2.24.1
11ca002

[2.24.1] — 2026-10-05

Fixed

  • docs: corrected MCP tool counts in the antigravity and opencode docs (Fixes #634) (#640).
  • The monofence-ai first-use pin follows the published 2.24.0 package (#638). The 2.24.0 release bumped the workspace monofence-ai to 2.24.0 but left the first-use install pinned at 1.0.7 (lock entry and per-file code hashes included), so main's CI failed the "pin equals workspace version" and fail-closed scanner tests, and the 2.24.0 CLI installs the older monofence from the registry. The pin, lock entry (URL and integrity, verified against the registry tarball) and version now match 2.24.0; the 16 dist/*.js hashes are unchanged because 2.24.0 differs from 1.0.7 only in its version number.
  • monomind deps install run from a checkout now writes the deps cache (#637). When the checkout's own node_modules held the pinned Claude SDK, the command found it, printed "installed and verified" and wrote nothing, so org roles (whose sandbox can only use ~/.monomind/deps) still lacked the SDK and a release's live Claude trials failed with EROFS. The command now always installs into the cache and says where.

Changed

  • The version gate blocks a forced major bump of a sub-package, and the release rules say who takes the release number (#636, #639). scripts/check-package-bumps.mjs now fails when a sub-package's major version rose since the last release tag without a breaking commit (type(scope)!: or a BREAKING CHANGE: footer) touching it; it skips when no release tag is reachable, and MONOMIND_ALLOW_MAJOR_BUMP=1 is the escape hatch. Run against the 2.24.0 release commit it reports all eight mis-bumped packages. The release rules skill now states that only monomind and @monoes/monomindcli take the release number and that a package with a first-use pin moves its pin, lock and hashes in the same commit. The release org's instruction digest changed with the skill, so the operator re-signs release before the next run.

Notes

  • Sub-package versions jumped to 2.24.0 (#636). The 2.24.0 release published @monoes/monobrowse (was 1.0.30), @monoes/monodesign (1.2.25), @monoes/hooks (1.0.13), @monoes/mcp (1.0.7), @monoes/memory (1.0.23), @monoes/monograph (1.6.15), @monoes/routing (1.1.1) and monofence-ai (1.0.7) at 2.24.0 instead of on their own semver lines. None of them has a breaking change in this release: the number is a version bump only, it cannot be unpublished, and their lines continue from 2.24.0. Only monomind and @monoes/monomindcli track the release number.

npm: https://www.npmjs.com/package/monomind/v/2.24.1 and https://www.npmjs.com/package/@monoes/monomindcli/v/2.24.1

Assets 2
Loading