Repository navigation
build(deps): bump @polymarket/clob-client-v2 from 1.0.8 to 1.2.0 - #479
Conversation
Bumps [@polymarket/clob-client-v2](https://github.com/Polymarket/clob-client-v2) from 1.0.8 to 1.2.0. - [Release notes](https://github.com/Polymarket/clob-client-v2/releases) - [Commits](Polymarket/clob-client-v2@v1.0.8...v1.2.0) --- updated-dependencies: - dependency-name: "@polymarket/clob-client-v2" dependency-version: 1.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
VickyXAI
left a comment
There was a problem hiding this comment.
I compared the published 1.0.8 and 1.2.0 packages. For orders placed by tokenID, which is all we send, they build and sign the same order. The rest is additive: positionID/v3 routing, sharing of duplicate in-flight requests, and stricter input checks. Note that the package is deprecated at every version in favour of the unified Polymarket SDK, so migrating off it is a separate follow-up.
Bumps @polymarket/clob-client-v2 from 1.0.8 to 1.2.0.
Release notes
Sourced from @polymarket/clob-client-v2's releases.
... (truncated)
Commits
e7c3e4achore: release v1.2.08046a89fix: validate order identifiers and cover public position flows (#110)28a303efeat(client): support PolyV2 position orders (#104)801696efeat: prime order metadata caches through the public getters (#107)1210b46Revert automatic V3 routing (#105) (#108)9cfb25ffeat: route Protocol V2 markets to V3 exchange automatically (#105)49083a6chore: restore package version on main39d8c12chore: release v1.2.0-canary.0f3e1a05chore: release v1.1.05b28ba0refactor: resolve transaction hashes internally for matched orders (#89)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)