Publishing & Store

This guide explains how to publish your NetPad plugin, submit it to the Plugin Store, and manage updates.

1. Versioning

• Use semantic versioning (e.g., 1.0.0, 1.1.0, 2.0.0)
• Update the version field in your manifest.json for every release
• Breaking changes require a major version bump

2. Publishing Workflow

1. Build your plugin:

   npm run build
2. Publish to the registry:

   netpad plugins publish
   • Validates your manifest and files
   • Uploads your plugin to the NetPad Plugin Registry (MongoDB Atlas)
   • Runs automated security and compatibility checks

3. Submitting to the Plugin Store

• After publishing, submit your plugin for review:

  netpad plugins submit --store
• Provide a description, screenshots, and usage examples
• The NetPad team will review for security, quality, and compliance
• Approved plugins appear in the Plugin Store for all users

4. Updating Plugins

• Update your code and manifest
• Bump the version (e.g., 1.0.1 → 1.1.0)
• Re-publish and re-submit for review if needed

5. Deprecation & Removal

• Deprecated plugins are marked in the store
• Users are notified of removals or breaking changes
• Use the Plugin Store dashboard to manage your published plugins

Further Reading

• Plugin Manifest Reference
• Development Workflow
• Security & Audit
• Examples

For more, see the Plugin Sprint Plan.