fix: mark internal packages as private to fix publish pipeline#73
fix: mark internal packages as private to fix publish pipeline#73
Conversation
chore: promote dev → staging
chore: promote staging → main (v0.3.0)
chore: version packages
feat: multi-dimensional health scoring + source-level accessibility analysis
fix: changeset targets helixir (root package) + CodeRabbit ignore config
fix: add root to pnpm workspace for changeset resolution
chore: version packages
chore: promote dev to staging — audit hardening
chore: promote staging to main — security audit hardening
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
Summary
Problem
The Publish GitHub Action fails on every merge to main because
changeset publishtries to publish@helixir/coreand@helixir/github-actionto npm. The@helixirscope doesn't exist on the npm registry, so both get 404 errors, and the entire publish step fails with exit code 1.The root
helixirpackage publishes fine (or is skipped if version is unchanged). The failure is exclusively from the two internal workspace packages.Evidence
PR #72 merge to main (2026-03-17): P...
Recovered automatically by Automaker post-agent hook