Skip to content

fix(cli): retrigger release after npm-stage publish fix - #3153

Merged
riderx merged 1 commit into
mainfrom
cursor/retrigger-cli-release-9be3
Aug 22, 2026
Merged

riderx merged 1 commit into
mainfrom
cursor/retrigger-cli-release-9be3

Conversation

@riderx

@riderx riderx commented Aug 21, 2026 •

Copy link
Copy Markdown
Member

Summary (AI generated)

  • Adds a one-line comment in cli/src/utils.ts with no behavior change.
  • Intentionally touches a path matched by scripts/release-scope.ts (cli/src/**) so the Bump version workflow sets run_cli=true on merge to main.

Motivation (AI generated)

PR #3152 (fix(ci): publish CLI via npm stage like plugins) fixed .github/workflows/publish_cli.yml to publish through the npm stage, but it merged without any CLI source changes. Bump version skipped the CLI release because release-scope.ts only triggers on changes under watched CLI paths (cli/src/**, cli/package.json, etc.).

PR #3151 already tagged cli-8.41.1, but that publish failed. npm still shows @capgo/cli@8.39.0, so SuperFrete and other customers cannot get the fixes from 8.41.x until a new tag is cut and published with the fixed workflow.

Business Impact (AI generated)

Unblocks publishing @capgo/cli@8.41.2 with the corrected npm-stage publish pipeline. Customers waiting on recent CLI fixes (including SuperFrete) can install the latest release once this merges and CI completes.

Test Plan (AI generated)

  • Change is comment-only; no logic, tests, version, or workflow edits.
  • File path cli/src/utils.ts matches componentMatchers.cli pattern /^cli\/src\// in scripts/release-scope.ts.
  • After merge: confirm Bump version tags cli-8.41.2 and publish_cli.yml runs successfully.
  • Do not retag or republish cli-8.41.1.

Generated with AI

Open in Web Open in Cursor 

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Review in cubic

Co-authored-by: Martin DONADIEU <martindonadieu@gmail.com>
@coderabbitai

coderabbitai Bot commented Aug 21, 2026 •

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 15 minutes

Limit details: You’ve used all 2 included reviews currently available. Your 56 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

You’re in a promotional period — use the checkbox below to run this review for free:

  • Run review for free

On-demand reviews are free for the next 30 days. After that, they cost $0.25 per reviewed file.

How can I continue?

Run this review now using the option above, or comment @coderabbitai review --use-credits.

You can also wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5545f8c6-97f6-4f5c-bd29-3f0ea63c64e9

📥 Commits

Reviewing files that changed from the base of the PR and between a32c4c5 and e169a6f.

📒 Files selected for processing (1)
  • cli/src/utils.ts

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

@codspeed

codspeed Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks1


Comparing cursor/retrigger-cli-release-9be3 (e169a6f) with main (a32c4c5)

Open in CodSpeed

Footnotes

  1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

@sonarqubecloud

Copy link
Copy Markdown

@riderx
riderx marked this pull request as ready for review August 22, 2026 05:07
@riderx
riderx merged commit 6c08959 into main Aug 22, 2026
65 of 67 checks passed
@riderx
riderx deleted the cursor/retrigger-cli-release-9be3 branch August 22, 2026 05:07

This branch was previously deployed

1 inactive deployment
deepsec-pr — e169a6fc Deployed Aug 21, 2026 by riderx via Scan PR changes #4759
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.

2 participants