[DanielButler1]

Summary

• determine Python SDK publication independently from Changesets' npm output
• query PyPI for the exact local package version before building
• keep trusted publishing idempotent with the existing skip-existing safeguard

Why

The npm packages published successfully, but the first PyPI OIDC attempt failed before the trusted publisher was configured. On retry, Changesets found no unpublished npm packages and returned published=false, which skipped the still-pending Python release. This change makes recovery retries publish Python whenever its local version is absent from PyPI.

Validation

• git diff --check
• parsed .github/workflows/ci.yml with PyYAML
• ran the release-status logic against PyPI; phaseo@2.0.6 correctly reports should_publish=true

Created with Codex

Summary by CodeRabbit

• Bug Fixes
  • Improved Python SDK release publishing by checking PyPI for an existing version before building and publishing.
  • Prevented unnecessary release attempts when the SDK version is already available on PyPI.
  • Preserved safe handling for already-published packages during the release process.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[coderabbitai]

Warning

Review limit reached

@DanielButler1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 09ae41c2-04cb-4a44-a257-0b6983aabb32

📥 Commits

Reviewing files that changed from the base of the PR and between 9aa7dde and f0f2587.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

📝 Walkthrough

Walkthrough

The publish workflow now checks whether the Python SDK version exists on PyPI before building and publishing. It conditionally executes those steps when the version is absent, while GitHub changelog release creation retains its existing changeset-based condition.

Changes

Python SDK PyPI publishing

Layer / File(s)	Summary
PyPI existence gate .github/workflows/ci.yml	The publish job sets up Python, checks the package version against PyPI, writes should_publish, and gates SDK build and trusted publishing steps on that output. GitHub release creation remains controlled by the changesets publish result.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: making PyPI release publishing retry-friendly.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/pypi-independent-publish-20260726

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9aa7dde380

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/ci.yml:
- Around line 874-909: The Python SDK publish gate currently derives
should_publish solely from PyPI and can run before npm publication completes.
Update the release workflow around the “Check Python SDK release status” step
and its downstream Python publish condition to require an explicit successful
npm-publication signal from changesets/action, or skip Python publishing while
changesets/action is in PR-create/publish mode; preserve the existing PyPI
version check once npm readiness is confirmed.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: e5d823f4-58b8-45cc-bf81-a5d98f642a8c

📥 Commits

Reviewing files that changed from the base of the PR and between d4b62d0 and 9aa7dde.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

[github-actions]

Web preview

Open the latest preview

Commit: 83be222