Publishing & Versioning

Use predictable release discipline to keep plugins stable across platform updates.

Versioning

Noxus uses semantic versioning for plugin packages. This is defined in your pyproject.toml or manifest.json.

# pyproject.toml
[project]
name = "weather-plugin"
version = "1.2.0" # Major.Minor.Patch

Pre-release validation

Run the validation tool to ensure schema compatibility.

noxus plugin validate --path ./my-plugin

Build & Package

Package your plugin for distribution.

noxus plugin build --path ./my-plugin

Deploy to Registry

Push your plugin to the Noxus registry or your private instance.

noxus plugin push --version 1.2.0

Inputs/Outputs: Never remove or rename existing inputs/outputs in a minor version; only add optional ones.
Config Migration: Provide default values for new configuration fields to avoid breaking existing deployments.
Deprecation: Mark old nodes as deprecated before removing them in a major version update.

⌘I