chore(release): 0.7.1 - #121
Merged
Merged
Conversation
Patch release carrying the agent guidance fix from #119. Documentation and tool-config changes only; no source or schema changes. Note that upgrading does not rewrite an existing .mex/ scaffold — tool configs are copied at setup time — so existing users need to replace the Code Graph section manually. Called out in the changelog.
There was a problem hiding this comment.
Pull request overview
Bumps the mex-agent package version to 0.7.1 and documents the patch release in the changelog, reflecting the previously merged agent-guidance updates from #119.
Changes:
- Bump npm package version to
0.7.1(package.json,package-lock.json). - Add a
0.7.1entry toCHANGELOG.mddescribing the shipped tool-config guidance update and upgrade note.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Updates published package version to 0.7.1. |
| package-lock.json | Aligns lockfile/root package metadata to 0.7.1. |
| CHANGELOG.md | Adds 0.7.1 release notes and guidance for existing scaffolds. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### Changed | ||
| - Agent guidance in the shipped tool configs now describes when to use each graph command, rather than preferring graph commands over text search in all cases. `mex graph query` and `mex graph get` lead when a symbol name is known — they are exact and typically 200-500 output tokens. `mex graph scope` is positioned as a starting point for unfamiliar tasks, with an explicit note that it matches on words rather than meaning, so a task phrased in vocabulary the code does not use will return weak results. | ||
| - Agents are now told to fall back to Grep/Glob when a scope manifest does not contain what they need, and to rephrase a scope task at most once. The previous wording discouraged text search, which could lead an agent to spend additional calls expanding a manifest that was not going to answer the question. | ||
| - Applied to `AGENTS.md`, `CLAUDE.md`, `.cursorrules`, `.windsurfrules`, and `.github/copilot-instructions.md`. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Patch release carrying the agent guidance fix merged in #119. Documentation and tool-config changes only — no source, schema, or CLI behaviour changes.
Contents
package.json/package-lock.json->0.7.1CHANGELOG.mdentrysrc/version.tsreads the version frompackage.jsonat runtime, so there is no second place to bump.Why a release rather than waiting
The guidance in #119 only reaches users through the published package —
templates/ships via thefileswhitelist, andmex setupcopies from it. Until it is published, the fix is only on GitHub.Known limitation, stated in the changelog
Upgrading does not rewrite an existing
.mex/scaffold. Tool configs are copied at setup time (src/setup/index.ts), and there is no refresh command, so existing users keep the old## Code Graphblock. The changelog tells them to replace that section fromtemplates/AGENTS.md.Extending
src/drift/checkers/tool-config-sync.tsto flag a stale Code Graph block against the shipped template would close this automatically and is worth a follow-up — that checker already compares tool configs to each other.Verification
npm run buildclean, including DTS and.wasm/schema asset copynpx vitest run369/369 passing (four consecutive full runs)npm pack --dry-run:mex-agent-0.7.1.tgz, 38 files, 1.1 MB packed / 8.3 MB unpackedtemplates/AGENTS.md,templates/.tool-configs/*,dist/cli.js, anddist/schema.sqlare all in the tarball, and that the shipped templates carry the new guidance textOne intermittent full-suite failure was observed twice earlier in the session and could not be reproduced across four subsequent runs; CI on #119 passed on both Node 22 and 24.
test/cli.test.tsshells out tonpm run buildfrom inside the suite, which is a plausible race against parallel tests readingdist/. Worth a separate look; not treated as a blocker here.Not included
#120 (README results framing, CODEOWNERS, eval fixture) is deliberately held back for a later release.