Skip to main content
Current documentVerified

Installation, registries and versions

SeeraOS packages use private registries. Public documentation access does not grant package download permissions. Obtain the appropriate feed address and a read credential from your deployment administrator. Access provisioning process and contact: information to be supplied.

Release snapshot​

These versions describe documentation and published packages read on 2026-10-10. They are not a compatibility matrix for every combination.

Package / toolVersion
Unit SDK .NET1.13.0
seeraos-unit-sdk Python0.8.0
seeraos-unit-sdk and seeraos-unit-sdk-types Rust0.9.0
dev.seeraos:unit-sdk Java0.9.0
@seeraos/unit-sdk TypeScript1.11.0
Platform Dev Toolkit0.18.0

The reviewed Composer pins Unit SDK .NET 1.12.0 and conformance 0.56.0. The source TypeScript template pins SDK 1.8.0, toolkit 0.15.0 and Node 24. These pins remain meaningful; do not replace them collectively with the newest version.

Access configuration​

EcosystemMappingCredential location
NuGetSeeraOS.* names to the appropriate private feedUser configuration / deployment mechanism
uvexplicit = true and mapping seeraos-unit-sdk to the indexUV_INDEX_SEERAOS_USERNAME and UV_INDEX_SEERAOS_PASSWORD variables
CargoPrivate sparse index and cargo:tokenOutside the project, with a Bearer prefix
Gradle / Mavendev.seeraos group to the appropriate registryUser properties / Maven settings file
npm / pnpm@seeraos scope to the private registryUser .npmrc file

Do not place tokens in the project, feed URL or lock file. The tutorial host registry.example.com is a placeholder for the administrator-provided address; it is not a SeeraOS registry. The Cargo example keeps registry name gitea to match dependencies and credentials.

First diagnosis​

401 usually points to authentication and feed mapping. 404 or no matching version can result from the registry address, permissions or runtime version. For Python also check ≥3.12; for Java check the toolchain ≥25. A Cargo token without cargo:token or a Bearer prefix does not match the source registry configuration. For npm check identical host, path and trailing slash in registry and auth lines.

Choose a language tutorial and use troubleshooting if needed. Installing dependencies does not perform enrollment or apply.