fix: correct security vulnerability

[AleJo2995]

Types of changes

• Hot fix (emergency fix and release)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation (change which affects the documentation site)
• Breaking change (fix or feature that would cause existing functionality to change)
• Release (develop -> main)

Quality assurance (all should be covered).

• My code follows the code style of this project.
• Documentation for my change is up to date?
• My PR meets testing requirements.
• All new and existing tests passed.
• All commits are signed-off.

Summary

Key links:

• Sonar coverage

Before you merge

• Ensure it is a 'squash commit' if not a release.
• Ensure CI is currently passing
• Check sonar. If you are working for a fork a maintainer will reach out, if required.

[AleJo2995]

I already tested out the change in the repo that is using trestle and the vulnerability has been resolved successfully

[mrgadgil]

This looks like a major version upgrade. Can you look at the change log to verify nothing breaks for us

[AleJo2995]

To me there's not actually something to be worried about in terms of any breaking changes so far. Here's the link for the 3.1.0 change coming from 3.0.1 version we had https://github.com/pallets/jinja/releases/tag/3.1.0. I don't see anything in particular to be worried about. for 3.1.3 they fix the vuln and that's pretty much it. One good signal of it is that all tests are passing correctly :)

[mrgadgil]

LGTM. Thank you for verifying.