Repository navigation
chore: version packages - #5633
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/v2/main
branch
11 times, most recently
from
November 18, 2026 23:25
d820a46 to
c213238
Compare
github-actions
Bot
force-pushed
the
changeset-release/v2/main
branch
from
November 18, 2026 23:36
c213238 to
bac4374
Compare
This branch has not been deployed
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to v2/main, this PR will be updated.
Releases
@modelcontextprotocol/server-everything@2.4.0
Minor Changes
a1137b8@cliffhall - The Streamable HTTP transport now evicts a 2025-era session that has been idle for 30 minutes: one with no request in flight and no stream open. Until now a session whose client never sent a DELETE stayed in memory, with its server instance, for the life of the process. An evicted session's next request is answered404 Session not found, the spec's signal for the client to initialize again. Set the newSESSION_IDLE_TIMEOUT_MILLISenvironment variable to change the timeout, or to0to keep sessions until their client ends them. 2026-07-28 clients have no sessions and are unaffected. Thanks to Pierpaolo1223 for the report and the measurements in #5558.@modelcontextprotocol/server-filesystem@2.4.1
Patch Changes
#5618
37a1f2f@cliffhall -move_filenow refuses to move a directory into itself withCannot move a directory into itself: <destination> is inside <source>, instead of reportingParent directory does not existfor a destination directory that does exist.#5622
062b32a@cliffhall - On Windows,list_directory,list_directory_with_sizes,directory_treeandsearch_filesnow check the directory they list before and after reading it: its path must have no junction or symlink on it and must name the same directory both times, or the call is refused with "Access denied - a directory on the path changed during the operation". A directory swapped for a junction after the path was validated is no longer listed. A swap made and undone while the directory is being read is still not detected; the README's "Limit on Windows" entry says what holds. macOS and Linux are unchanged.#5620
731abb0@cliffhall -search_filesno longer answers a search that matched nothing with a bareNo matches found. The result still begins with those words, and now names the pattern and the directory searched, says the pattern is a case-sensitive glob over names relative to that directory (never file contents), and, for a pattern with no**, suggests the**/form that reaches subdirectories.@modelcontextprotocol/server-memory@2.2.2
Patch Changes
0f3ff98@cliffhall - Close three narrow gaps in how the memory file lock changes hands between server processes: a writer could start while a live lock was momentarily moved aside by a server checking a stale one, a lock could be put back after its holder had finished (delaying later writes by up to 30 seconds), and a server releasing a lock it had held past the stale timeout could remove the lock of the server that took over. The momentary<memory file>.lock.breakfile now orders every release and stale-lock break, and a server that has just created the lock waits for it to go before writing. Servers on this version and on 2.2.1 or earlier can still share a memory file; the older server's own releases and acquisitions keep those gaps.