Skip to content

feat(release): publish the plugin to npm - #21

Merged
yannelli merged 1 commit into
mainfrom
feat/publish-plugin-to-npm
Oct 5, 2026
Merged

yannelli merged 1 commit into
mainfrom
feat/publish-plugin-to-npm

Conversation

@yannelli

@yannelli yannelli commented Oct 5, 2026

Copy link
Copy Markdown
Owner

The Release workflow now publishes @yannelli/paseo-be-concise to npm after the GitHub release step. The step publishes the package.json version when npm does not have it yet, so reruns complete an interrupted publish. Paseo installs it with paseo plugin add npm:@yannelli/paseo-be-concise.

package.json drops private, takes the @yannelli scoped name, lists the plugin source in files, and sets public access with provenance. The job grants id-token: write. npm uses trusted publishing when the package has a trusted publisher and the NPM_TOKEN repository secret otherwise. docs/npm-publishing.md lists the npm trust command, which needs a 2FA login after the first publish.

Testing

  • npm run check (typecheck and 37 tests pass)
  • npm pack --dry-run lists 22 files: the entries, client/, server/, shared/, paseo-plugin.json, README, and LICENSE

The release workflow publishes @yannelli/paseo-be-concise after the GitHub release. It uses trusted publishing when configured and the NPM_TOKEN secret otherwise.
@yannelli
yannelli merged commit fa4d96b into main Oct 5, 2026
1 check passed
@yannelli
yannelli deleted the feat/publish-plugin-to-npm branch October 5, 2026 04:10
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