build(cli): read release app credentials in the version job - #1529
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
Included review availability: 3 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. WalkthroughThe Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized workflow change assigns the version job to the release-version environment so required release credentials are available; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Full details: Title checkExplanation The title follows Conventional Commits with the allowed type and scope. It uses imperative mood, describes the credential change in the version job, stays under 72 characters, and has no trailing punctuation. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Note
PR body AI drafted & edited as needed
Overview of Changes
#1524 moved the deployment approval onto the
publishjob, soversionruns without an environment. So a required key is empty inversionandcreate-github-app-tokenfails with "The 'client-id' (or deprecated 'app-id') input must be set to a non-empty string" error..github/workflows/release.yml: puts theversionjob on arelease-versionenvironment.Testing
Checklist