chore: prepare 0.13.1 release

[isasmendiagus]

What

Release preparation for 0.13.1.

• Document the OkHttp read timeout fix (from Fix: Disable OkHttp read timeout to prevent premature timeouts #43) in CHANGELOG.md under [0.13.1] ### Fixed
• Set the [0.13.1] release date to 2026-07-01
• No pom.xml change: version already reads 0.13.1

Why

0.13.1 was bumped in pom.xml and added to the CHANGELOG by an earlier change (env API key support) but was never tagged or released — the latest real tag and GitHub release is v0.13.0. Rather than jump to 0.13.2 and leave a version gap, we fold the read-timeout fix into the still-unreleased 0.13.1. It ships both changes:

• Load SCANOSS API key from SCANOSS_API_KEY env var
• Disable OkHttp default read timeout (requests bounded by callTimeout)

tools/get_next_version.sh will correctly propose v0.13.1 (latest tag v0.13.0 ≠ pom 0.13.1).

Release steps (after merge)

1. Merge this PR to main.
2. Run the Repo Version Tagging workflow (workflow_dispatch) with run_for_real = true → creates and pushes tag v0.13.1.
3. The tag push triggers Publish → build/test → deploy to Maven Central + native binaries + draft GitHub Release.
4. Review and publish the draft release.

Verification of the read-timeout fix

Verified with a MockWebServer test:

• Old client (callTimeout only) dies at ~10s on a slow read (the bug).
• Fixed code (readTimeout=0, callTimeout=60s) completes a 15s slow read.
• callTimeout still bounds the request: with callTimeout=5s the call aborts at ~5s even with read timeout disabled (roof timeout preserved).

[coderabbitai]

Warning

Review limit reached

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

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

Run ID: 92efd714-fb80-4ec5-a093-b0de9fb9fc24

📥 Commits

Reviewing files that changed from the base of the PR and between c37e2dd and 8ba1724.

📒 Files selected for processing (1)

• CHANGELOG.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/prepare-release-0.13.1

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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