<aside> 🔔 This is generated documentation; DO NOT EDIT. / Generated by: Update Handbook GitHub Action / Last updated: 2024-09-28T07:08:31Z / Generated from: sourcegraph/managed-services@b149888

</aside>

This document describes operational guidance for Release Registry infrastructure. This service is operated on the Managed Services Platform (MSP).

If you need assistance with MSP infrastructure, reach out to the Core Services team in #discuss-core-services.

<aside> 🚨 Due to Notion limitations, we currently recreate the contents of each page entirely on updates. This means you cannot share links to sections within these pages, as the linked blocks will not persist - sourcegraph/notionreposync#7 tracks future improvements to this mechanism.

</aside>

Service overview

• Service ID: releaseregistry (specification)
• Owners: dev-experience
• Service kind: Cloud Run service
• Environments:
  • prod
  • dev
• Docker image: us.gcr.io/sourcegraph-dev/releaseregistry
• Source code: [github.com/sourcegraph/releaseregistry - .](https://github.com/sourcegraph/releaseregistry/tree/HEAD/.)

Rollouts

• Delivery pipeline: releaseregistry-us-central1-rollout
• Stages: dev -> prod

Changes to Release Registry are continuously delivered to the first stage (dev) of the delivery pipeline.

Promotion of a release to the next stage in the pipeline must be done manually using the GCP Delivery pipeline UI.

Environments