Skip to content

Release 0.30.3: share-session's cleaner preview - #843

Open
anirudhkumar-nanonets wants to merge 14 commits into
mainfrom
release/0.30.3
Open

anirudhkumar-nanonets wants to merge 14 commits into
mainfrom
release/0.30.3

Conversation

@anirudhkumar-nanonets

Copy link
Copy Markdown
Collaborator

0.30.2 plus #840: trail share-session's preview is four short sections (what's sent, from which folders, what's removed before sending, what happens after you say yes) and one question, → Send it? [y/N]. It's built on release/0.30.2 (#839), which hasn't merged yet, so merging this one covers #839 and the release PRs under it too.

Moves: none of the current project's metrics. Like #840, it should raise how many share-session previews end in a send (share_bundle with outcome sent).

Checked

Published as @trailhq/trail-code only; @nanonets/graft stays at 0.30.1.

🤖 Generated with Claude Code

Shrish Dwivedi and others added 14 commits October 30, 2026 22:42
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.
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.
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.
0.30.0 plus Anirudh's #836: share-session needs no flag and signs in by itself. Built on release/0.30.0 (#835), which hasn't reached main yet.
@trailhq-graft

trailhq-graft Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

🌱 graft blast radius

Nothing 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.

  • – Trail Packing — no function, method or class changed here

⚠️ 8 changed files not in the graph (.mcp.json, .trail/learnings/2026-10-29-the-mcp-registry-listing-reads-the-shrish.md, .trail/learnings/2026-10-30-the-mcp-registry-listing-reads-the-shrish.md, .trail/learnings/2026-11-16-packing-the-graft-package-rebuilds-it-anirudhkumar.md, CHANGELOG.md) — no parser claims the extension, or the index predates the file.

graft blast · origin/main...HEAD · depth 2 · 9 changed files

Open the interactive graph → — click an area to see its dependent symbols at file:line.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant