fix(release): switch to workflow_run trigger, disable PyPI publishing#58
Conversation
- Trigger changed from push:branches to workflow_run:workflows:["CI"] so releases only fire after CI passes (not on every push to main) - Added job-level if guard for workflow_run conclusion == success - publish-to-pypi set to false (no repos currently publish to PyPI) - run-tests set to false with skip-tests-reason (CI already ran them) - Concurrency group updated to use workflow_run.head_branch Applies PSR v10.5.3 mitigations from ByronWilliamsCPA/.claude reference implementation (validated end-to-end on 2026-05-28 with v0.14.0 release). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 59 minutes and 54 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
❌ This pull request cannot be evaluated by MergifyDetailsfiles are inaccessible |
|
❌ This pull request cannot be evaluated by MergifyDetailsfiles are inaccessible |
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s release workflow to only run after the CI workflow completes successfully (via workflow_run), and adjusts release inputs to reflect that CI already validated tests and that PyPI publishing is disabled for this repo.
Changes:
- Switch release trigger from
pushtoworkflow_runon theCIworkflow, and gate the job on upstream success. - Update the release concurrency group to use the upstream run’s
head_branch(with fallback). - Disable running tests inside the release reusable workflow and provide a skip reason; keep PyPI publishing disabled.
| # Prevent concurrent releases | ||
| concurrency: | ||
| group: "release-${{ github.ref }}" | ||
| group: "release-${{ github.event.workflow_run.head_branch || github.ref_name }}" |
| if: >- | ||
| github.event_name == 'workflow_dispatch' || | ||
| github.event.workflow_run.conclusion == 'success' | ||
| uses: ByronWilliamsCPA/.github/.github/workflows/python-release.yml@961eb17d8e9b7fe0d8bfc5dbe9d23c824484fb11 # main |
| publish-to-pypi: false # re-enable when PyPI project is registered | ||
| pypi-package-name: 'rag-processor' | ||
| run-tests: true | ||
| run-tests: false | ||
| skip-tests-reason: 'Tests run in upstream CI pipeline before this workflow fires' | ||
| no-build: false |
Summary
push: branchestoworkflow_run: ["CI"]so releases are gated behind CI successhead_branchforworkflow_runeventscontents: readpublish-to-pypi: false(private repo — no PyPI publishing)run-tests: false+skip-tests-reason(CI already validated tests upstream)secrets: inheritfor reusable workflow token passthroughContext
Part of fleet-wide replication of PSR v10.5.3 bug mitigations. The core fixes (vcs_release, commit:false, HEAD attachment) live in the org-level reusable workflow (ByronWilliamsCPA/.github PR #184). This PR updates the caller to use the CI-gated trigger pattern.
Test plan
workflow_runGenerated with Claude Code