ci: decouple publish from release-please workflow_call#644
ci: decouple publish from release-please workflow_call#644
Conversation
The publish workflow now triggers only on tag push, removing the workflow_call path. This fixes the PyPI trusted publishing failure where the OIDC token claims didn't match because the workflow was called from release.yaml rather than triggered directly by the tag. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe pull request refactors GitHub Actions workflows to eliminate a redundant job intermediary. The Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
workflow_calltrigger frompublish.yaml— it now triggers only on tag pushpublishjob fromrelease.yaml— release-please creates the tag, which triggers publish independentlyworkflow_refclaims didn't match because publish was called viaworkflow_callfromrelease.yamlHow it works now
update-citation-dateanddeploy-docsTest plan
publish.yaml🤖 Generated with Claude Code
Summary by CodeRabbit