Skip to content

Bump central publishing maven plugin#61

Merged
IgorDobryn merged 2 commits into
mainfrom
bump-central-publishing-maven-plugin
Jul 13, 2026
Merged

Bump central publishing maven plugin#61
IgorDobryn merged 2 commits into
mainfrom
bump-central-publishing-maven-plugin

Conversation

@IgorDobryn

@IgorDobryn IgorDobryn commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Motivation

Changes

  • Bump central-publishing-maven-plugin version
  • Update deploy config not to wait until new SDK version is fully published

How to test

  • Merge this PR
  • Draft, review, approve, merge release PR
  • Trigger workflow to deliver new SDK version
  • Assert version is released

Summary by CodeRabbit

  • Chores
    • Updated the Maven publishing workflow to use the latest publishing plugin version.
    • Builds now proceed after Central validation rather than waiting for publication completion.

@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@IgorDobryn, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fcddf226-22e8-4792-ba7d-34c0ea9ab38f

📥 Commits

Reviewing files that changed from the base of the PR and between 1a9b099 and 9efd2a7.

📒 Files selected for processing (1)
  • pom.xml
📝 Walkthrough

Walkthrough

The Maven Central Publishing plugin was upgraded from 0.5.0 to 0.11.0, and waitUntil was changed from published to validated.

Changes

Central publishing configuration

Layer / File(s) Summary
Update publishing plugin configuration
pom.xml
The Central Publishing Maven plugin now uses version 0.11.0 and waits for the validated state instead of published.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: upgrading the central publishing Maven plugin.
Description check ✅ Passed The description follows the template and covers changes and testing, but the Motivation section is empty and Images/GIFs are omitted.
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.

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

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 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 `@pom.xml`:
- Line 219: Remove the stray “k” immediately before the <version> element in the
Maven plugin configuration, leaving valid XML and preserving the 0.11.0 version
value.
🪄 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

Run ID: 80b9fc60-33ee-4d0b-9408-3ff964dbc56e

📥 Commits

Reviewing files that changed from the base of the PR and between 2e0625f and 1a9b099.

📒 Files selected for processing (1)
  • pom.xml

Comment thread pom.xml Outdated
@IgorDobryn IgorDobryn force-pushed the bump-central-publishing-maven-plugin branch from 1a9b099 to 9efd2a7 Compare July 13, 2026 11:26
@IgorDobryn IgorDobryn merged commit 84bc5de into main Jul 13, 2026
2 checks passed
@IgorDobryn IgorDobryn deleted the bump-central-publishing-maven-plugin branch July 13, 2026 13:04
@github-actions github-actions Bot mentioned this pull request Jul 13, 2026
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.

3 participants