Repository navigation
chore(release): version packages - #3743
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
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
force-pushed
the
changeset-release/master
branch
17 times, most recently
from
November 11, 2026 13:32
f7885b5 to
0cb7df5
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
November 11, 2026 13:33
0cb7df5 to
57192a9
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 the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@upstash/context7-mcp@4.7.0
Minor Changes
pageargument to theget-upgrade-guideresearch preview tool: a long guide now comes in pages, each in full detail. Page 1 starts with everything needed to migrate (summary, before you start, codemods, breaking changes, deprecations), which continues on the next pages when it is longer than one page; behavior, config and API changes follow. A guide is served only once it is complete, so its pages always fit together; until then the tool says it is being prepared and when to call again, or that it could not be prepared.Patch Changes
get-upgrade-guideno longer tells the agent never to retry a guide that could not be prepared: the agent usesquery-docsnow and calls again only after the time the answer gives. Telemetry records an unavailable guide asunavailableand a page past the last asinvalid, instead ofnot_found; neither is shown to the agent as an error.@upstash/context7-sdk@0.7.0
Minor Changes
searchLibraryreturns an empty list (or, withtype: "txt", a "No libraries found" message) when nothing matches, instead of throwing a 404Context7Error. Text results label the trust score as "Source Reputation", the same as the MCP server.ctx7@0.11.1
Patch Changes
/reactjs/react.devin CLI help examples./facebook/reactnow redirects to another library and returns no documentation.@upstash/context7-tools-ai-sdk@1.0.4
Patch Changes
resolveLibraryIdreturns the SDK's "No libraries found" message when nothing matches, andqueryDocsreturns its "No documentation found" message for an unknown library ID. Other errors no longer end with ".. Check your API key and try again."