Publishing Software (Packages)

The Software page doubles as the publishing tool for software packages — the builds users download from this server (udStream and other udSDK products). Browsing is open to any signed-in user; creating and editing packages requires the Server Config global permission, which reveals the Add Package and Edit controls on that page.

A package represents a named product at a specific version, with one or more downloadable deliverables attached.

Creating a Package

Click Add Package and complete the form:

FieldDescription
Package NameThe product name, e.g. udStream. Clients look packages up by this name, so keep it stable across releases.
Version StringThe human-readable version shown to users, e.g. 1.0.0.
Version NumberAn integer (≥ 1) that determines ordering. The highest version number is treated as the latest release for that package name.
VisibilityPublic (everyone) or Beta (only accounts with beta access — see below).
Release NotesOptional notes shown with the package. Markdown is supported.
DeliverablesThe downloadable files (see below).

Deliverables and Variants

Each deliverable pairs a variant with a download URL:

  • The variant names the build, typically a platform such as Windows or Linux. It becomes the label on the user's download button.
  • The download URL is where that build is hosted.

Add as many deliverables as the release needs. A package with no deliverables is still listed, but users see no download links for it.

When editing an existing package, the variant name of a deliverable that is already attached cannot be changed — remove it and add a new one if you need to rename it. New deliverables can be added at any time.

Visibility

  • Public packages are visible to every signed-in user.
  • Beta packages are visible only to accounts that hold the Beta global permission. Use Beta visibility to roll a build out to testers before making it public; change the visibility to Public when you're ready to release it widely.

Latest-Version Resolution

Applications check for updates by asking the server for the latest version of a package name for a given variant. The server returns the package with the highest version number that has a deliverable matching the requested variant — so a release only becomes "available" for a platform once a deliverable for that variant is attached.

Editing and Updating

Use the Edit action on a package to change its details, adjust visibility (for example to promote a Beta build to Public), or attach additional deliverables.

For the underlying API — including the create, list, latest, and update endpoints — see Packages in the developer guide.