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:
- deploy_requirements.txt
#### Vulnerabilities that will be fixed
##### By pinning:
Severity | Issue | Upgrade | Breaking Change | Exploit Maturity
:-------------------------:|:-------------------------|:-------------------------|:-------------------------|:-------------------------
 | Cross-site Scripting (XSS) [SNYK-PYTHON-JINJA2-6150717](https://snyk.io/vuln/SNYK-PYTHON-JINJA2-6150717) | `jinja2:` `2.11.3 -> 3.1.3` | No | No Known Exploit
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](https://app.snyk.io/org/pcic-devops/project/6c07beff-1b59-463b-9f79-6fe458e23d7e?utm_source=github&utm_medium=referral&page=fix-pr)
🛠 [Adjust project settings](https://app.snyk.io/org/pcic-devops/project/6c07beff-1b59-463b-9f79-6fe458e23d7e?utm_source=github&utm_medium=referral&page=fix-pr/settings)
📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities)
[//]: # (snyk:metadata:{"prId":"5779b4df-b0a1-497b-a5a5-ac33ae46d864","prPublicId":"5779b4df-b0a1-497b-a5a5-ac33ae46d864","dependencies":[{"name":"jinja2","from":"2.11.3","to":"3.1.3"}],"packageManager":"pip","projectPublicId":"6c07beff-1b59-463b-9f79-6fe458e23d7e","projectUrl":"https://app.snyk.io/org/pcic-devops/project/6c07beff-1b59-463b-9f79-6fe458e23d7e?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-PYTHON-JINJA2-6150717"],"upgrade":[],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title"],"priorityScoreList":[null],"remediationStrategy":"vuln"})
---
**Learn how to fix vulnerabilities with free interactive lessons:**
🦉 [Cross-site Scripting (XSS)](https://learn.snyk.io/lesson/xss/?loc=fix-pr)
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: - deploy_requirements.txt #### Vulnerabilities that will be fixed ##### By pinning: Severity | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|:-------------------------|:-------------------------|:-------------------------|:-------------------------  | Cross-site Scripting (XSS)[SNYK-PYTHON-JINJA2-6150717](https://snyk.io/vuln/SNYK-PYTHON-JINJA2-6150717) | `jinja2:`
`2.11.3 -> 3.1.3`
| No | No Known Exploit 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: