Repository navigation
Fix the release tarball check against npm@latest - #7
Conversation
The v0.1.1 release has failed twice at this step. The second run took 23s and ended with "Cannot read properties of undefined (reading 'files')": the step above installs npm@latest, and npm no longer returns an array whose [0] holds the file list, so indexing it yields undefined. Nothing was ever wrong with the package — every required file was present at that tag, and the same check passes under npm 10 locally. tar -tzf reads the artifact itself and does not depend on a JSON shape npm is free to change.
|
Warning Review limit reached
Next review available in: 24 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
v0.1.1has failed to publish twice at Pack and check the tarball.The first run was the GitHub Actions outage — it hung for 30 minutes. The rerun failed in 23 seconds with the real cause:
The step above installs
npm@latest, and newer npm no longer returns an array fromnpm pack --jsonwhose[0]holds the file list. Under npm 10 locally it still does, which is why this passed when it was written.Nothing is wrong with the package: every required file was present at that tag, and
filesis unchanged.Fix: pack to a temp directory and read the artifact with
tar -tzf, which does not depend on a JSON shape npm is free to change. Verified locally — it lists the same 4 files and still fails loudly when a required one is absent.The same fix has gone into
rulebase-cli, whosesyntax-check.mjshad the identical bug and would have hit it on its first tagged release.After merging, rerun the
v0.1.1release to publishrulebase-skills@0.1.1.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.