Currently, WBS Docker images are rebuilt and released based on changes within our own components or MediaWiki releases. However, these images rely on base images (such as Debian or PHP) that receive regular updates—often for security or stability.

This task involves evaluating the feasibility and desirability of automatically triggering WBS image rebuilds and releases when their upstream base images are updated.

Key considerations include:

• By what mechanism do we detect when a relevant base image (e.g., php:8.1-fpm, debian:bullseye) is updated?
• Assessing how often these updates occur and whether they justify automated downstream rebuilds.
  • Ensuring that such rebuilds are safe, testable, and do not introduce regressions.
  • Avoiding unnecessary noise or churn in releases.

etc.

Definition of Done:

• A recommendation as to whether or not we should or shouldn't be making WBS image releases based purely on upstream image updates (beyond MediaWiki which we already do).
• If so, a recommendation of how often (e.g. weekly, monthly, etc), and/or if they should be triggered by upstream updates
• If further analysis or work is identified, the relevant work is defined and documented in Phabricator tickets

The scope of these recommendations don't need to be for "all time", but for a suggestion scope for the next 6 months to 1 year.