chore: promote staging to main — publish pipeline fix

[himerus]

Summary

• fix: mark internal packages (@helixir/core, @helixir/github-action) as "private": true so changeset publish stops trying to publish them to npm

This fixes the Publish workflow that has been failing on every merge to main since v0.4.0. The @helixir npm scope doesn't exist, causing 404 errors when changesets tries to publish the internal workspace packages.

What changes

• packages/core/package.json — added "private": true
• packages/github-action/package.json — added "private": true

Expected result

After merge, the Publish workflow should succeed — helixir publishes normally, internal packages are skipped.

Summary by CodeRabbit

• Chores
  • Marked the core and github-action packages as private in their respective package configurations to prevent accidental publication to external package registries. These internal packages are now fully protected from unintended public releases and will remain available exclusively for internal project development and use.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8a37b6f3-17b2-420d-bf81-bf5d70a63dd4

📥 Commits

Reviewing files that changed from the base of the PR and between e7eae41 and cc4a3ce.

📒 Files selected for processing (2)

• packages/core/package.json
• packages/github-action/package.json

---

Walkthrough

Marks two internal packages as private by adding a "private": true field to their respective package.json files. This prevents these packages from being published to npm registries.

Changes

Cohort / File(s)	Summary
Package Configuration packages/core/package.json, packages/github-action/package.json	Added "private": true field to mark both packages as non-publishable.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Migrate release pipeline to changesets (PUBLISHING.md standard) #44: Marks the same packages as private via Changesets' ignore list, providing an alternative or complementary approach to prevent publishing.
• fix: harden release pipeline for reliable unattended npm publish #41: Adjusts npm publish behavior through package.json metadata modifications, addressing the same goal of controlling package publication.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch staging

📝 Coding Plan

• Generate coding plan for human review comments

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}