[Snyk] Security upgrade jinja2 from 3.1.3 to 3.1.4

[Sackstools]

User description

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • docs/_klipper3d/mkdocs-requirements.txt

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	556/1000 Why? Recently disclosed, Has a fix available, CVSS 5.4	Cross-site Scripting (XSS) SNYK-PYTHON-JINJA2-6809379	jinja2: 3.1.3 -> 3.1.4	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

---

PR Type

enhancement

---

Description

• This PR updates the jinja2 package from version 3.1.3 to 3.1.4 in the mkdocs-requirements.txt to fix a known security vulnerability (Cross-site Scripting (XSS)).
• The update addresses the vulnerability identified by Snyk with ID SNYK-PYTHON-JINJA2-6809379.

---

Changes walkthrough 📝

	Relevant files
Dependencies	mkdocs-requirements.txt Update Jinja2 to Fix Security Vulnerability                            docs/_klipper3d/mkdocs-requirements.txt Updated jinja2 from version 3.1.3 to 3.1.4 to address a security vulnerability. +1/-1

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Description updated to latest commit (fe11eff)

• Copy walkthrough table to "Files Changed" Tab

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Review 🔍

⏱️ Estimated effort to review [1-5]	1, because the PR involves a simple version bump in a requirements file, which is straightforward and typically does not require extensive review.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Code Suggestions ✨

Category

Suggestions

Best practice

Use a compatible release version specifier for jinja2 to automatically include non-breaking updates. Consider using a more flexible version specification for jinja2 to automatically incorporate non-breaking updates. Instead of pinning to a specific patch version, you can specify a minimum version with a compatible release clause. docs/_klipper3d/mkdocs-requirements.txt [2] -jinja2==3.1.4 +jinja2~=3.1.4