Skip to content

v3.2.3#325

Merged
bl-ue merged 1 commit intomainfrom
release/3.2.3
Jan 1, 2026
Merged

v3.2.3#325
bl-ue merged 1 commit intomainfrom
release/3.2.3

Conversation

@bl-ue
Copy link
Copy Markdown
Member

@bl-ue bl-ue commented Jan 1, 2026

Summary by CodeRabbit

  • New Features

    • Added --verbose flag for enhanced output
    • Increased search window to 1,000 characters
  • Bug Fixes

    • Fixed native installation support
  • Chores

    • Released version v3.2.3

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jan 1, 2026

📝 Walkthrough

Walkthrough

A version bump release from v3.2.2 to v3.2.3 that updates version strings across package metadata and source files, and documents four improvements in the changelog.

Changes

Cohort / File(s) Summary
Changelog Entry
CHANGELOG.md
Added new Unreleased section for v3.2.3 (2026-01-01) documenting four changes: increased thinkerFormat search window, new --verbose flag, debug logs for native module loading, and native installation support fix
Version Metadata
package.json
Updated version field from "3.2.2" to "3.2.3"
Version Strings in Source
src/index.tsx, src/patches/index.ts
Bumped CLI and patch version strings from 3.2.2 to 3.2.3

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop and a bump, from two to the three,
Version strings dance where they're meant to be!
Changelog sings of fixes and flags,
No bugs left behind in our version bags! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'v3.2.3' is overly vague and generic, using only a version number without describing what changed or why this release matters. Consider a more descriptive title such as 'Release v3.2.3' or 'v3.2.3: Add verbose flag and improve native installation support' to better convey the purpose and scope of changes.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b984601 and d13511f.

📒 Files selected for processing (4)
  • CHANGELOG.md
  • package.json
  • src/index.tsx
  • src/patches/index.ts
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-12-31T20:58:54.456Z
Learnt from: signadou
Repo: Piebald-AI/tweakcc PR: 322
File: package.json:84-86
Timestamp: 2025-12-31T20:58:54.456Z
Learning: In package.json, ensure engines.node reflects the runtime requirement (the minimum Node.js version needed to run the built artifacts), not the build-time tool. For this project, set "engines": {"node": ">=20.0.0"} if runtime requires Node 20.x, even if the build tool (e.g., tsdown) needs a newer version.

Applied to files:

  • package.json
🔇 Additional comments (4)
CHANGELOG.md (1)

10-15: LGTM! Changelog entry is well-formatted.

The v3.2.3 entry follows the established format and properly documents the four changes with PR references and author attributions. The "Unreleased" section correctly remains as a placeholder for future changes.

src/index.tsx (1)

28-28: LGTM! CLI version string correctly updated.

The version string is properly bumped to match the package.json version and will display correctly in tweakcc --version output.

src/patches/index.ts (1)

592-592: LGTM! Patch indication version correctly updated.

The version string passed to writePatchesAppliedIndication is properly updated to '3.2.3', ensuring the correct version is displayed in the patched Claude Code installation.

package.json (1)

3-3: LGTM! Package version correctly bumped.

The version field is properly updated to "3.2.3", maintaining consistency across all files in this release.


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

@bl-ue bl-ue merged commit 254d033 into main Jan 1, 2026
1 of 2 checks passed
@bl-ue bl-ue deleted the release/3.2.3 branch January 1, 2026 18:00
This was referenced Jan 4, 2026
@coderabbitai coderabbitai bot mentioned this pull request Jan 18, 2026
This was referenced Feb 5, 2026
@coderabbitai coderabbitai bot mentioned this pull request Feb 23, 2026
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