Postmaster v9.3.0 native file resource handoff - #8
Merged
Conversation
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.
Summary
get_stored_file_resource(file_id, transport)returning a real MCPResourceLinkpostmaster://files/{file_id}for MCPresources/readGET/HEAD /files/{file_id}streaming with HMAC expiry and byte rangesfile_idcanonical and stream the existing SHA-256 FileStore blob without transcode/recompression/temp copiesdocs/FILE_HANDOFF.mdDeployment
postmaster-mcp.ymlremains unchanged. The HTTP handoff reuses existingPUBLIC_MCP_HOST; optional process-level overrides areFILE_STORE_PUBLIC_BASE_URL,FILE_STORE_DOWNLOAD_SECRET, andFILE_STORE_DOWNLOAD_URL_TTL_SECONDS. If no public base is configured,transport=autofalls back to the MCP resource URI. The download secret is generated persistently under/datawhen not supplied.An existing
POSTMASTER_VERSION=latestdeployment can receive v9.3 by restarting after the stable release is published.