Repository navigation
Prepare version 1.4.0 - #154
Merged
Merged
Conversation
qirh
force-pushed
the
prepare-compatibility-release
branch
from
October 17, 2026 01:15
64050f8 to
918f461
Compare
qirh
marked this pull request as ready for review
October 17, 2026 01:28
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
1 participant
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.
Prepare version 1.4.0 with the merged nullable Search date support and Agent search token-budget controls. Keep package, registry, plugin and reported server versions aligned.
Built and installed the packed package in a separate consumer project. Its executable completes an MCP stdio handshake and exposes all four tools. The installed server accepts Agent search budgets of 120,000 total and 20,000 per page, rejects larger values before an API call, serializes the search tool and versioned headers correctly, and handles nullable Search dates. API responses were mocked for this package smoke test.
Merging this PR triggers the existing npm and MCP registry publishing workflows. These workflows run independently, so verify npm availability and the registry publication separately.