Repository navigation
Release 0.30.4: share-session survives deeply nested sessions - #846
anirudhkumar-nanonets wants to merge 16 commits into
Conversation
The official MCP Registry accepts a server only when the npm package it names carries mcpName. pack-trail.mjs now puts mcpName io.github.trailhq/trail-code on @trailhq/trail-code alone, and both packages get MCP keywords for npm search. server.json is the registry entry (from mcp-publisher init, then fixed: description under the 100-character limit, the trailhq/Trail-Code URL, the `mcp` argument so npx starts the server rather than the CLI, and no placeholder API key). .mcp.json at the root is how Cursor Directory and others find the server. The repo's package.json keeps the @nanonets/graft name: the registry reads npm, not the repo, and tests assume this checkout runs as graft.
… keeps the graft name
…d:org token, not the device login
Anirudh's #723, #724, #730, #734, #736, #737 and #740 (share-session still behind TRAIL_SHARE_SESSION=1), #707's WASM depth tier, and the 0.28.1 MCP listing from #742, which never reached main. trail check flags CHANGELOG.md against two learnings on sign-in testing and single claude -p runs. Those are word matches on the changelog's wording; the release only describes code already merged.
# Conflicts: # CHANGELOG.md
Everything merged since 0.29.0: Anirudh's #725-#733, #747-#750 and #828, and the community batch (new languages, Pi host, resolver and Windows fixes). Also carries release/0.29.0 (#761), which never reached main, so main gets the 0.29.0 changelog and the MCP listing too. share-session stays behind TRAIL_SHARE_SESSION=1. trail check flags CHANGELOG.md against two learnings on sandbox PATHs and single claude -p runs. Those are word matches on the changelog's wording; the release only describes code already merged.
A line nested too deep to walk is scrubbed as text, a session the scrub fails on is left out instead of ending the share, and two scrub regexes no longer go quadratic on long words.
🌱 graft blast radiusNothing outside this diff depends on it. 1 area changed; no indexed dependents at depth 2. Test signal per changed area — 1 –Reached = a node under a test path has a resolved edge into the changed symbol. It undercounts anything called indirectly — through a CLI, a spawned process or a dynamic import — so read a low ratio as “look here”, never as a coverage gate.
Open the interactive graph → — click an area to see its dependent symbols at file:line. |
0.30.3 plus #844, as a hotfix:
trail share-sessionno longer stops on a session holding deeply nested JSON. A line that deep is scrubbed as text, and a session the scrub still can't read is left out and named in the summary while the rest go. It's built onrelease/0.30.3(#843), which hasn't merged yet. Main's other changes since then (#757, #739) aren't in it; they go out in the next regular release.Moves: none of the current project's metrics. It unblocks internal devs sharing their sessions (distinct senders in trail-cloud's
shared_sessions), 5 on 17 Nov, one of them stopped by the crash.Checked
@trailhq/trail-code@0.30.4, 3.4 MB, telemetry key stamped (same key and host as 0.30.3),mcpNamekept.trail --versionprints 0.30.4.distscrubs a session line nested 3,000 and 12,000 deep without throwing; 0.30.3 threw at 3,000.🤖 Generated with Claude Code