Repository navigation
chore: version packages - #176
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
October 30, 2026 14:40
4a68056 to
303647a
Compare
This branch was successfully 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
@pincerpay/agent@0.10.3
Patch Changes
#173
c4ecadcThanks @ds1! - Fix MCP and SDK bugs found in the 2026-10 audit:get-settlement-metricscalls the facilitator's unauthenticated/metricsroute (was/v1/metrics, which returned 401).FACILITATOR_ROUTES.metricsis now/metrics.scaffold-x402-middlewaregenerates one handler per paywalled route, with paywall keys and handler paths that match (previously every route pointed at an/examplehandler and 404'd after payment).validate-payment-configreports schema and route errors together, and treats unknown chains, missing wallets and wrong-format addresses as errors.allowedMerchantsandallowedChainsbefore signing.AgentConfig.facilitatorUrlis deprecated (unused).--versionand the MCP server version are read from package.json.Updated dependencies [
c4ecadc]:@pincerpay/cli@0.3.4
Patch Changes
#173
c4ecadcThanks @ds1! - Fix MCP and SDK bugs found in the 2026-10 audit:get-settlement-metricscalls the facilitator's unauthenticated/metricsroute (was/v1/metrics, which returned 401).FACILITATOR_ROUTES.metricsis now/metrics.scaffold-x402-middlewaregenerates one handler per paywalled route, with paywall keys and handler paths that match (previously every route pointed at an/examplehandler and 404'd after payment).validate-payment-configreports schema and route errors together, and treats unknown chains, missing wallets and wrong-format addresses as errors.allowedMerchantsandallowedChainsbefore signing.AgentConfig.facilitatorUrlis deprecated (unused).--versionand the MCP server version are read from package.json.Updated dependencies []:
@pincerpay/core@0.10.3
Patch Changes
#173
c4ecadcThanks @ds1! - Fix MCP and SDK bugs found in the 2026-10 audit:get-settlement-metricscalls the facilitator's unauthenticated/metricsroute (was/v1/metrics, which returned 401).FACILITATOR_ROUTES.metricsis now/metrics.scaffold-x402-middlewaregenerates one handler per paywalled route, with paywall keys and handler paths that match (previously every route pointed at an/examplehandler and 404'd after payment).validate-payment-configreports schema and route errors together, and treats unknown chains, missing wallets and wrong-format addresses as errors.allowedMerchantsandallowedChainsbefore signing.AgentConfig.facilitatorUrlis deprecated (unused).--versionand the MCP server version are read from package.json.@pincerpay/mcp@0.10.3
Patch Changes
#175
0edf820Thanks @ds1! - Correct embedded docs: the merchant middleware is Hono-based (Next.js App Router and any Hono app), the UCP manifest serving snippet uses Hono and Next.js instead of Express, and the gas description matches current facilitator behavior#173
c4ecadcThanks @ds1! - Fix MCP and SDK bugs found in the 2026-10 audit:get-settlement-metricscalls the facilitator's unauthenticated/metricsroute (was/v1/metrics, which returned 401).FACILITATOR_ROUTES.metricsis now/metrics.scaffold-x402-middlewaregenerates one handler per paywalled route, with paywall keys and handler paths that match (previously every route pointed at an/examplehandler and 404'd after payment).validate-payment-configreports schema and route errors together, and treats unknown chains, missing wallets and wrong-format addresses as errors.allowedMerchantsandallowedChainsbefore signing.AgentConfig.facilitatorUrlis deprecated (unused).--versionand the MCP server version are read from package.json.Updated dependencies [
c4ecadc]:@pincerpay/merchant@0.10.3
Patch Changes
c4ecadc]:@pincerpay/onboarding@0.3.4
Patch Changes
c4ecadc]: