Skip to content

chore: fix release pipeline for publish gradle file#339

Merged
SoulPancake merged 1 commit into
mainfrom
fix/release-pipeline-publish-gradle
May 4, 2026
Merged

chore: fix release pipeline for publish gradle file#339
SoulPancake merged 1 commit into
mainfrom
fix/release-pipeline-publish-gradle

Conversation

@SoulPancake
Copy link
Copy Markdown
Member

@SoulPancake SoulPancake commented May 4, 2026 •
edited by coderabbitai Bot
Loading

Description

What problem is being solved?

How is it being solved?

What changes are made to solve it?

References

Review Checklist

  • I have clicked on "allow edits by maintainers".
  • I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
  • The correct base branch is being used, if not main
  • I have added tests to validate that the change in functionality is working as expected

Summary by CodeRabbit

  • Chores
    • Version updated to 0.9.8 in release configuration.

Copilot AI review requested due to automatic review settings May 4, 2026 14:49
@SoulPancake SoulPancake requested a review from a team as a code owner May 4, 2026 14:49
@SoulPancake SoulPancake enabled auto-merge May 4, 2026 14:51
@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented May 4, 2026 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 38.47%. Comparing base (e91ced8) to head (45243b6).

Additional details and impacted files 
@@             Coverage Diff              @@
##               main     #339      +/-   ##
============================================
- Coverage     38.48%   38.47%   -0.02%     
+ Complexity     1268     1267       -1     
============================================
  Files           198      198              
  Lines          7704     7704              
  Branches        900      900              
============================================
- Hits           2965     2964       -1     
  Misses         4591     4591              
- Partials        148      149       +1

☔ View full report in Codecov by Sentry.
📢 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.

@SoulPancake SoulPancake added this pull request to the merge queue May 4, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 4, 2026 •
edited
Loading

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1bcb46a7-4864-4080-9b42-63af4540f39f

📥 Commits

Reviewing files that changed from the base of the PR and between e91ced8 and 45243b6.

📒 Files selected for processing (2)
  • publish.gradle
  • release-please-config.json

Walkthrough

The POM version in the Maven publication configuration is pinned to a literal value with a release-please version marker, and the release-please configuration is updated to track this file during automated releases.

Changes

Release Automation Configuration

Layer / File(s) Summary
Version Marker & POM Configuration
publish.gradle		 Maven publication POM version is set to fixed literal '0.9.8' (marked with // x-release-please-version) instead of deriving from project.version.
Release Automation Setup
release-please-config.json		 publish.gradle is added to the extra-files array so release-please tracks version updates in this file during automated releases.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested reviewers

  • rhamzeh
  • emilic
  • jimmyjames
🚥 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 'chore: fix release pipeline for publish gradle file' accurately describes the main changes: updating publish.gradle versioning and release-please configuration to fix the release pipeline.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/release-pipeline-publish-gradle

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

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
Review rate limit: 0/1 reviews remaining, refill in 60 minutes.

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

Copilot AI reviewed May 4, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates release-please configuration to also bump versions in publish.gradle, and adds a release-please version marker in the publishing script to support automated releases.

Changes:

  • Added publish.gradle to release-please-config.json extra-files so release-please will update it during releases.
  • Replaced project.version usage in publish.gradle with a literal version string annotated with x-release-please-version.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
release-please-config.json Adds publish.gradle to release-please’s tracked extra files for version bumping.
publish.gradle Introduces an x-release-please-version marker by hardcoding the version in publishing metadata.

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

Comment thread publish.gradle
Merged via the queue into main with commit 7c8f062 May 4, 2026
28 of 31 checks passed
@SoulPancake SoulPancake deleted the fix/release-pipeline-publish-gradle branch May 4, 2026 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@rhamzeh rhamzeh rhamzeh approved these changes

@curfew-marathon curfew-marathon curfew-marathon approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@SoulPancake @codecov-commenter @rhamzeh @curfew-marathon