Publication status of the packages
This page replaces the 3.0.0-era “Package Publishing Guide”, which described publishing individual npm packages at version 3.0.0 with a publish-all script. That process is not part of the 1.0.0 release candidate, and the site is not a publishing runbook; this page states what is, and is not, published.
Nothing is published yet
Release line 1.0.0-rc.7. No package of any of the ten targets is on a public registry; the decided coordinates are listed on Packages of the 1.0.0 release candidate and resolve nowhere until the launch publishes them. Until then, build from source (Installation Guide).
How a release is made
- One version for every package of a release line (
1.0.0-rc.Ncandidates,1.0.0the complete release), spelled per ecosystem (1.0.0rc7,v1.0.0-rc.7,1.0.0-rc7); the spellings are derived and checked by tooling, not typed. - Candidates are built and verified locally before anything is published: a crate registry for Rust, a wheel and sdist for Python, npm tarballs, a Maven repository, a NuGet feed, a Go module proxy, a CMake prefix and a SwiftPM path dependency, each consumed by a clean consumer that can reach nothing else and replays the catalog’s profiles through the package. The quickstarts on this site were run that way (2026-10-09).
- Registry accounts belong to the SovereignWallet-Network organisation (owner decision of 2026-09-16); publication is a hand-run, reviewed step, never an automatic one.
- Withdrawal follows each registry’s rules (release policy in the source repository): a published version is deprecated or yanked with a message, never deleted, so that builds which pinned it keep resolving.
- CocoaPods is not a channel; Swift is distributed through SwiftPM git tags only.
Where to look
The authoritative records are in the source repository: documents/public-release/namespaces.json (names, ownership, adoption of the release line), release-policy.md (versions, tags, withdrawal), cutover-runbook.md (the launch sequence) and the evidence files under documents/public-release/evidence/. This page carries no command; the packaging tools are internal release tooling, not consumer API.