chore(release): prepare 0.62.0

[elkaix]

Related Issue

N/A — scheduled root Pythinker CLI release.

Description

• Prepare the root pythinker-code CLI release as version 0.62.0.
• Promote the authored Unreleased changelog entries into the dated 0.62.0 section.
• Regenerate the documentation changelog and update version-derived README, installer, pyproject, and lockfile references.
• Do not bump independently versioned packages under packages or sdks.

Checklist

• I have read the CONTRIBUTING document.
• I have linked the related issue, if any. No issue applies to this release-preparation PR.
• I have added tests that prove my fix is effective or that my feature works. Release automation passed version/dependency gates and 9 lockstep tests; pre-push hooks passed the full check and test suites.
• I have run make gen-changelog to update the changelog. The release orchestrator promoted CHANGELOG.md and ran the authoritative docs changelog sync directly.
• I have run make gen-docs to update the user documentation. The release orchestrator updated the affected generated and version-derived documentation.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 21 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: c46d1c91-5600-485d-9159-6aea26ac5b1d

📥 Commits

Reviewing files that changed from the base of the PR and between 14c13f8 and 2aab35c.

⛔ Files ignored due to path filters (4)

• docs/en/guides/getting-started.md is excluded by !docs/**
• docs/en/release-notes/breaking-changes.md is excluded by !docs/**
• docs/en/release-notes/changelog.md is excluded by !docs/**
• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• CHANGELOG.md
• README.md
• packages/linux-installer/README.md
• pyproject.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/0.62.0

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!