Skip to content

chore(code): bump version to 0.1.12 and add manual publish#85

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

chore(code): bump version to 0.1.12 and add manual publish#85
amondnet merged 1 commit into
mainfrom
chore/bump-code-version

Conversation

@amondnet

@amondnet amondnet commented Jan 29, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Bump @pleaseai/code version to 0.1.12 (includes logger sync mode fix)
  • Add workflow_dispatch with publish_only option for manual npm publish

Changes

  1. Version bump: packages/code 0.1.11 → 0.1.12
  2. CI: Add manual trigger for publish workflow

Manual publish usage

Go to Actions → Release Please → Run workflow → Check "Skip release-please and publish directly"


Summary by cubic

Bumped @pleaseai/code to 0.1.12 with a logger sync mode fix for bundled binaries. Added a manual publish path to let us publish to npm without waiting for a release.

  • New Features

    • Added workflow_dispatch with a publish_only input to skip release-please and publish directly (Actions → Release Please → Run workflow → enable “Skip release-please and publish directly”).
    • Updated publish job to run when a release is created or when publish_only is true.
  • Bug Fixes

    • Includes logger sync mode fix in @pleaseai/code 0.1.12 for bundled binaries.

Written for commit 070dbfe. Summary will update on new commits.

@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 updates the version of the @pleaseai/code package to 0.1.12, incorporating a logger sync mode fix. Concurrently, it enhances the CI/CD process by introducing a manual trigger for npm publishing, providing greater flexibility in release management.

Highlights

  • Version Bump: The @pleaseai/code package has been updated from version 0.1.11 to 0.1.12. This update is reflected in both the .release-please-manifest.json and packages/code/package.json files, and includes a fix for logger sync mode.
  • Manual Publish Workflow: A workflow_dispatch option has been added to the CI/CD pipeline, enabling manual triggering of the npm publish workflow. This allows for direct publishing by selecting 'Skip release-please and publish directly' in the GitHub Actions UI.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/release-please.yml
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.

Add workflow_dispatch with publish_only option to manually trigger
npm publish without waiting for release-please to create a release.

Also add NODE_AUTH_TOKEN for npm publish.
@amondnet
amondnet force-pushed the chore/bump-code-version branch from 58eed79 to 070dbfe Compare January 29, 2026 02:59
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying code-please with  Cloudflare Pages  Cloudflare Pages

Latest commit: 070dbfe
Status:⚡️  Build in progress...

View logs

@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 bumps the version of the @pleaseai/code package from 0.1.11 to 0.1.12 in packages/code/package.json and .release-please-manifest.json. These changes are consistent with the PR's objective to prepare for a new release. The modifications are correct and look good to merge.

@amondnet
amondnet merged commit 7c3bd4d into main Jan 29, 2026
2 of 4 checks passed
@amondnet
amondnet deleted the chore/bump-code-version branch January 29, 2026 02:59

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

1 issue found across 3 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name=".github/workflows/release-please.yml">

<violation number="1" location=".github/workflows/release-please.yml:51">
P2: Using `always()` will run the publish job even if `release-please` fails. Use `!failure() && !cancelled()` instead to allow running when skipped (for `publish_only` mode) but prevent publishing when the release job actually fails.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

publish:
needs: release-please
if: ${{ needs.release-please.outputs.release_created == 'true' }}
if: ${{ always() && (needs.release-please.outputs.release_created == 'true' || inputs.publish_only) }}

@cubic-dev-ai cubic-dev-ai Bot Jan 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2: Using always() will run the publish job even if release-please fails. Use !failure() && !cancelled() instead to allow running when skipped (for publish_only mode) but prevent publishing when the release job actually fails.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/release-please.yml, line 51:

<comment>Using `always()` will run the publish job even if `release-please` fails. Use `!failure() && !cancelled()` instead to allow running when skipped (for `publish_only` mode) but prevent publishing when the release job actually fails.</comment>

<file context>
@@ -40,7 +48,7 @@ jobs:
   publish:
     needs: release-please
-    if: ${{ needs.release-please.outputs.release_created == 'true' }}
+    if: ${{ always() && (needs.release-please.outputs.release_created == 'true' || inputs.publish_only) }}
     runs-on: ubuntu-latest
     permissions:
</file context>
Suggested change
if: ${{ always() && (needs.release-please.outputs.release_created == 'true' || inputs.publish_only) }}
if: ${{ !failure() && !cancelled() && (needs.release-please.outputs.release_created == 'true' || inputs.publish_only) }}
Fix with Cubic

@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 (cd8ba57) to head (070dbfe).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #85   +/-   ##
=======================================
  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