Publish packages from GitLab CI/CD

Create an automation token owned by the same personal account or organization as the repository. Add it under Settings → CI/CD → Variables as RVS_TOKEN.

Mark the value Masked. Mark it Protected when only protected branches or tags should publish packages.

Python example

.gitlab-ci.yml

publish-python:
  image: ubuntu:24.04
  stage: deploy
  rules:
    - if: $CI_COMMIT_TAG
  script:
    - curl -fsSL https://ravenstash.com/install.sh | bash
    - rvs art select platform/packages
    - rvs uv build
    - rvs uv publish

Replace platform/packages with the namespace and repository names shown in Ravenstash.

npm and Maven

Select the repository with rvs art select platform/packages, then run rvs npm publish or rvs mvn deploy. rvs supplies the selected registry URL and temporary authentication.

The package-type publish guides contain the native configuration:

• Publish Python packages
• Publish npm packages
• Publish Maven artifacts

Verify before removing old credentials

Run the pipeline against a new package version, inspect it in Ravenstash, and resolve that exact version through the corresponding download host. Delete a replaced token only after every protected release path succeeds.