Skip to content

Conversation

@kdcokenny
Copy link
Collaborator

@kdcokenny kdcokenny commented Jan 15, 2026

Problem

The platform-specific npm packages (oh-my-opencode-linux-x64, oh-my-opencode-darwin-arm64, etc.) are returning 404 from npm because they were never published.

Root Cause

SKIP_PLATFORM_PACKAGES: true was added in commit 0230e71 by @justsisyphus on Jan 16 as a temporary workaround when OIDC wasn't configured for the platform packages. The 'for now' workaround was never removed.

Fix

Remove the SKIP_PLATFORM_PACKAGES: true flag so the publish workflow publishes all 8 packages (main + 7 platform binaries).

Note

For the first publish of the platform packages, ensure NPM_TOKEN is configured as a repo secret since OIDC/Trusted Publisher can only be configured after the packages exist on npm.

After the first successful publish, configure Trusted Publisher on npmjs.com for each of the 8 packages to enable OIDC authentication going forward.


Summary by cubic

Enable publishing of platform-specific npm packages by removing SKIP_PLATFORM_PACKAGES from the CI workflow. Fixes 404 installs for platform binaries and ensures the main package plus 7 platform packages are published.

  • Migration
    • For the first publish, add NPM_TOKEN as a repo secret.
    • After the first successful publish, configure Trusted Publisher (OIDC) on npm for all 8 packages.

Written for commit f76e909. Summary will update on new commits.

Remove SKIP_PLATFORM_PACKAGES flag that was temporarily added as a workaround
when OIDC wasn't configured. This was preventing the 7 platform-specific
binary packages from being published to npm, causing 404 errors when users
tried to install oh-my-opencode.

The platform packages (oh-my-opencode-{darwin,linux,windows}-{arm64,x64}, etc.)
contain the Bun single-file executables for each platform and are required
for the CLI to work without Bun installed.
Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

CI: true
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_CONFIG_PROVENANCE: true
SKIP_PLATFORM_PACKAGES: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This still needs an NPM_TOKEN to be injected, just FYI

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep, working with Q to get that done b4 merging

@code-yeongyu
Copy link
Owner

Closing as duplicate - the same change was already pushed directly in commit ec2cf22 on Jan 17. Thanks for the PR @kdcokenny!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants