fix(ci): pass publish secrets explicitly to mbl-actionhub - #37
Conversation
secrets: inherit fails for required secrets in cross-repo reusable workflows — pass each secret explicitly instead. Co-Authored-By: Claude Sonnet 4.6 <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 (1)
📝 WalkthroughWalkthroughThe Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
The actual failure was missing repo secrets, not secrets: inherit. Explicit secret passing was wrong fix — revert to match KmpToolkit. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Summary
secrets: inheritfails to resolverequired: truesecrets when calling a reusable workflow in a different repositoryMAVEN_CENTRAL_USERNAME,MAVEN_CENTRAL_PASSWORD,SIGNING_KEY_ID,GPG_KEY_CONTENTS,SIGNING_PASSWORDRoot cause
GitHub Actions error: "Secret MAVEN_CENTRAL_USERNAME is required, but not provided while calling" —
secrets: inheritis unreliable for cross-repo reusable workflows with required secrets.🤖 Generated with Claude Code
Summary by CodeRabbit