Conversation
…anges GitHub's REST API does not support changing package visibility. This must be done manually via the GitHub web UI. Added comment with instructions for manual visibility change.
|
Warning Rate limit exceeded
⌛ 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. 📒 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
set-publicjob from deploy workflow - GitHub's REST API does not support changing package visibilitydeployjob to not depend on removedset-publicjobBackground
The
set-publicjob was failing with 404 errors because GitHub's REST API does not provide an endpoint to change container package visibility. This is a known limitation - visibility changes must be done through the GitHub web UI.Manual step required
After first release, set package visibility to public via:
https://github.com/orgs/vultisig/packages → Package Settings → Change visibility to Public