Application Version Management

Application Version Management lets you control which versions of JuliaHub apps your users can launch. You decide which versions appear in the version selector, which one is the default, and whether a version is broadly available or restricted to a small group for testing.

It's typically used for add-on apps such as Pumas. Standard JuliaHub apps (such as Julia IDE and Pluto) are managed by JuliaHub directly and don't appear here, so there's no need to ask support to enable management for them.

This feature is only available on platforms with the customer admin role enabled.

Getting Access

Application Version Management must be turned on per app by JuliaHub support. If an add-on app you want to manage isn't listed in the panel, contact JuliaHub support and ask them to enable management for it.

Opening the Panel

  1. Open the Admin section in the left sidebar.
  2. Select Application Version Management.
  3. Click the card for the app you want to manage.

If the app has both CPU and GPU images, you'll be asked to pick a repository first. If it only has CPU images, you'll go straight to the version table.

How Versions Are Organized

The version table is split into two sections:

  • Managed Versions — the versions your users can see and launch. Anything in this list is part of your platform's offering for the app.
  • Available Versions — versions that exist in the container registry but aren't yet offered to users. Move a version into Managed Versions to make it available.

Per-Version Controls

Each managed version has a few settings:

  • Display Name — the user-friendly label shown in the version selector (e.g., "Julia 1.10.0"). Pick something clear; avoid latest or test.
  • Limited access — when on, only users with staging access can launch this version. When off, the version is available to everyone with access to the app. The two states are mutually exclusive: a version is either broadly available or restricted to staging users.
  • Hot Standby — keeps the image cached on standby nodes for faster session startup. See the Hot Standby guide for the full picture.
  • Default — marks this version as the default selection for new sessions. Only one version per repository can be the default.

Edits aren't saved until you click Apply Changes at the bottom of the table. Cancel discards them.

Common Tasks

Make a new version available to everyone

  1. Find the version in Available Versions (use the search box if the list is long).
  2. Click Add. The version moves into Managed Versions.
  3. Set a clear Display Name.
  4. Click Apply Changes.

Test a new version with a small group first

  1. Add the version to Managed Versions as above.
  2. Turn Limited access on. The version becomes visible only to users with staging access.
  3. Click Apply Changes.
  4. Grant staging access to your test users (see Granting staging access below).
  5. Once you're satisfied, turn Limited access off and click Apply Changes again to release it to everyone.

Granting staging access

Staging access is a per-user feature managed from Admin → Users and Groups:

  1. Find the user in the users table.
  2. Open their features (the Features column).
  3. Enable the staging feature for that user and save.

You can also pre-grant staging access to users you've invited but who haven't logged in yet — see Staged Users. For more on user features in general, see Users and Groups.

Change the default version

  1. In Managed Versions, toggle Default on for the version you want as the new default. The previous default is unset automatically.
  2. Click Apply Changes.

Pick a stable, well-tested version and let users know when the default changes.

Remove a version

  1. Click the trash icon in the Actions column.
  2. Click Apply Changes.

The version disappears from your users' selector and reappears in Available Versions, so you can add it back later if needed.

Troubleshooting

An app I want to manage isn't on the Managed Applications page. It needs to be enabled at the platform level. Contact JuliaHub support.

My changes don't seem to take effect. Confirm you clicked Apply Changes and watch for the success message. If you see an error instead, the message will indicate what went wrong; if it isn't clear, contact JuliaHub support.

A new version from the registry isn't in Available Versions yet. JuliaHub scans registries periodically. Newly pushed images can take up to an hour to appear.