ci: add release-please-develop pre-release workflow - #734
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new GitHub Actions workflow to support a pre-release lane from the develop branch, delegating the actual release logic to the shared openfga/.github reusable workflow (pinned by SHA) to keep implementation consistent across SDK repos.
Changes:
- Introduces
.github/workflows/release-please-develop.ymlto generate/publish pre-releases fromdevelop. - Supports both
workflow_dispatch(explicit pre-release version input) andpushtodevelopgated onrelease:-prefixed merge commits. - Configures job-level permissions and passes expected inputs (
base-branch,staging-branch,trigger-event) to the reusable workflow.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
WalkthroughAdds a GitHub Actions workflow that runs prerelease automation for ChangesDevelop prerelease automation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/release-please-develop.yml:
- Around line 26-31: Update the reusable workflow’s release-version handling so
the workflow input is passed through an environment variable and validated
before use, rather than interpolated into the parse-release.sh invocation or
commit commands. Preserve the required alpha/beta/rc format validation, use the
validated value safely in shell steps, and update the referenced commit pin to
include this fix.
- Around line 14-16: Update the trigger comments near the reusable prerelease
workflow to clarify that it creates the signed tag and draft release, while
publication is performed downstream by a separate workflow; do not describe this
workflow as publishing the release.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: b34fa4bb-4de8-4dc4-bc35-67d9a321bdac
📒 Files selected for processing (1)
.github/workflows/release-please-develop.yml
📄 Knowledge reviewDosu skipped reviewing this PR because your organization has used its |
Adds a
release-please-developworkflow enabling pre-release (alpha/beta/rc) releases from thedevelopbranch, viaworkflow_dispatchor on merge of arelease:PR. It is a thin caller around the sharedopenfga/.githubreusablerelease-please-prerelease.yml, mirroring the existingrelease-pleasemain flow.Reference: https://github.com/openfga/js-sdk/blob/main/.github/workflows/release-please-develop.yml
Summary by CodeRabbit