Repository navigation
chore(platform-node): keep the spike host off npm until it is complete - #327
Conversation
`@lunora/platform-node` landed as a spike (plan 234) but was configured to publish: `.releaserc.json` present, `publishConfig.access: public`, version `0.0.0`, never released. The next `multi-semantic-release` run from this branch would have shipped a half-finished host to npm as `1.0.0-alpha.1` — durable-looking alarms nothing re-arms, a scheduler that stores jobs and never dispatches them, and no deploy driver. Marks it `private` and drops its `.releaserc.json`, matching how `@lunora/search-core` and `@lunora/dispatch` are kept unpublished — both carry the same pair and both 404 on npm. `multi-semantic-release` skips private packages, so this is the whole gate. The package stays in the workspace: it builds, its conformance and engine suites run in CI, and `--target node` remains selectable for codegen. The only thing that changes is that npm cannot receive it yet. The branch completing the host flips both back. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ Deploy Preview for lunorash ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Thank you for following the naming conventions! 🙏 |
|
Thank you for confirming the Contributor License Agreement! 🙏 |
WalkthroughThe platform-node package is now private. Its ChangesPlatform Node publication
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Why
@lunora/platform-nodelanded as a plan-234 spike but was configured to publish:.releaserc.jsonpresent,publishConfig.access: public, version0.0.0, never released. The nextmulti-semantic-releaserun fromalphawould have shipped a half-finished host to npm as1.0.0-alpha.1— alarms that persist a timestamp nothing re-arms, a scheduler that stores jobs and never dispatches them, and no deploy driver.What
Marks the package
privateand drops its.releaserc.json— the same pair@lunora/search-coreand@lunora/dispatchcarry, both of which 404 on npm.multi-semantic-releaseskips private packages, so this is the whole gate.The package stays in the workspace: it builds, its conformance and engine suites still run in CI, and
--target noderemains selectable for codegen. The only thing that changes is that npm cannot receive it yet.Follow-up
#328 completes the host and flips both settings back, so the package becomes publishable in the same change that makes it worth publishing.
Verification
lint:package-jsonclean (key order —privatesits directly afterversion).check-agents-md-packagesandcheck-sibling-peer-rangespass. No lockfile change: the drift that showed up while working on this is pre-existing and unrelated (see the follow-up PR's notes).🤖 Generated with Claude Code
Summary by CodeRabbit