Release workflow: explicitly dispatch PyPI publish

[guysmoilov]

Summary

• The release workflow's gh release create step ran with the default GITHUB_TOKEN. GitHub Actions does not propagate the release: published event to other workflows when the triggering action used the default token, so python-publish.yml never actually fired.
• Confirmed by running the release workflow for 0.7.1: the GitHub release was created correctly, but the package never reached PyPI until manually dispatched.
• Fix: after creating the release, explicitly gh workflow run python-publish.yml --ref <bump-commit-sha> (skipped when draft: true, matching the existing "don't publish drafts" behavior).

Test plan

• Run the release workflow with draft: true and confirm the publish workflow is not triggered.
• Run the release workflow with draft: false on a test version and confirm python-publish.yml fires automatically and the version lands on PyPI.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 17 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c29f0f77-5f78-49db-981b-6bda115bb3bc

📥 Commits

Reviewing files that changed from the base of the PR and between b90b227 and c4607a4.

📒 Files selected for processing (1)

• .github/workflows/release.yml

📝 Walkthrough

Walkthrough

The release workflow now grants actions: write permission and explicitly dispatches python-publish.yml for the release commit, except when creating a draft release.

Changes

Release publishing trigger

Layer / File(s)	Summary
Dispatch Python publishing after release .github/workflows/release.yml	The workflow adds actions: write permission and conditionally triggers python-publish.yml with the release target commit SHA for non-draft releases.

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

Possibly related PRs

• DagsHub/client#706: Adds the release workflow that this change extends with publishing dispatch logic.

Poem

A bunny watched the release hop,
Then nudged the publish workflow’s stop.
Drafts stay quiet, tags run bright,
Permissions make the actions right.
“Ship the package!” cheered the hare.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: explicitly dispatching the PyPI publish workflow from the release workflow.
Description check	✅ Passed	The description matches the changeset and explains the release workflow fix, rationale, and test plan.
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-release-publish-trigger

---

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

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2d97d62e-eee8-4d06-977f-f2d2c3135fae

📥 Commits

Reviewing files that changed from the base of the PR and between 64c97d9 and b90b227.

📒 Files selected for processing (1)

• .github/workflows/release.yml

📜 Review details

⏰ Context from checks skipped due to timeout. (5)

• GitHub Check: build (3.9)
• GitHub Check: build (3.10)
• GitHub Check: build (3.11)
• GitHub Check: build (3.13)
• GitHub Check: build (3.12)

🔇 Additional comments (1)

.github/workflows/release.yml (1)

31-31: LGTM!