cmd/assets/memcached.Dockerfile.txt currently hard-codes the Renovate datasource and package target to alpine_3_22/php83-pecl-memcache:
# renovate: datasource=repology depName=alpine_3_22/php83-pecl-memcache
ARG PHP_MEMCACHE_VERSION=8.2-r0
RUN apk add --no-cache php83-pecl-memcache=="${PHP_MEMCACHE_VERSION}"
That assumes both Alpine 3.22 and PHP 8.3. The target Drupal Dockerfile may use a different Alpine release and PHP package family, such as php83, php84, or
php85.
We should make this dynamic by scanning the target Dockerfile at runtime to detect the Alpine version and PHP package prefix, then query Repology to resolve
the right php*-pecl-memcache package/version before writing the component block.
We still need Renovate to keep ARG PHP_MEMCACHE_VERSION current in this repo, so the implementation should preserve a Renovate-managed default/fallback
while avoiding hard-coded assumptions when applying the component to a target stack.
cmd/assets/memcached.Dockerfile.txt currently hard-codes the Renovate datasource and package target to alpine_3_22/php83-pecl-memcache:
That assumes both Alpine 3.22 and PHP 8.3. The target Drupal Dockerfile may use a different Alpine release and PHP package family, such as php83, php84, or
php85.
We should make this dynamic by scanning the target Dockerfile at runtime to detect the Alpine version and PHP package prefix, then query Repology to resolve
the right php*-pecl-memcache package/version before writing the component block.
We still need Renovate to keep ARG PHP_MEMCACHE_VERSION current in this repo, so the implementation should preserve a Renovate-managed default/fallback
while avoiding hard-coded assumptions when applying the component to a target stack.