GitLab

GitLab CI/CD: Tag-Based Releases

Applies to: Gatewayruntime for API, AI, and MCP gateways
Hosting: Managed EdgeManaged DedicatedSelf-HostedDiffers

1 difference by hosting option

Self-Hosted

Add --self-hosted-endpoint with your management API hostname to each zuplo deploy command so it targets your cluster. See zuplo deploy.

Deploy only when tags are pushed for controlled releases.

.gitlab-ci.yml
image: node:24

stages:
  - deploy

deploy:
  stage: deploy
  script:
    - npm install
    - npx zuplo deploy --api-key "$ZUPLO_API_KEY" --environment "$CI_COMMIT_TAG"
  only:
    - tags

This pipeline triggers only on tags and creates an environment named after the tag (e.g., v1.0.0).

Next Steps

Add multi-stage deployment with approval

Edit this page

Last modified on October 22, 2026

Local testing in CI Multi-Stage Deployment