Souin is on 1.7.5; upstream released 1.7.8 on 2025-09-18 (patch bump).
Changes to apply
hub/souin/stack.yaml
version: "1.7.5" → version: "1.7.8"
hub/souin/stack.yaml
updated_at: 2024-11-06 → updated_at: 2025-09-18
hub/souin/compose.yaml
${SOUIN_VERSION:-1.7.5} → ${SOUIN_VERSION:-1.7.8}
Container tag v1.7.8 was verified to exist upstream.
Required before merging
A newer release is not evidence that the new version still works with our
compose file, our .env and our volumes. Establish a baseline first, then
prove the bump did not regress it:
# 1. baseline: does it pass today, before any change?
./packages/scripts/maintenance/test-stack.sh souin
# 2. apply the edits above, then:
./packages/scripts/maintenance/test-stack.sh souin
The test pulls every image, waits for all services to become healthy, checks
that nothing crash-loops during a settle window, and makes a real HTTP request
to the app's entry point.
- If the baseline fails too, this app was already broken: fix that first or say
so in the PR — it is not a regression from this bump.
- If the baseline passes and the bump fails, do not merge. Read the release
notes: a required new env var or a migration usually needs .env or
compose.yaml changes alongside the version.
- Attach the test output to the PR.
Filed automatically from work/version-drift.json.
Souin is on
1.7.5; upstream released1.7.8on 2025-09-18 (patch bump).Changes to apply
hub/souin/stack.yamlversion: "1.7.5"→version: "1.7.8"hub/souin/stack.yamlupdated_at: 2024-11-06→updated_at: 2025-09-18hub/souin/compose.yaml${SOUIN_VERSION:-1.7.5}→${SOUIN_VERSION:-1.7.8}Container tag
v1.7.8was verified to exist upstream.Required before merging
A newer release is not evidence that the new version still works with our
compose file, our
.envand our volumes. Establish a baseline first, thenprove the bump did not regress it:
The test pulls every image, waits for all services to become healthy, checks
that nothing crash-loops during a settle window, and makes a real HTTP request
to the app's entry point.
so in the PR — it is not a regression from this bump.
notes: a required new env var or a migration usually needs
.envorcompose.yamlchanges alongside the version.Filed automatically from
work/version-drift.json.