Update fragment image versions and docs

[github-actions]

The scheduled job has detected updated Docker image tags. Please update stale image versions across all fragments.

Instructions

Do NOT use web search for version lookups. Use the MCP tools below instead.

Step 1: Find fragments to update

Check each .json file in fragments/compose/ and note the current image tag in the variables field (e.g. POSTGRES_VERSION, REDIS_TAG).

Step 2: Look up the best tag using Docker Hub MCP

For each image, call the Docker Hub MCP tool list_repository_tags to identify the best tag using this priority order:

• Prefer major-version tags with the image variant suffix (e.g. 4-management-alpine, 16-alpine).
• Fall back to minor-version only if no major-version tag exists for the variant (e.g. 16.3).
• Only use full semver (e.g. 4.2.5-management-alpine) as a last resort.
• Never use latest, edge, nightly, beta, or rc.

list_repository_tags({ namespace: "library", repository: "postgres" })

Use check_repository_tag to verify the chosen tag exists before updating.

Step 3: Look up documentation using Context7 MCP (optional)

If you need to understand configuration options for a service, use Context7 MCP:

resolve-library-id({ libraryName: "postgres" })
query-docs({ context7CompatibleLibraryId: "..." })

Step 4: Update the files

• Update the tag value in the fragment .json file
• Update any hardcoded tag references in the corresponding .yml file
• Update the docs/fragments/<name>.md frontmatter if it has a version field

Step 5: Run validation

npm run validate

Step 6: Submit a pull request with all changes.