chore(main): release polymarket-client 0.1.0-b4

[github-actions]

🤖 I have created a release beep boop

0.1.0-b4 (2026-06-05)

Features

• client: default secure clients to deposit wallet (98ad0e9)
• client: default secure clients to deposit wallet (872c5de)

Bug Fixes

• gamma: accept event market URLs (afcdca5)
• gamma: accept event market URLs (c1e9893)
• gamma: default list_events to open events (4f66139)
• gamma: default list_events to open events (9d92d4f)
• gamma: drop tag/series request params not honored upstream (0e6c8f0)
• gamma: drop tag/series response fields not populated upstream (24ff6f9)
• orders: map unknown builder code to user input error (67a00fb)
• orders: map unknown builder code to user input error (6cace4f)

Documentation

• fix get_market examples (86c6606)
• fix get_market examples (4c893c9)

---

This PR was generated with Release Please. See documentation.

---

Note

Low Risk
Only version manifest, package version, and changelog updates; runtime behavior ships via prior merges, not this diff.

Overview
Release-please PR that bumps polymarket-client from 0.1.0-b3 to 0.1.0-b4 in pyproject.toml and .release-please-manifest.json, and adds the 0.1.0-b4 section to CHANGELOG.md.

No library source changes are in this diff; merging cuts the 0.1.0-b4 release whose notes cover already-merged work: secure clients defaulting to the deposit wallet, Gamma API alignment (event market URLs, open-by-default list_events, dropped unsupported tag/series params and fields), order error mapping for unknown builder codes, and doc fixes for get_market examples.

^{Reviewed by Cursor Bugbot for commit df6f84b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Invalid PEP 440 version string breaks Python packaging

High Severity

The version changed from the valid PEP 440 format "0.1.0b3" (no hyphen) to "0.1.0-b4" (with hyphen). The hyphenated form is not PEP 440 compliant — pre-release segments must be directly appended (e.g., 0.1.0b4). This will cause hatchling builds and pip install to reject or misinterpret the version, effectively breaking package distribution.

 

^{Reviewed by Cursor Bugbot for commit cac293d. Configure here.}

[cursor]

Dev fallback version stale

Medium Severity

pyproject.toml was bumped to the new beta, but the PackageNotFoundError fallback in version.py still reports 0.1.0b3. Editable or non-installed runs expose the wrong __version__ via polymarket.__version__ until metadata is present.

 

^{Reviewed by Cursor Bugbot for commit 2778c6b. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 3 total unresolved issues (including 2 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 73d9428. Configure here.}

[cursor]

Lockfile stale after version bump

Medium Severity

The version in pyproject.toml is bumped to 0.1.0-b4, but uv.lock still records polymarket-client as 0.1.0b3. With uv sync --locked in Verify/Integration workflows, that metadata mismatch typically fails dependency install and blocks CI on this branch.

 

^{Reviewed by Cursor Bugbot for commit 73d9428. Configure here.}