Skip to content

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

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--polymarket-client
Open

chore(main): release polymarket-client 0.1.0-b4#65
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--polymarket-client

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Jun 2, 2026

🤖 I have created a release beep boop

0.1.0-b4 (2026-06-04)

Bug Fixes

  • gamma: drop tag/series request params not honored upstream (0e6c8f0)
  • gamma: drop tag/series response fields not populated upstream (24ff6f9)

Documentation


This PR was generated with Release Please. See documentation.


Note

Low Risk
Only version, manifest, and changelog metadata change; no runtime code in this diff.

Overview
This PR is a Release Please cut for polymarket-client 0.1.0-b4. It bumps the package version in pyproject.toml and .release-please-manifest.json from 0.1.0-b3 to 0.1.0-b4, and adds a CHANGELOG section for that release.

The new changelog entry documents fixes already merged on main—gamma API alignment (dropping tag/series request params and response fields the upstream service does not honor or populate) and docs fixes for get_market examples. Those behavioral changes are not in this diff; this PR only publishes the version and release notes.

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

Comment thread pyproject.toml
[project]
name = "polymarket-client"
version = "0.1.0b3"
version = "0.1.0-b4"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit cac293d. Configure here.

@github-actions github-actions Bot force-pushed the release-please--branches--main--components--polymarket-client branch from cac293d to bb47927 Compare June 4, 2026 07:09
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--polymarket-client branch from bb47927 to 2778c6b Compare June 4, 2026 12:04
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

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

Fix All in Cursor

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

Reviewed by Cursor Bugbot for commit 2778c6b. Configure here.

Comment thread pyproject.toml
[project]
name = "polymarket-client"
version = "0.1.0b3"
version = "0.1.0-b4"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 2778c6b. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants