fix(release): allow Maven publication propagation

[kriptoburak]

Maven Central published 0.8.0 shortly after the existing 10-minute verification cutoff. Extend the bounded signature-verification window to 20 minutes and derive retry attempts from named timing values.

Verified locally:

• full Gradle check
• release workflow contract check
• public 0.8.0 signature and expected signing fingerprint

---

Summary by cubic

Extends the Maven Central signature verification window from 10 to 20 minutes and derives retry attempts from the timeout and delay values to avoid hardcoded limits. This prevents release failures when publication lags slightly (as happened with 0.8.0).

^{Written for commit c6a537a. Summary will update on new commits.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 6 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4258c56e-0e0c-4668-baac-f0ba6271af62

📥 Commits

Reviewing files that changed from the base of the PR and between ceb35d9 and c6a537a.

📒 Files selected for processing (1)

• bin/verify-release-signature

---

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