Manage development runtimes with rvs

rvs runtime can manage local Python, Node.js, and Java installations independently of Ravenstash package repositories. Managed files live beneath ~/.rvs/runtimes and are selected through lightweight shims.

Runtime installation supports Linux. Runtime archives are accepted only after their publisher integrity material verifies: Node.js uses a signed checksum manifest and pinned release keyring, while Python and Java use published SHA-256 digests. Installation completes only after those checks succeed.

Note

Runtime management is optional. You can use rvs authentication and package commands with compatible runtimes and native tools installed by your operating system or another version manager.

Install runtimes

rvs runtime install python 3.14
rvs runtime install node 22
rvs runtime install java 21

List installed versions and locate one executable:

rvs runtime list
rvs runtime which python 3.14

Use --force with runtime install only when you intentionally want to remove and download the matching installation again.

Enable runtime shims

Print the environment changes for the current shell:

rvs runtime env

Or add the shim initialization to a supported shell startup file:

rvs runtime setup-shell

The command auto-detects Bash, Zsh, or Fish. Select one explicitly with --shell bash, --shell zsh, or --shell fish.

rvs runtime setup-shell installs runtime shims. It is separate from rvs shell setup, which adds the visible Ravenstash local profile, acting account, and package-target context to your prompt. You can use either or both integrations.

Review shell-startup changes before propagating them across managed developer machines.

Pin a project version

From a project directory:

rvs runtime use python 3.14
rvs runtime use node 22
rvs runtime use java 21

These commands write the conventional project selection files .python-version, .node-version, and .java-version. Commit them only when your team intends to share those runtime requirements.

Diagnose and remove runtimes

rvs runtime doctor
rvs runtime uninstall node 22

doctor reports the runtime manager’s local state and is the first check when a shim resolves the wrong executable. Removing a runtime does not edit project version files that still refer to it.