---
# Helper container images the scenarios use for probing. Here rather than inline in each
# verify.yml, so there is one pin per image instead of one per role, and so Renovate can see
# them. See the customManager in .github/renovate.json.

# Used to reach a role's container over its own container network, because the role publishes
# no host port - exactly as in a real deployment. Publishing one for the test would collide
# between scenarios running in parallel.
# renovate: datasource=docker depName=docker.io/curlimages/curl
molecule_shared_image_curl: "docker.io/curlimages/curl:8.22.0"

# Used for small stub services (a fake homeserver, and so on).
# renovate: datasource=docker depName=docker.io/library/python
molecule_shared_image_python: "docker.io/library/python:3.14-alpine"

# Postgres for scenarios whose role has a database. Pinned at the major the postgres role
# deploys to new installations, and left to Renovate from there: when a new major lands,
# the PR bumping this pin runs every scenario that uses Postgres against it, which is the
# earliest warning we get that a component does not cope. Users who upgrade Postgres promptly are on that major
# well before the postgres role makes it the default for new installations.
# renovate: datasource=docker depName=docker.io/library/postgres
molecule_shared_image_postgres: "docker.io/library/postgres:18.6-alpine"

# Real SFU for the LiveKit JWT service's room creation and publishing grants.
# renovate: datasource=docker depName=docker.io/livekit/livekit-server
molecule_shared_image_livekit_server: "docker.io/livekit/livekit-server:v1.13.7"