pnpm publish. Publishing is always done from the monorepo root — never from inside an individual package directory.
Published Packages
| Package | Registry name | Visibility |
|---|---|---|
packages/sdk | agent-economy-wallet | Public |
packages/wallet-core | @agent-economy-wallet/core | Public |
packages/mcp-server | @agent-economy-wallet/mcp-server | Public |
@agent-economy-wallet/cli are marked "private": true and are never published.
Prerequisites
- A free npmjs.com account
- An npm organisation named
agent-economy-wallet(required for scoped packages like@agent-economy-wallet/core) - Two-Factor Authentication (2FA) enabled on your npm account
Publishing Steps
Bump versions
Edit the
"version" field inside the package.json of each package you changed. All three published packages should stay in sync:packages/sdk/package.jsonpackages/wallet-core/package.jsonpackages/mcp-server/package.json
patch for fixes, minor for new features, major for breaking changes.Publish the workspace
pnpm publish -r recursively publishes every non-private package in the workspace. It automatically replaces internal workspace:* references with real version numbers in the published bundle — so consumers never see them.Get your
--otp code from your authenticator app (Google Authenticator, Authy, etc.) immediately before running this command — OTP codes expire in 30 seconds.What Gets Published
The SDK (agent-economy-wallet) is a thin re-export layer over @agent-economy-wallet/core and @agent-economy-wallet/mcp-server. Consumers can use a single import: