Repository navigation
ci: use npm stage publish for 2FA - #6
Conversation
npm no longer allows long-lived bypass_2fa tokens. Stage the package in plugin CI, then let Cap-go/automations approve it.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 41 minutes Limit details: You’ve used the included review currently available. Your 60 included PR review attempts over the past 7 days set your current allowance at 1 review 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 31 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 (3)
Comment |
Beta npm buildMaintainers can publish this PR to npm for fast testing. Comment The workflow will:
Security note: beta publish is only enabled for branches inside this repository. |
There was a problem hiding this comment.
1 issue found across 3 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".github/workflows/build.yml">
<violation number="1" location=".github/workflows/build.yml:57">
P1: When this workflow stages the package with npm 11.15.0, npm removes its `bin` mapping, so installed releases no longer expose `capgo-capacitor-patch`. Fix the package’s bin metadata and verify the staged tarball retains the executable mapping before publishing.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| - name: Publish to npm with next tag | ||
| run: | | ||
| npm --version | ||
| npm stage publish --provenance --access public --ignore-scripts |
There was a problem hiding this comment.
P1: When this workflow stages the package with npm 11.15.0, npm removes its bin mapping, so installed releases no longer expose capgo-capacitor-patch. Fix the package’s bin metadata and verify the staged tarball retains the executable mapping before publishing.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/build.yml, line 57:
<comment>When this workflow stages the package with npm 11.15.0, npm removes its `bin` mapping, so installed releases no longer expose `capgo-capacitor-patch`. Fix the package’s bin metadata and verify the staged tarball retains the executable mapping before publishing.</comment>
<file context>
@@ -46,16 +46,32 @@ jobs:
- - name: Publish to npm with next tag
+ run: |
+ npm --version
+ npm stage publish --provenance --access public --ignore-scripts
+ - name: Stage publish to npm with next tag
if: ${{ contains(github.ref, '-alpha.') }}
</file context>
Stage publish cannot set pr-N tags without 2FA. Point testers at @beta/@Version after automations approves.
Stage publish cannot refresh dist-tags without 2FA. The in-progress comment must match that.
There was a problem hiding this comment.
All reported issues were addressed across 1 file (changes from recent commits).
Requires human review: Auto-approval blocked because this review re-detected 1 unresolved issue already reported by Cubic.
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
Plugin repos should not describe the internal approver.
There was a problem hiding this comment.
1 issue found across 2 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".github/workflows/pr_beta_publish.yml">
<violation number="1" location=".github/workflows/pr_beta_publish.yml:247">
P3: The success comment now reads "Latest beta:" right after showing "Status: staged". The package is only staged at this point (the approval dispatch for the org's 2FA review runs with continue-on-error, and the beta becomes installable only after Cap-go/automations approves it). Removing the prior "(after Cap-go/automations approves the stage)" qualifier leaves the install commands (bun add package@beta) looking immediately available while the header still says staged, which can mislead a reader who tries them before approval. Keep the qualification or align the heading to the staged state.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
| @@ -236,11 +247,7 @@ jobs: | |||
| 'Latest beta:', | |||
There was a problem hiding this comment.
P3: The success comment now reads "Latest beta:" right after showing "Status: staged". The package is only staged at this point (the approval dispatch for the org's 2FA review runs with continue-on-error, and the beta becomes installable only after Cap-go/automations approves it). Removing the prior "(after Cap-go/automations approves the stage)" qualifier leaves the install commands (bun add package@beta) looking immediately available while the header still says staged, which can mislead a reader who tries them before approval. Keep the qualification or align the heading to the staged state.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/pr_beta_publish.yml, line 247:
<comment>The success comment now reads "Latest beta:" right after showing "Status: staged". The package is only staged at this point (the approval dispatch for the org's 2FA review runs with continue-on-error, and the beta becomes installable only after Cap-go/automations approves it). Removing the prior "(after Cap-go/automations approves the stage)" qualifier leaves the install commands (bun add package@beta) looking immediately available while the header still says staged, which can mislead a reader who tries them before approval. Keep the qualification or align the heading to the staged state.</comment>
<file context>
@@ -244,7 +244,7 @@ jobs:
`Requested by @${actor}`,
'',
- 'Latest beta (after Cap-go/automations approves the stage):',
+ 'Latest beta:',
'```sh',
`bun add ${packageName}@beta`,
</file context>
| 'Latest beta:', | |
| 'Latest beta (after Cap-go/automations approves the stage):', |
What
npm publishtonpm stage publish.Why
How
NPM_TOKEN.Testing
@capgo/capacitor-wifi.Not Tested
/publish-betaon a live PR.