Skip to content

chore(code): bump version to 0.1.12#83

Merged
amondnet merged 1 commit into
mainfrom
chore/bump-code-version
Jan 29, 2026
Merged

chore(code): bump version to 0.1.12#83
amondnet merged 1 commit into
mainfrom
chore/bump-code-version

Conversation

@amondnet

@amondnet amondnet commented Jan 29, 2026

Copy link
Copy Markdown
Contributor

Summary

Manual version bump to 0.1.12 to include logger sync mode fix for bundled binaries.

Changes

  • Update packages/code/package.json version to 0.1.12
  • Update .release-please-manifest.json

Why manual bump?

The logger fix was in packages/logger which is not tracked by release-please.
The fix resolves ModuleNotFound: thread-stream error in compiled binaries.


Summary by cubic

Manually bump @pleaseai/code to 0.1.12 to include the logger sync mode fix for bundled binaries. This prevents the “ModuleNotFound: thread-stream” error in compiled builds.

Written for commit 44a4398. Summary will update on new commits.

Manual version bump to include logger sync mode fix for bundled binaries.
@amondnet
amondnet merged commit aeca7db into main Jan 29, 2026
3 checks passed
@amondnet
amondnet deleted the chore/bump-code-version branch January 29, 2026 02:53
@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @amondnet, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request implements a targeted version update for the packages/code module to 0.1.12. This manual increment is essential to propagate a critical logger fix that prevents ModuleNotFound errors in bundled binaries, thereby enhancing the reliability of compiled applications.

Highlights

  • Manual Version Bump: The packages/code module has been manually bumped to version 0.1.12.
  • Critical Bug Fix Integration: This version bump integrates a fix from packages/logger that resolves a ModuleNotFound: thread-stream error occurring in compiled binaries.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request manually bumps the version of @pleaseai/code to 0.1.12. The version updates in packages/code/package.json and .release-please-manifest.json are correct. However, the changelog for packages/code is missing an entry for this new version. I've kept the comment suggesting this update. To prevent such manual interventions in the future, I recommend adding the packages/logger package to release-please-config.json so its version can be managed automatically.

"name": "@pleaseai/code",
"type": "module",
"version": "0.1.11",
"version": "0.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

With a manual version bump, it's important to also manually update the changelog. Please add an entry to packages/code/CHANGELOG.md for version 0.1.12 detailing the logger fix mentioned in the pull request description. This ensures users are aware of the changes in the new release.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 2 files

@codecov

codecov Bot commented Jan 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 39.27%. Comparing base (bf3d94f) to head (44a4398).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #83   +/-   ##
=======================================
  Coverage   39.27%   39.27%           
=======================================
  Files          59       59           
  Lines        6503     6503           
=======================================
  Hits         2554     2554           
  Misses       3949     3949           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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