Skip to content

chore(release): prepare 0.35.0 - #79

Merged
elkaix merged 4 commits into
mainfrom
release/0.35.0
Jun 5, 2026
Merged

chore(release): prepare 0.35.0#79
elkaix merged 4 commits into
mainfrom
release/0.35.0

Conversation

@elkaix

@elkaix elkaix commented Jun 4, 2026

Copy link
Copy Markdown
Member

Related Issue

Release prep; no linked issue.

Description

Prepares the 0.35.0 release by:

  • Bumping the root pythinker-code package version to 0.35.0.
  • Promoting the authored Unreleased changelog entries into the 0.35.0 release section.
  • Syncing generated docs changelog content from the root CHANGELOG.md.
  • Updating README, getting-started, and Linux installer version references.
  • Documenting that docs/en/release-notes/changelog.md must not be edited manually and updating release tooling to sync it from the canonical root changelog.

Checklist

  • Changelog updated from the authored root CHANGELOG.md.
  • Docs changelog regenerated with node docs/scripts/sync-changelog.mjs / npm run sync.
  • Version lockstep test passed locally: uv run pytest tests/test_version_lockstep.py -q.
  • CI checks passed on the release branch.

Summary by CodeRabbit

  • Documentation
    • Added 0.35.0 release entries to changelogs and breaking-changes; updated “What’s New”, getting-started, installer, and other docs to reference 0.35.0 assets and instructions; added contributor guidance about changelog edits.
  • Chores
    • Project version bumped to 0.35.0; installer/package filenames and install/verification commands updated; release tooling adjusted to sync docs changelog from the canonical changelog.

@coderabbitai

coderabbitai Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: dacb3816-9b83-4e5f-8138-c1f47d3b5150

📥 Commits

Reviewing files that changed from the base of the PR and between 32c56c2 and 33ff572.

📒 Files selected for processing (1)
  • scripts/release.py

📝 Walkthrough

Walkthrough

This pull request bumps the project version to 0.35.0, inserts dated 0.35.0 release headers into changelogs, updates README/getting-started/linux-installer docs to reference 0.35.0 artifacts, adds an AGENTS.md rule about generated docs, and modifies the release script to regenerate the docs changelog during release rewrites.

Changes

Release 0.35.0 Version Bump

Layer / File(s) Summary
Project version and release headers
pyproject.toml, CHANGELOG.md, docs/en/release-notes/breaking-changes.md, docs/en/release-notes/changelog.md
Project [project].version bumped to 0.35.0; dated ## 0.35.0 (2026-06-04) headers inserted into CHANGELOG and release-notes files.
Documentation and installer version references
README.md, docs/en/guides/getting-started.md, packages/linux-installer/README.md, AGENTS.md
Updated README “What’s New”, Quick Start, Windows installer filenames, Linux .deb/.rpm artifact filenames and .sha256 verification commands to 0.35.0; added AGENTS.md rule marking docs changelog as generated.
Release script: docs changelog sync
scripts/release.py
Removed docs changelog from the hand-edited CHANGELOG_FILES list, added DOCS_CHANGELOG_SCRIPT and require_executable(), implemented sync_docs_changelog() which runs docs/scripts/sync-changelog.mjs, requires node in validate(), and calls the sync from rewrite() before other version-string rewrites.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 50.00% which is insufficient. The required threshold is 70.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed Title follows conventional commits format with correct type (chore), scope (release), and clear description of the 0.35.0 version bump.
Description check ✅ Passed Description covers the release prep objectives, mentions version bump, changelog promotion, docs sync, and updated documentation, with completed checklist items.
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 docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/0.35.0

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov

codecov Bot commented Jun 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 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 `@docs/en/release-notes/changelog.md`:
- Around line 20-21: Revert the manual change to the header "## 0.35.0
(2026-06-04)" in docs/en/release-notes/changelog.md and regenerate the file from
the canonical root CHANGELOG.md using the repository's sync flow (run the sync
script or CI job that updates docs from root CHANGELOG.md); ensure future edits
are made only in the root CHANGELOG.md so the header is produced automatically
by the sync process.

In `@packages/linux-installer/README.md`:
- Around line 44-45: Update the example build command in README.md to use the
0.35.0 version string instead of 0.34.0 so it matches the artifact names;
specifically change the occurrence of "bash packages/linux-installer/build.sh
0.34.0" to "bash packages/linux-installer/build.sh 0.35.0" to keep the
documented example consistent with the `pythinker-code_0.35.0_amd64.deb` and
`pythinker-code-0.35.0.x86_64.rpm` entries.
🪄 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 23428fe0-0d92-4848-b98a-31dcc9fecf97

📥 Commits

Reviewing files that changed from the base of the PR and between 420af0e and b7cb2d7.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (7)
  • CHANGELOG.md
  • README.md
  • docs/en/guides/getting-started.md
  • docs/en/release-notes/breaking-changes.md
  • docs/en/release-notes/changelog.md
  • packages/linux-installer/README.md
  • pyproject.toml

Comment thread docs/en/release-notes/changelog.md
Comment thread packages/linux-installer/README.md

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

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 `@scripts/release.py`:
- Around line 159-160: Add a preflight check in validate() to ensure the `node`
binary is available before any file mutations happen; call shutil.which("node")
(or equivalent) and if it returns None raise a ReleaseError with a clear,
actionable message telling the user that `node` is not on PATH and how to
recover (e.g., install Node.js or add it to PATH) so sync_docs_changelog() won't
produce an uncaught FileNotFoundError after
set_root_version()/promote_changelog()/rewrite() have mutated files; keep
sync_docs_changelog() as-is but document that it assumes validate() has
confirmed `node` presence.
🪄 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 4ac6f14a-8888-4d5a-ae27-9e804c702305

📥 Commits

Reviewing files that changed from the base of the PR and between 793efeb and 32c56c2.

📒 Files selected for processing (2)
  • AGENTS.md
  • scripts/release.py

Comment thread scripts/release.py Outdated
@elkaix
elkaix merged commit 4856060 into main Jun 5, 2026
50 checks passed
@elkaix
elkaix deleted the release/0.35.0 branch June 5, 2026 00:22
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.

1 participant