Repository navigation
fix(cli): retrigger release after npm-stage publish fix - #3153
Conversation
Co-authored-by: Martin DONADIEU <martindonadieu@gmail.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. 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:
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 You can also wait for the limit to reset, then comment 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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
Comment |
Merging this PR will not alter performance
Comparing Footnotes
|
|



Summary (AI generated)
cli/src/utils.tswith no behavior change.scripts/release-scope.ts(cli/src/**) so theBump versionworkflow setsrun_cli=trueon merge tomain.Motivation (AI generated)
PR #3152 (
fix(ci): publish CLI via npm stage like plugins) fixed.github/workflows/publish_cli.ymlto publish through the npm stage, but it merged without any CLI source changes.Bump versionskipped the CLI release becauserelease-scope.tsonly 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.2with 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)
cli/src/utils.tsmatchescomponentMatchers.clipattern/^cli\/src\//inscripts/release-scope.ts.Bump versiontagscli-8.41.2andpublish_cli.ymlruns successfully.cli-8.41.1.Generated with AI
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.