Skip to content

Commit 9f3197e

Browse files
cliffhallclaude
andcommitted
chore(filesystem): fold the modelcontextprotocol#5101 changeset into the 1.0.0 CHANGELOG
As for modelcontextprotocol#5094 and modelcontextprotocol#5097 on this branch: 1.0.0 is unpublished and its changesets are already folded. No version change. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: cliffhall <[email protected]>
1 parent 3f6aaf4 commit 9f3197e

2 files changed

Lines changed: 2 additions & 5 deletions

File tree

‎.changeset/filesystem-roots-refresh-barrier.md‎

Lines changed: 0 additions & 5 deletions
This file was deleted.

‎src/filesystem/CHANGELOG.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,5 @@ The first semantic version, resuming semver after the date-stamped releases (las
2525
- [#5094](https://github.com/modelcontextprotocol/servers/issues/5094) [`bea1c9a`](https://github.com/modelcontextprotocol/servers/commit/bea1c9a1bd623aea093a4408b0f71e95cd0e1d03) [@cliffhall](https://github.com/cliffhall) - A `roots/list_changed` update that leaves no valid root now revokes access once the client's roots are in force, instead of keeping the previous allowed directories, so a client that withdraws its roots withdraws the server's access too (#5094). Every path is then refused with "Access denied - no allowed directories" until the client exposes a root again. Before any root has been in force, such an update still keeps the command-line directories.
2626

2727
- [#5097](https://github.com/modelcontextprotocol/servers/issues/5097) [`a13e809`](https://github.com/modelcontextprotocol/servers/commit/a13e809d95d6771159483a69e707d0466a9fe1b1) [@cliffhall](https://github.com/cliffhall) - Overlapping roots refreshes now take effect in the order they started: when a client sends `roots/list_changed` again before the previous `roots/list` answer arrived (or while the initial roots are still loading), an answer that arrives after a newer refresh has started is discarded instead of overwriting it, so a stale answer can no longer undo a newer update such as a revocation (#5097).
28+
29+
- [#5101](https://github.com/modelcontextprotocol/servers/issues/5101) [`3f6aaf4`](https://github.com/modelcontextprotocol/servers/commit/3f6aaf4ff6b3d48243f8a94f1ea8dafb574de5ad) [@cliffhall](https://github.com/cliffhall) - Tool calls that arrive while a `roots/list_changed` refresh is fetching the client's roots now wait for it, as they already did for the initial roots, so a call can no longer reach a root the client has just withdrawn while the answer is pending (#5101).

0 commit comments

Comments
 (0)