Install and publish packages with rvs
rvs runs native package tools with temporary credentials for the repository or
mirror you selected. It does not provide a second install or publish interface.
Install from any supported target
Section titled “Install from any supported target”Select a private repository or mirror, then run the appropriate native tool:
rvs art select platform/packagesrvs pip install internal-sdk
rvs art mirror select pypiorgrvs pip install requests
rvs art mirror select npmjsrvs npm install lodash
rvs art mirror select maven-centralrvs mvn dependency:get -Dartifact=org.slf4j:slf4j-api:2.0.17Install with pip or uv using temporary authentication:
rvs pip install internal-sdk==1.2.3rvs uv pip install internal-sdk==1.2.3Build and publish distributions with the native wrappers:
rvs art select platform/packagesrvs uv buildrvs twine upload dist/*# Or publish through uv:rvs uv publishrvs art select platform/packagesrvs npm install @acme/design-systemrvs npm publishResolve a coordinate or deploy the selected project:
rvs art select platform/packagesrvs mvn dependency:get -Dartifact=com.acme:internal-sdk:1.2.3rvs mvn deployFor one prepared file, use Maven’s deploy-file goal:
rvs mvn org.apache.maven.plugins:maven-deploy-plugin:3.1.3:deploy-file \ -Dfile=target/internal-sdk-1.2.3.jar \ -DgroupId=com.acme \ -DartifactId=internal-sdk \ -Dversion=1.2.3 \ -Dpackaging=jarPublishing wrappers show the destination and planned content before invoking the
native tool. In guarded automation, pass --rvs-yes.
Official and custom mirrors are read-only. Select a private repository before publishing:
rvs art select platform/releasesrvs npm publishUse rvs art endpoint --format pypi|npm|maven to inspect a credential-free
native address. Use rvs art native config TOOL or rvs art token mint when a
tool cannot be run through an rvs wrapper.

