Publishing a .niso package takes four commands. Everything after the first login step can live in your CI pipeline.
If you haven't already, install niso on your development machine.
$ curl -sSL https://niso.online/install.sh | shRequires Linux with systemd 250+ and cgroups v2. macOS and Windows developers can use niso machine for a lightweight development VM.
Open your API keys page and create a key with push permission on @your-username/*. Copy the key immediately — it's shown only once.
Log in on the machine that will do the push. Pasting the key when prompted.
$ niso loginThe CLI stores the token in ~/.config/niso/credentials with 0600 permissions. In CI, pass the token via --token $NISO_TOKEN instead.
Create a manifest.toml next to your binary and run niso pack. The result is a portable .niso archive.
$ niso pack --binary target/release/my-appSee the manifest reference for required and optional fields.
Upload the package to the niso registry. The manifest name must match the URL, and you must have push permission on the namespace.
$ niso push @your-username/my-app:1.0.0Tags are aliases that point to a specific version. The latest tag is the default when users run niso pull without a version.
$ niso tag @your-username/my-app latest 1.0.0Publishing problems? See the registry docs, or email support@niso.online. We usually reply within a day.