chore(release): prepare 0.52.0

[elkaix]

Automated release prep for 0.52.0. Tag after merge (C1).

Summary by CodeRabbit

• Chores
  • Version bumped to 0.52.0
  • Updated installation instructions and documentation across all platforms (Windows, Linux, and system package managers) to reflect the new version

[coderabbitai]

📝 Walkthrough

Walkthrough

Version bump from 0.51.0 to 0.52.0: pyproject.toml version field updated, CHANGELOG.md gains a new release section header, and all installation documentation in root and packages/linux-installer READMEs updated with new artifact filenames, URLs, and checksum references.

Changes

Release 0.52.0 Version Bump

Layer / File(s)	Summary
Version field and changelog header pyproject.toml, CHANGELOG.md	version bumped to 0.52.0; new ## 0.52.0 (2026-06-23) section added after ## Unreleased.
README installer references README.md, packages/linux-installer/README.md	All version strings, installer executable names (PythinkerSetup-0.52.0.exe), Linux .deb/.rpm artifact filenames, download URLs, and sha256sum checksum filenames updated from 0.51.0 to 0.52.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Pythoughts-labs/pythinker-code#176: Same release-bump pattern across the identical four files, updating installer artifact filenames and version references from the prior release to the next.
• Pythoughts-labs/pythinker-code#173: Mechanical version bump of CHANGELOG.md, README.md, packages/linux-installer/README.md, and pyproject.toml — directly analogous to this PR for 0.50.0.
• Pythoughts-labs/pythinker-code#163: Same release-bump workflow updating the same four files with installer artifact filenames and checksum commands for 0.48.0.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is minimal but appropriate for an automated release preparation, though it omits most template sections like Related Issue and Checklist items.	Consider filling in the Related Issue section and confirming checklist items (especially changelog and docs generation) were completed for this automated release.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows conventional commits format with type 'chore' and scope 'release', clearly describing the main change: preparing version 0.52.0.
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 release/0.52.0

---

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

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/linux-installer/README.md (1)

39-39: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Build script example still references 0.51.0, contradicting expected output.

Line 39 shows the build example as bash packages/linux-installer/build.sh 0.51.0, but lines 44–45 now document the expected outputs as 0.52.0 artifacts. A user following the example as written would produce 0.51.0 binaries, which contradicts the stated release version. Update line 39 to 0.52.0.

🔧 Proposed fix

-bash packages/linux-installer/build.sh 0.51.0
+bash packages/linux-installer/build.sh 0.52.0

🤖 Prompt for 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.

In `@packages/linux-installer/README.md` at line 39, The build command example on
line 39 uses version 0.51.0, but the expected output documentation on lines
44-45 references 0.52.0 artifacts, creating a contradiction. Update the version
argument in the bash packages/linux-installer/build.sh command example from
0.51.0 to 0.52.0 to align with the documented expected output.

🤖 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.

Outside diff comments:
In `@packages/linux-installer/README.md`:
- Line 39: The build command example on line 39 uses version 0.51.0, but the
expected output documentation on lines 44-45 references 0.52.0 artifacts,
creating a contradiction. Update the version argument in the bash
packages/linux-installer/build.sh command example from 0.51.0 to 0.52.0 to align
with the documented expected output.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f2f33b68-fae1-4d7b-b329-58854b440a3a

📥 Commits

Reviewing files that changed from the base of the PR and between 7394800 and 88df99e.

⛔ 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!