ci: fix publish job trigger for multi-crate workspace#14
Conversation
release-please v4 with cargo-workspace plugin uses package-specific output keys (crates/cachekit--release_created), not the bare release_created. The publish job was skipped on v0.2.0 release because the condition never evaluated to true. Also adds debug step to log all release-please outputs for future diagnosis.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 32 minutes and 1 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ 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 |
Summary
The v0.2.0 publish job was skipped because the workflow checked
release_created(bare), but release-please v4 withcargo-workspaceplugin outputs package-specific keys likecrates/cachekit--release_created.steps.release.outputs['crates/cachekit--release_created']insteadContext
v0.2.0 GitHub releases were created successfully but
cargo publishnever ran. This was a one-time manual publish for v0.2.0; this fix prevents recurrence on all future releases.