Repository navigation
docs(site): main-status drift — #1698 model_usage fix, #1701 traverse-mcp packaging - #161
Merged
Merged
Conversation
…se-mcp packaging (#1701)
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
1 participant
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.
Two caveats went stale today when eng PRs merged on traverse
main. Neither is in a published release, so pages keep the 0.15.0 caveats and only update status wording.model_usagewithusage_invalid. Blog Signed models on every host, model_usage Q&A, llms.txt: "fix in review" → "merged on main, not in a release yet". Publishedtraverse-embedder-web@0.15.0still accepts any string; the pass-exactly advice stays.traverse-mcp(Linux x86_64 + macOS arm64,SHA256SUMS, provenance, non-Latesttraverse-mcp-v*) runs on the next product tag. Agents page, agent-MCP-demo Q&A, llms.txt: "longer-term work" → "workflow on main, first release with next tag, none published yet".Historical blog agent-mcp-exact-ref left as written.
Validation:
npm run build✅ (Node 22.12) ·npm test✅ 11 pass