Repository navigation
chore: publish to npm as @e2b/opencode - #20
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Publish the plugin to npm as
@e2b/opencode, released from CI over trusted publishing (OIDC). No npm token exists anywhere.Users get
opencode plugin add @e2b/opencodefor the plugin andnpm install -g @e2b/opencodefor theopencode-e2bcommand. Until now the only way in was a local checkout: the package wasprivate, and an install from GitHub fails becausedist/is not committed.How
package.json: name@e2b/opencode,privateremoved,publishConfig.access: public,repository,license,keywords(opencode-plugingets it listed on OpenDock),LICENSEinfiles. Scriptsversionandrelease(notpublish, which npm runs as a lifecycle hook and re-enterschangeset publish)..github/workflows/ci.yml:bun run checkon PRs and main. The repo had no CI..github/workflows/release.yml: dispatch only, modeled one2b-dev/eve-sandbox, plus the ref check and the "commit before publish, push only if tagged" order fromcode-interpreter. The publish job runs in thedeploymentenvironment (main only); the npm trusted publisher will be pinned to it.LICENSE: Apache-2.0, ase2b-dev/E2Bandcode-interpreter.package-lock.jsonremoved:bun.lockis the lockfile CI uses, and the npm one still carried the old name.e2b-opencode/<version>(wasopencode-e2b-workspace-plugin/<version>).Release order
npm trust github @e2b/opencode --repo e2b-dev/opencode-e2b --file release.yml --env deployment --allow-publish.gh workflow run release.yml --ref mainpublishes 0.2.1 with provenance.Already set up:
deploymentenvironment (main only),Main branchruleset (1 approval, CLA andCheckrequired, version bumper bypass), version bumper app installed.Tested
bun run check: 101 tests pass, lint and format clean.npm-clean-tarball.sh, 107 entries, no devDependencies): a global install runsopencode-e2b --help,bin/bashkeeps its executable bit, and OpenCode 2.2.1 loads the installed copy as a plugin (/e2b-statusreplies).