Skip to content

chore(release): prepare 0.33.0 - #74

Merged
elkaix merged 1 commit into
mainfrom
release/0.33.0
Jun 3, 2026
Merged

chore(release): prepare 0.33.0#74
elkaix merged 1 commit into
mainfrom
release/0.33.0

Conversation

@elkaix

@elkaix elkaix commented Jun 3, 2026

Copy link
Copy Markdown
Member

0.33.0 release prep

Changes in this release:

  • Three-scope config resolution (User → Project → Local). Five-step merge pipeline for ~/.pythinker/config.toml, .pythinker/config.toml, and .pythinker/config.local.toml. Scope-locked fields blocked from project/local files; local files auto-gitignored on first use; PYTHINKER_* env vars overlay all file sources.
  • Pythinker identity: developed by Pythoughts-labs. Package metadata, --version output, and pythinker info updated.
  • ❓ question marker standardized. Single QUESTION_MARKER constant replaces inconsistent glyphs across transcript, panel, pager, and prompt.
  • Scratchpad isolated to current session. Scratch files deleted on every session exit; no stale planning from prior sessions.
  • SetTodoList gated behind explicit plan approval. Tool description and system prompt now enforce the plan-first contract.

Files changed: pyproject.toml, uv.lock, CHANGELOG.md, docs/en/release-notes/changelog.md, docs/en/release-notes/breaking-changes.md, README.md, docs/en/guides/getting-started.md, packages/linux-installer/README.md

Local gates passed: check_version_tag.py, README heading/snippet checks, CHANGELOG grep, check_pythinker_dependency_versions.py, tests/test_installation_docs.py, tests/test_homebrew_formula.py

Summary by CodeRabbit

Release 0.33.0

  • Bug Fixes & Improvements

    • Enhanced config resolution across different scopes
    • Improved scratchpad session isolation cleanup on exit
    • Standardized question display glyphs
    • Identity and metadata updates
  • Changes

    • SetTodoList now requires explicit user plan approval
  • Documentation

    • Updated installation guides and getting-started documentation
    • Confirmed backward compatibility with version 0.32.0

@coderabbitai

coderabbitai Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

This PR bumps Pythinker Code to version 0.33.0. The project version in pyproject.toml is incremented, and all release documentation, changelog entries, and installation guides across README, getting-started docs, release notes, and Linux installer instructions are updated to reference the new version and its feature/breaking-change details.

Changes

Release 0.33.0 Preparation

Layer / File(s) Summary
Version declaration update
pyproject.toml
Project version incremented from 0.32.0 to 0.33.0.
Release notes and changelog entries
CHANGELOG.md, docs/en/release-notes/changelog.md, docs/en/release-notes/breaking-changes.md, README.md
CHANGELOG and release-notes documents updated with 0.33.0 release header, feature changes list, explicit no-breaking-changes declaration, and upgrade instructions; README "What's New" section refreshed with 0.33.0 content.
Installation and getting-started documentation
README.md, docs/en/guides/getting-started.md, packages/linux-installer/README.md
README Quick Start and Windows/Linux installation instructions, getting-started guide, and Linux installer README updated to reference 0.33.0 Windows executables, Linux package filenames/URLs, checksums, build commands, and verification steps.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • Pythoughts-labs/pythinker-code#70: Version bump and release-prep documentation update swapping 0.32.0 → 0.33.0 across the same surfaces (pyproject.toml, CHANGELOG.md, README.md, docs/en/release-notes/*, and packages/linux-installer/README.md).
  • Pythoughts-labs/pythinker-code#59: Release-prep version and documentation bump updating the same set of files for a different 0.x release.
  • Pythoughts-labs/pythinker-code#53: Release-prep version bump across CHANGELOG.md, README.md, packages/linux-installer/README.md, and pyproject.toml for a different release version.

Suggested labels

dependencies

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive Description provides detailed release notes covering all changes, but omits the required template structure with explicit Related Issue, full Checklist sections, and CONTRIBUTING acknowledgment. Fill in Related Issue section (or explicitly state none), and complete all checklist items with confirmations rather than just listing files changed and gate results.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed Title follows conventional commits format with valid type (chore), appropriate scope (release), and clearly describes the main change (prepare 0.33.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.33.0

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

@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 `@docs/en/release-notes/changelog.md`:
- Around line 20-31: The changes to docs/en/release-notes/changelog.md must be
reverted because that file is auto-synced from the root CHANGELOG.md; undo any
manual edits to docs/en/release-notes/changelog.md (or revert the commit/patch
that touched it) and instead make any release-note edits in the root
CHANGELOG.md so the sync script can propagate them; ensure you do not
reintroduce edits to docs/en/release-notes/changelog.md in this PR and run the
sync script locally to verify the generated docs match before pushing.
🪄 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: 6090b758-1918-4170-8a2d-8d99055b2f6b

📥 Commits

Reviewing files that changed from the base of the PR and between d12c505 and a60bde2.

⛔ 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
@codecov

codecov Bot commented Jun 3, 2026

Copy link
Copy Markdown

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment

Thanks for integrating Codecov - We've got you covered ☂️

@elkaix
elkaix merged commit 5066a83 into main Jun 3, 2026
55 checks passed
@elkaix
elkaix deleted the release/0.33.0 branch July 17, 2026 20:04
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