Update dependency @mcp-b/webmcp-polyfill to v3#8673
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
6bc401a to
dd6cd2c
Compare
dd6cd2c to
4b701e5
Compare
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 contains the following updates:
2.3.2→3.0.0Release Notes
WebMCP-org/npm-packages (@mcp-b/webmcp-polyfill)
v3.0.0Major Changes
4f3cc5e: Track the May 27, 2026 WebMCP draft that moves themodelContextgetter fromNavigatortoDocument.@mcp-b/webmcp-polyfillnow installsdocument.modelContextas the canonical surface.navigator.modelContextis kept as a deprecated, backward-compatible alias that returns the sameModelContextinstance and emits a one-time runtime deprecation warning on first access. Tools registered on either surface are observable on the other. Native detection now checks both surfaces so the polyfill no-ops when the browser exposes WebMCP on either.@mcp-b/webmcp-typesadds theDocument.modelContextglobal augmentation and marksNavigator.modelContextas@deprecated. Chrome 150 deprecatednavigator.modelContextand will remove it in a future release; the deprecated alias remains available in this release as a migration fallback.provideContext()andclearContext()APIs remain absent from the strict WebMCP types and polyfill runtime. Consumers still calling those legacy APIs should migrate to explicitregisterTool()andunregisterTool()calls.Migration:
Tracks webmachinelearning/webmcp#173 and webmachinelearning/webmcp#184.
Patch Changes
4f3cc5e]Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.