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

[github-actions]

🤖 I have created a release beep boop

0.1.0-b8 (2026-06-15)

Features

• models: add parent_event_id to Event (4b87156)
• models: add parent_event_id to Event (c966aec)

Bug Fixes

• data: parse combo trade activity (24d3cf2)
• data: parse combo trade activity (dc9150a)
• gamma: omit legacy non-binary market listings (f649c6c)
• gamma: omit legacy non-binary market listings (abbce8c)
• models: expose missing activity market icons as None (0adfad7)
• models: expose missing activity market icons as None (b36b41f)
• models: normalize empty-string trade and position icons to None (233cb2d)
• models: normalize empty-string trade and position icons to None (5949925)
• rfq: support balance error codes (59e366d)
• rfq: support balance error codes (0a0387e)

---

This PR was generated with Release Please. See documentation.

---

Note

Low Risk
Release metadata only; no application code changes in this diff.

Overview
This is a Release Please cut that publishes polymarket-client 0.1.0-b8. The diff only bumps the package version in pyproject.toml, updates .release-please-manifest.json, and adds the 0.1.0-b8 section to CHANGELOG.md.

That changelog entry documents SDK changes already landed on main since 0.1.0-b7: parent_event_id on Event, combo trade activity parsing, filtering legacy non-binary gamma listings, icon fields normalized to None when missing or empty, and RFQ balance error code handling.

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

[cursor]

Invalid PEP 440 project version

Medium Severity

The release bumps version from 0.1.0b7 to 0.1.0-b8. PEP 440 beta tags attach directly to the release segment (0.1.0b8), not with a hyphen. That mismatch with project release guidance can break uv build/PyPI metadata and confuse installs pinned as polymarket-client==0.1.0b8.

 

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

[cursor]

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

There are 2 total unresolved issues (including 1 from previous review).

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

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

[cursor]

Lockfile stale after version bump

High Severity

The release commit bumps version in pyproject.toml to 0.1.0-b8 but does not update uv.lock, which still records the workspace package as 0.1.0b7. Verify and Integration run uv sync --locked, which errors when project metadata and the lockfile disagree, so CI on this commit likely fails before tests or builds run.

 

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