Publishing Your Plugin
Prerequisites
- Plugin built and tested locally
- Noorle API key with plugin:upload permission
- Account with sufficient quota
Via CLI
Via Console UI
- Navigate to Capabilities → Plugins
- Click New Plugin or Upload Version
- Select
.npackfile - Review metadata and permissions
- Click Upload
Plugin Metadata in Registry
After uploading, your plugin appears in the registry with:Version Management
Understanding Versions
Plugins support multiple versions for iterative development:Creating New Versions
When you upload an updated plugin:- Detects it’s the same plugin (by name)
- Creates version v2
- Makes v2 the new active version
- Preserves version v1 for rollback
Setting Active Version
Change which version is active: Via CLI:- Go to Capabilities → Plugins → my-plugin
- Find Versions section
- Click Make Active on desired version
Viewing Version History
Semantic Versioning
While plugin versions are numbered (v1, v2, v3), adopt semantic versioning for your releases:Version Naming Convention
Include semantic version in your plugin archive and noorle.yaml:Handling Breaking Changes
Major Version Bump
When making breaking changes:Backported Fixes
Support older versions with critical fixes:Rollback Strategy
Quick Rollback
If v3 has bugs, rollback to v2:Gradual Rollout
Test new versions with subset of agents:Deprecation
Mark Version as Deprecated
Document when versions will be unsupported:End of Life
After sunset date, retire the version:Access Control
Share Plugins
Plugins are account-scoped by default. Share with other accounts:Version Permissions
Control which versions are accessible:Publishing Best Practices
Pre-Release Checklist
Before publishing:- Run all tests locally
- Verify plugin builds without warnings
- Test all tools with sample inputs
- Review noorle.yaml configuration
- Check file size (under 5MB)
- Verify network/filesystem permissions
- Update README with changes
- Document new tools
- Test with actual agents/MCP gateways