Release information

Where it is published

The Windows x64 build is published on npm as uuldana-cli. The newest version there is v0.1.0. The workflow Publish to npm builds it and publishes it when a version tag vX.Y.Z is pushed, using npm Trusted Publishing, so no token is stored in the repository. The binary is not code signed. There are no packages for Linux or macOS yet, and the Cargo workspace sets publish = false on every crate, so nothing is published to crates.io.

Version numbers

The binary reports both identifiers:

uuldana X.Y.Z (provider contract 0.2)

X.Y.Z is the workspace version, the same as the npm version. 0.2 is the provider contract, which identifies interface compatibility between adapters and the core and is not a release version.

Building archives

scripts/package-release.ps1 and scripts/package-release.sh write uuldana-<version>-<target>.zip or .tar.gz and a .sha256 file to target/dist. The workflow Release archives runs the same scripts on Linux, macOS, and Windows for a manual run or a v* tag, smoke-tests the packaged binary with --version, and keeps the archives as workflow artifacts. It never creates a release or uploads elsewhere.

Before publishing

1. The formatting, clippy, and test checks pass on every platform in the CI matrix.
2. The workspace version is the version being released, and Cargo.lock is current.
3. The README provider table and platform notes match what was actually verified. A provider that was not run against the real program stays marked as such.
4. The manual checks CI cannot do are done: open each installed provider through uuldana, quit it, and run a session with uuldana resume. A real failover needs a real exhausted quota, and if it was not exercised, the release notes say so.
5. The public security contact exists. Remove publish = false only for crates that are meant to be published, and only after that.

Release notes state which platforms and providers were verified and which were not.