feat(cli): add multi-platform npm release foundation#27
Conversation
Abdulmuiz44
commented
Jun 2, 2026
Abdulmuiz44
commented
- Adds multi-platform binary packaging foundation for @codra/cli.
- Adds artifact-based packaging script for linux, macOS, and Windows targets.
- Adds manual GitHub Actions release workflow draft.
- Keeps npm publish guarded and disabled by default.
- Preserves current local host build/test/pack flow.
- Does not publish to npm yet.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 89945aa917
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - name: Set up Node.js | ||
| uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 20 |
There was a problem hiding this comment.
When publish: true is used, this job sets NODE_AUTH_TOKEN only on the npm publish step, but the preceding actions/setup-node invocation does not specify registry-url, so it never writes the .npmrc entry that tells npm to use that token. The setup-node docs state that registry-url creates project-level npm config with auth read from env.NODE_AUTH_TOKEN (https://github.com/actions/setup-node#readme), and I also checked npm whoami --registry=https://registry.npmjs.org/ with only NODE_AUTH_TOKEN set locally, which still reports ENEEDAUTH; as a result, the guarded publish path will build and pack successfully but fail at the final npm publish.
Useful? React with 👍 / 👎.
| artifact: codra-linux-arm64 | ||
| bin_name: codra | ||
| - target: darwin-x64 | ||
| os: macos-13 |
There was a problem hiding this comment.
The darwin-x64 matrix leg is pinned to macos-13, but GitHub announced that the macOS 13 runner image was retired by December 4, 2025 and that macos-13 is one of the removed labels (https://github.blog/changelog/2025-09-19-github-actions-macos-13-runner-image-is-closing-down/). On current GitHub-hosted runners this leg will fail before building the Intel macOS binary, so the release workflow cannot collect all required artifacts or publish the multi-platform package.
Useful? React with 👍 / 👎.
1 participant
