Re-apply Jackson 2.18.6 upgrade with round-trip test coverage (#599)

* test: 🧪 add roundtrip serialization test utility

* test: fix false positives epoch format errors, added comment about this
in the serialization package.

* test: fixed false positves DateTime differences

* test: fixing error in lex event fixture

* test: fixing connect event

* test: fixing api gateway proxy event false negative

* test: fixing cloudfront and s3 event false negatives

* chore: adding mise to gitignore

* test: fix MSKFirehose, LexEvent, RabbitMQ, APIGatewayV2Auth and ActiveMQ serialization test fixtures

* test: Add round-trip fixtures for 4 registered events

Add JSON test fixtures and round-trip test cases for CognitoEvent,
DynamodbTimeWindowEvent, IoTButtonEvent, and KinesisTimeWindowEvent.
These were the only events registered in LambdaEventSerializers
SUPPORTED_EVENTS that lacked test fixtures.

Fixtures based on official AWS Lambda documentation examples. Time
window event fixtures use round-trip-safe date formats to avoid
coercion issues.

Coverage: 32 passing + 2 known failures (34 total, up from 30).

* test: Add round-trip fixtures for 21 unregistered events

Add UnregisteredEventSerializationRoundTripTest covering events not in
LambdaEventSerializers.SUPPORTED_EVENTS: 10 Cognito UserPool triggers,
5 Kinesis Analytics events, 2 API Gateway V2 WebSocket, 2 AppSync,
1 S3 Batch, and 1 TimeWindow response. S3ObjectLambdaEvent is a known
failure (Lombok xAmzRequestId naming issue).

Split SerializationRoundTripTest into registered (34 tests) and
unregistered (22 tests) for clarity. Total: 56 tests, 53 passing,
3 known failures.

* test: Add round-trip tests for 11 response event types

Add ResponseEventSerializationRoundTripTest covering all 11 response
event types in aws-lambda-java-events. 9 pass cleanly, 2 are known
failures (IamPolicyResponse, IamPolicyResponseV1 — getPolicyDocument()
returns Map<String,Object> instead of the PolicyDocument POJO, making
round-trip impossible by design since these are serialize-only types).

Also update SerializationRoundTripTest comment for
APIGatewayV2CustomAuthorizerEvent to clarify the date format change
is a lossy transformation, not a bug.

Total: 69 tests (34 registered + 22 unregistered + 11 response + 2
LambdaEventAssertTest), all green. Coverage now 66/68 event classes
(97%).

* chore: fixed comment

* test: including IAM Policy Reponse roundtrip test

* test: add test for JsonNodeUtils

* chore: remove unwanted file on origin

* docs: add tests 1.1.2 changelog entry

* chore: remove entry in changelog

* fix: 🔧 updating again jacjson 2.15.4 -> 2.18.6

* fix: fixing an error in github actions that was causing false positive errors when running aws-lambda-java-serialization

* docs: update changelogs

* chore: releasing aws-lambda-tests

* chore: add space

---------

Co-authored-by: Davide Melfi <dmelfi@amazon.com>

Author: darklight3it

.github/workflows/aws-lambda-java-serialization.yml

@@ -40,7 +40,7 @@ jobs:
 
     # Package and install target module
     - name: Package serialization with Maven
-      run: mvn -B package install --file aws-lambda-java-serialization/pom.xml
+      run: mvn -B install --file aws-lambda-java-serialization/pom.xml
 
     # Run tests
     - name: Run tests from aws-lambda-java-tests

aws-lambda-java-serialization/RELEASE.CHANGELOG.md

@@ -1,7 +1,14 @@
+### March 26, 2026
+`1.4.0`:
+- Update `jackson-databind` dependency from 2.15.4 to 2.18.6
+- Replace deprecated `PropertyNamingStrategy.PascalCaseStrategy` with `PropertyNamingStrategies.UpperCamelCaseStrategy`
+- The regression reported in 1.3.1 was a false positive caused by a CI workflow bug (`mvn package install` running the shade plugin twice, corrupting the artifact). Fixed by using `mvn install` instead.
+
 ### March 19, 2026
 `1.3.1`:
 - Revert `jackson-databind` dependency from 2.18.6 to 2.15.4
 - Revert `PropertyNamingStrategies.UpperCamelCaseStrategy` to `PropertyNamingStrategy.PascalCaseStrategy`
+- Note: reverted due to a suspected regression in Joda DateTime deserialization; later confirmed to be a false positive (see 1.4.0)
 
 ### March 11, 2026
 `1.3.0`:

aws-lambda-java-serialization/pom.xml

@@ -4,7 +4,7 @@
 
     <groupId>com.amazonaws</groupId>
     <artifactId>aws-lambda-java-serialization</artifactId>
-    <version>1.3.1</version>
+    <version>1.4.0</version>
     <packaging>jar</packaging>
 
     <name>AWS Lambda Java Runtime Serialization</name>
@@ -32,7 +32,7 @@
         <maven.compiler.source>1.8</maven.compiler.source>
         <maven.compiler.target>1.8</maven.compiler.target>
         <relocation.prefix>com.amazonaws.lambda.thirdparty</relocation.prefix>
-        <jackson.version>2.15.4</jackson.version>
+        <jackson.version>2.18.6</jackson.version>
         <gson.version>2.10.1</gson.version>
         <json.version>20231013</json.version>
         <owasp.version>7.3.2</owasp.version>

aws-lambda-java-serialization/src/main/java/com/amazonaws/services/lambda/runtime/serialization/events/LambdaEventSerializers.java

@@ -1,3 +1,9 @@
+### March 27, 2026
+`1.1.3`:
+- Add serialization round-trip tests covering 66 event classes
+- Bumped `aws-lambda-java-serialization` to version `1.4.0` (Jackson `2.15.x` → `2.18.6`)
+- Bumped `aws-lambda-java-events` to version `3.16.1`
+
 ### August 26, 2021
 `1.1.1`:
 - Bumped `aws-lambda-java-events` to version `3.11.0`

aws-lambda-java-tests/RELEASE.CHANGELOG.md

@@ -5,7 +5,7 @@
 
     <groupId>com.amazonaws</groupId>
     <artifactId>aws-lambda-java-tests</artifactId>
-    <version>1.1.2</version>
+    <version>1.1.3</version>
     <packaging>jar</packaging>
 
     <name>AWS Lambda Java Tests</name>
@@ -40,18 +40,22 @@
         -->
         <junit.version>5.9.2</junit.version>
         <jacoco.maven.plugin.version>0.8.7</jacoco.maven.plugin.version>
+        <aws-lambda-java-serialization.version>1.4.0</aws-lambda-java-serialization.version>
+        <aws-lambda-java-events.version>3.16.1</aws-lambda-java-events.version>
+        <commons-lang3.version>3.18.0</commons-lang3.version>
+        <assertj-core.version>3.27.7</assertj-core.version>
     </properties>
 
     <dependencies>
         <dependency>
             <groupId>com.amazonaws</groupId>
             <artifactId>aws-lambda-java-serialization</artifactId>
-            <version>1.2.0</version>
+            <version>${aws-lambda-java-serialization.version}</version>
         </dependency>
         <dependency>
             <groupId>com.amazonaws</groupId>
             <artifactId>aws-lambda-java-events</artifactId>
-            <version>3.16.1</version>
+            <version>${aws-lambda-java-events.version}</version>
         </dependency>
         <dependency>
             <groupId>org.junit.jupiter</groupId>
@@ -71,13 +75,13 @@
         <dependency>
             <groupId>org.apache.commons</groupId>
             <artifactId>commons-lang3</artifactId>
-            <version>3.18.0</version>
+            <version>${commons-lang3.version}</version>
         </dependency>
 
         <dependency>
             <groupId>org.assertj</groupId>
             <artifactId>assertj-core</artifactId>
-            <version>3.27.7</version>
+            <version>${assertj-core.version}</version>
             <scope>test</scope>
         </dependency>
     </dependencies>

aws-lambda-java-tests/pom.xml

@@ -25,13 +25,8 @@
  * {@link AssertionError}.
  * </p>
  *
- * <p>
- * This class is intentionally package-private to support updates to 
- * the aws-lambda-java-events and aws-lambda-java-serialization packages.
- * Consider making it public if there's a real request for it.
- * </p>
  */
-class LambdaEventAssert {
+public class LambdaEventAssert {
 
     private static final ObjectMapper MAPPER = new ObjectMapper();