Skip to content

ci: add release-please-develop pre-release workflow - #303

Merged
SoulPancake merged 1 commit into
mainfrom
feat/release-please-develop
Jul 29, 2026
Merged

ci: add release-please-develop pre-release workflow#303
SoulPancake merged 1 commit into
mainfrom
feat/release-please-develop

Conversation

@SoulPancake

@SoulPancake SoulPancake commented Jul 28, 2026

Copy link
Copy Markdown
Member

Adds a release-please-develop workflow enabling pre-release (alpha/beta/rc) releases from the develop branch, via workflow_dispatch or on merge of a release: PR. It is a thin caller around the shared openfga/.github reusable release-please-prerelease.yml, mirroring the existing release-please main flow.

Reference: https://github.com/openfga/js-sdk/blob/main/.github/workflows/release-please-develop.yml

Summary by CodeRabbit

  • Chores
    • Added automated prerelease release management for the develop branch.
    • Prereleases can be initiated automatically or manually with a specified release version.

Copilot AI review requested due to automatic review settings July 28, 2026 11:37
@SoulPancake
SoulPancake requested a review from a team as a code owner July 28, 2026 11:37
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.93%. Comparing base (9449df9) to head (a0b6dc7).

❌ Your project status has failed because the head coverage (69.93%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #303   +/-   ##
=======================================
  Coverage   69.93%   69.93%           
=======================================
  Files         142      142           
  Lines       10774    10774           
=======================================
  Hits         7535     7535           
  Misses       3239     3239           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new GitHub Actions workflow to enable pre-release (alpha/beta/rc) automation from the develop branch by invoking the shared openfga/.github reusable workflow, mirroring the existing stable release-please flow on main.

Changes:

  • Introduces .github/workflows/release-please-develop.yml to run pre-release automation on develop (push) or via workflow_dispatch.
  • Wires the workflow to the shared reusable release-please-prerelease.yml pinned by SHA, passing base-branch/staging-branch and release inputs.
  • Aligns trigger/guard behavior (startsWith(..., 'release:')) and permissions structure with the existing release-please.yml workflow.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

A new GitHub Actions workflow manages prerelease release-PR creation from develop, supporting push and manual triggers. Eligible runs invoke a pinned reusable workflow with branch, version, permissions, and release-signing configuration.

Changes

Develop prerelease workflow

Layer / File(s) Summary
Trigger and version input configuration
.github/workflows/release-please-develop.yml
Adds develop push triggering and manual dispatch with a required alpha, beta, or release-candidate version input.
Conditional prerelease job wiring
.github/workflows/release-please-develop.yml
Runs for manual dispatches or release: commits and delegates to the pinned reusable workflow using develop and release-develop branch settings, release inputs, permissions, and secrets.

Estimated code review effort: 2 (Simple) | ~10 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHub as GitHub event
  participant DevelopWorkflow as release-please-develop workflow
  participant ReusableWorkflow as release-please-prerelease workflow
  GitHub->>DevelopWorkflow: Push to develop or workflow_dispatch
  DevelopWorkflow->>DevelopWorkflow: Check event and release version
  DevelopWorkflow->>ReusableWorkflow: Invoke prerelease workflow with branches, inputs, and secrets
  ReusableWorkflow->>GitHub: Create or publish prerelease release PR
Loading

Suggested reviewers: aaguiarz, copilot

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the new release-please-develop pre-release workflow added in this PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/release-please-develop

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:
- Line 16: Update the trigger documentation comment on line 16 to state that
merging the release PR creates a signed tag and draft prerelease, while
publication is handled later by the publish workflow; remove the claim that this
trigger publishes the release.
- Line 44: Update the reusable workflow’s workflow_dispatch handling to pass
release-version through an env variable before any shell assignment, validate
that environment variable with the pre-release regex, and use it for validation
and commit operations. Then update the caller’s pinned reusable-workflow
reference in release-please-develop.yml so it points to the fixed revision.
🪄 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: f6781bbb-faa0-43b4-b7cb-0be802b6c7c4

📥 Commits

Reviewing files that changed from the base of the PR and between 9449df9 and a0b6dc7.

📒 Files selected for processing (1)
  • .github/workflows/release-please-develop.yml

Comment thread .github/workflows/release-please-develop.yml
Comment thread .github/workflows/release-please-develop.yml
@SoulPancake
SoulPancake enabled auto-merge July 29, 2026 05:58
@SoulPancake
SoulPancake added this pull request to the merge queue Jul 29, 2026
Merged via the queue into main with commit 2875c26 Jul 29, 2026
41 checks passed
@SoulPancake
SoulPancake deleted the feat/release-please-develop branch July 29, 2026 05:58
@dosubot

dosubot Bot commented Jul 29, 2026

Copy link
Copy Markdown

📄 Knowledge review

Dosu skipped reviewing this PR because your organization has used its 200 included credits for the month. Your usage will reset on 2026-08-01. To have Dosu review this PR before then, ask your organization admin to upgrade to a pro account.


Leave Feedback Ask Dosu about python-sdk Add Dosu to your team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants