Maintenance: review zod update

[dreamorosi]

Summary

In #4206 Zod is being updated from 4.0.5 to 4.0.8 - something seem to have changed in how errors are formatted/generated which breaks our unit tests.

Why is this needed?

So that we can ensure compatibility with the Parser utility.

Which area does this relate to?

No response

Solution

We should look into the change and understand if it's a regression on Zod's side or if it's due to our test case being too brittle.

If it's the former, we might want to open an issue upstream. If it's the latter, we can update our tests and upgrade safely - use your best judgement here.

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[dreamorosi]

@sdangol can you please take a look at this tomorrow? There's a Dependabot PR that and its CI is failing.

We know our customers are staying on top of Zod's updates, so it'd be good if we can have an answer to understand if our Parser is still compatible with the latest versions.

[sdangol]

@dreamorosi In Zod 4.0.7, they changed the behavior to not continue to parsing if something fails. In the failing test, the base64 that is passed in not a base64 encoded string so, it doesn't get to the transform part where we throw the custom error.
I think it'd be better to update our tests in this case. I'll create a PR for it

[dreamorosi]

Sounds good, thank you for diving into it. Good change on their part.

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.