Skip to content

ci(node): run npm publish on a github-hosted runner for provenance#14

Merged
upsetbit merged 1 commit into
masterfrom
ci/npm-publish-github-hosted
Jul 4, 2026
Merged

ci(node): run npm publish on a github-hosted runner for provenance#14
upsetbit merged 1 commit into
masterfrom
ci/npm-publish-github-hosted

Conversation

@upsetbit

@upsetbit upsetbit commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

The main @c3-oss/codexcw publish failed with E422 … Unsupported GitHub Actions runner environment: "self-hosted". Only "github-hosted" runners are supported when publishing with provenance. — npm provenance requires a
GitHub-hosted runner, and Blacksmith is self-hosted.

Move only the lightweight publish job to ubuntu-latest (free on public
repos) so provenance is issued; the build matrix stays on Blacksmith. The six
platform packages already published on the prior run; napi pre-publish will
skip them and publish the main package.

🤖 Generated with Claude Code

npm only issues provenance attestations on GitHub-hosted runners, and
Blacksmith is self-hosted (publish failed with E422). Move just the publish
job to ubuntu-latest (free on public repos) while the build matrix stays on
Blacksmith, so `@c3-oss/codexcw` publishes with provenance.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@upsetbit upsetbit merged commit 6266cbc into master Jul 4, 2026
@upsetbit upsetbit deleted the ci/npm-publish-github-hosted branch July 4, 2026 00:40
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.

1 participant