Publishing SDK Packages

Overview

The @made-open/sdk, @made-open/plugin-sdk, and @made-open/shared packages are published to npm using Changesets for version management and GitHub Actions for automated publishing.

All three packages use linked versioning — when any package changes, all three get the same version bump.

Setup (one-time)

1. Create an npm account and join the @made-open organization
2. Create an automation token: npmjs.com → Access Tokens → Generate → Automation
3. Add to GitHub: repo Settings → Secrets → Actions → NPM_TOKEN

Making a Release

1. Make your changes to packages/sdk, packages/plugin-sdk, or packages/shared
2. Run pnpm changeset — select the affected packages, bump type (patch/minor/major), and write a summary
3. Commit the generated changeset file (in .changeset/) and push to main
4. CI creates a "Version Packages" PR that bumps versions in package.json files
5. Review and merge the PR → CI publishes to npm automatically

Manual Publish (emergency)

npm login --scope=@made-open
pnpm release

Verifying Package Contents

Before publishing, you can check what files would be included:

pnpm -F @made-open/sdk pack --dry-run
pnpm -F @made-open/plugin-sdk pack --dry-run
pnpm -F @made-open/shared pack --dry-run

Package Details