From 3ed8fceee315ce3efd3b7308fa0fff4a37b22d45 Mon Sep 17 00:00:00 2001 From: Arne Franken Date: Fri, 11 Sep 2026 14:05:57 +0200 Subject: [PATCH] Prepare changelog for 5.2.2 --- CHANGELOG.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2aea6bbad..1fcbdf1a6 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,6 +9,8 @@ Whenever a 3rd party library is updated, S3Mock will update its MINOR version. * [Planned changes](#planned-changes) * [CURRENT - 5.x - THIS VERSION IS UNDER ACTIVE DEVELOPMENT](#current---5x---this-version-is-under-active-development) * [5.3.0 - PLANNED](#530---planned) + * [5.2.2](#522) + * [5.2.1](#521) * [5.2.0](#520) * [5.1.0](#510) * [5.0.0](#500) @@ -159,7 +161,7 @@ Version 5.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Jav * Version updates (build dependencies) * TBD -## 5.2.1 +## 5.2.2 * Features and fixes * fix: Restore the ability to persist data to a mounted Docker volume. Since the migration to the Cloud Native Buildpacks OCI image (which runs as the non-root `cnb` user), a mounted named volume was no longer writable. The image now pre-creates a `cnb`-owned `/s3mockroot` directory, so a Docker named volume mounted at `/s3mockroot` (with `COM_ADOBE_TESTING_S3MOCK_STORE_ROOT=/s3mockroot`) is writable without running the container as root. S3Mock now also fails fast with a clear message when the configured store root is not writable, creates nested store-root paths (not just a single missing directory), and `S3MockContainer.withNamedVolume(...)` plus a container restart persistence test were added. The image also restores `/` (rather than the Buildpacks default `/workspace`) as its working directory, so a *relative* `COM_ADOBE_TESTING_S3MOCK_STORE_ROOT` resolves exactly as it did before 5.2 instead of silently resolving under `/workspace` and missing the mounted volume; the resolved absolute root folder is now always logged at startup alongside the configured value. ([#3139](https://github.com/adobe/S3Mock/issues/3139)) @@ -171,6 +173,10 @@ Version 5.x is JDK17 LTS bytecode compatible, with Docker and JUnit / direct Jav * Bump docker/setup-qemu-action from 4.2.0 to 4.3.0 * Bump step-security/harden-runner from 2.21.0 to 2.21.1 +## 5.2.1 + +Release of Java modules failed, please use 5.2.2 + ## 5.2.0 * Features and fixes