Skip to content

chore: release v1.1.1-canary.0 - #109

Closed
kartojal wants to merge 2 commits into
mainfrom
release/v1.1.1-canary.0
Closed

kartojal wants to merge 2 commits into
mainfrom
release/v1.1.1-canary.0

Conversation

@kartojal

@kartojal kartojal commented Sep 23, 2026 •

Copy link
Copy Markdown
Collaborator

Prepare @polymarket/clob-client-v2@1.1.1-canary.0 from main by bumping the package version. The GitHub prerelease will publish through the existing workflow to npm's canary tag; latest stays at 1.1.0.

The release includes #107: order metadata cache warm-up, shared in-flight metadata requests, and a single retry when order placement is rejected for an order-version mismatch. Automatic V3 routing was reverted on main and is not included.

Validation: frozen-lockfile installation, lint, build, all 307 tests, package dry run, and CommonJS/ESM import smoke checks passed. The version-bump commit is GitHub-signed and verified.


Note

Low Risk
Single package version bump with no runtime or API code changes in the diff.

Overview
Bumps @polymarket/clob-client-v2 from 1.1.0 to 1.1.1-canary.0 in package.json so the existing release workflow can publish a npm canary prerelease while latest remains on 1.1.0.

No source, build, or dependency changes in this diff—only the version string.

Reviewed by Cursor Bugbot for commit 98a661e. Bugbot is set up for automated code reviews on this repo. Configure here.

@kartojal
kartojal requested a review from a team as a code owner September 23, 2026 12:20

This branch was successfully deployed

1 active deployment
npm — 98a661ef Deployed Sep 23, 2026 by kartojal via publish #30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant