Repository navigation
Release 0.30.5: share-session says what to type, folder numbers included - #848
anirudhkumar-nanonets wants to merge 18 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.
The send question was only '→ Send it? [y/N]', so a teammate didn't know folders could be left out. One line now says what each answer does, then a bare → prompt; folders can be left out more than once.
🌱 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 the code that changed, and the line that reaches it. |
0.30.4 plus #847: after the preview,
trail share-sessionsays what to type (ysends it all,nsends nothing, folder numbers leave those folders out), and folders can be left out more than once. It's built onrelease/0.30.4(#846), which hasn't merged yet, so merging this one covers #846 too. Main's other changes (#757, #739) still wait for the next regular release.Moves: none of the current project's metrics. It should raise how many share-session previews end in a send (
share_bundleoutcomesentorpartial), since a teammate holding back one folder no longer has to decline the whole share.Checked
@trailhq/trail-code@0.30.5, telemetry key stamped (same key and host as 0.30.4),mcpNamekept.trail --versionprints 0.30.5. The packeddisthas both share-session survives deeply nested sessions #844's deep-line scrub and share-session says what to type, folder numbers included #847's question line.2left that folder out, andysent the rest.🤖 Generated with Claude Code