[Release] Candidate - #328
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
7 times, most recently
from
September 3, 2026 18:04
5b1761f to
8fd2bb5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 3, 2026 19:58
8fd2bb5 to
4fc0d2d
Compare
kartojal
approved these changes
Sep 3, 2026
kartojal
left a comment
Contributor
There was a problem hiding this comment.
Approved for SDK release.
Contributor
|
Temporarily closing and reopening to trigger required PR checks that were suppressed on the bot-authored release commit. |
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 main, this PR will be updated.
Releases
@polymarket/bindings@0.9.0
Minor Changes
assetIdinputs when estimating, preparing, creating, and placing market and limit orders, infer Polymarket V2 routing from the structured position-ID namespace, and retaintokenIdas a deprecated input alias.market.state.comboStatus,while passing newly introduced status values through as strings.
marketMakerAddress,ammType,fpmmLive,volumeAmm,volume24hrAmm,volume1wkAmm,volume1moAmm,volume1yrAmm, andliquidityAmmfrom the raw market schema,liquidityAmmfrom the raw event schema,volumeAmmfromMarketMetrics, andliquidityAmmfromEventMetrics. Also remove the internalpagerDutyNotificationEnabledmarket field andrequiresTranslationfrom market, event, series, and tag models, and drop themarketMakerAddressesfilter fromlistMarkets. Responses that still carry any of these fields keep parsing; the values are ignored.Patch Changes
orderingvalue on event and team-list responses.@polymarket/client@0.9.0
Minor Changes
8a26d28: Accept protocol-neutral
assetIdinputs when estimating, preparing, creating, and placing market and limit orders, infer Polymarket V2 routing from the structured position-ID namespace, and retaintokenIdas a deprecated input alias.1fb4dd9: Add
fetchTradingApprovalsStatefor reading a wallet's missing trading approvals without a signer or transaction workflow. Export the approval requirement types, and report malformed approval-check results asUnexpectedResponseErrorin both read and setup workflows.Secure account read methods now reject invalid request values—including
null, arrays, primitives, anduser: null—withUserInputErrorinstead of silently defaulting the wallet or throwing a raw error.4486dee: Expose each market's Combo eligibility status as
market.state.comboStatus,while passing newly introduced status values through as strings.
74ad47b: Expose protocol versions on markets and events.
01438a1: Remove legacy AMM-era fields that the API no longer returns:
marketMakerAddress,ammType,fpmmLive,volumeAmm,volume24hrAmm,volume1wkAmm,volume1moAmm,volume1yrAmm, andliquidityAmmfrom the raw market schema,liquidityAmmfrom the raw event schema,volumeAmmfromMarketMetrics, andliquidityAmmfromEventMetrics. Also remove the internalpagerDutyNotificationEnabledmarket field andrequiresTranslationfrom market, event, series, and tag models, and drop themarketMakerAddressesfilter fromlistMarkets. Responses that still carry any of these fields keep parsing; the values are ignored.1a47d73: Return from
revokeSessionKeyonce the session key is removed from the active-key registry instead of waiting for on-chain confirmation. The method now returnsPromise<void>, andRevokeSessionKeyResulthas been removed.Patch Changes
orderingvalue on event and team-list responses.Note
Medium Risk
Minor version with breaking API surface changes (removed types/fields,
revokeSessionKeyreturn type) plus order routing and wallet/session-key behavior that integrators should re-test before upgrading.Overview
Release candidate that bumps
@polymarket/bindingsand@polymarket/clientto 0.9.0, folds consumed Changesets into each package CHANGELOG, and removes the corresponding.changesetfiles so npm publish can run on merge.The published 0.9.0 notes (already implemented on main) include protocol-neutral
assetIdon order estimate/prepare/create/place flows with PolyV2 routing inferred from position IDs, whiletokenIdstays as a deprecated alias. Market/event models gainprotocolVersionandmarket.state.comboStatus(unknown combo statuses pass through as strings), legacy AMM-era fields andlistMarkets’marketMakerAddressesfilter are dropped from typed surfaces (extra wire fields still parse but are ignored), and teamorderingis preserved on event/team lists.Client-only in this line:
fetchTradingApprovalsStatefor read-only missing-approval checks (withUnexpectedResponseErroron malformed checks), stricter secure account reads that throwUserInputErroron invaliduser/request shapes,revokeSessionKeyresolving once the key leaves the active registry (Promise<void>,RevokeSessionKeyResultremoved), and longer relayer waits (up to five minutes) for session-key authorize/revoke submits.Reviewed by Cursor Bugbot for commit 4fc0d2d. Bugbot is set up for automated code reviews on this repo. Configure here.