[Snyk] Upgrade @huggingface/jinja from 0.1.3 to 0.5.1

[sestinj]

Snyk has created this PR to upgrade @huggingface/jinja from 0.1.3 to 0.5.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 12 versions ahead of your current version.

• The recommended version was released 3 months ago.

Release notes

Package name: @huggingface/jinja

• 0.5.1 - 2025-07-10
• 0.5.0 - 2025-05-05
• 0.4.1 - 2025-05-01
• 0.4.0 - 2025-04-29
• 0.3.4 - 2025-04-10
• 0.3.3 - 2025-01-30
• 0.3.2 - 2024-10-30
• 0.3.1 - 2024-09-16
• 0.3.0 - 2024-08-07
• 0.2.2 - 2024-03-15
• 0.2.1 - 2024-03-06
• 0.2.0 - 2024-03-05
• 0.1.3 - 2024-02-15
  

  🔖 @ hugginface/hub v0.1.3

from @huggingface/jinja GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

---

Summary by cubic

Upgraded @huggingface/jinja in core/vendor/modules/@xenova/transformers from 0.1.x to 0.5.1 to stay current and pick up fixes and improvements. Only the package.json dependency was updated; no code changes.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ Continue API authentication failed. Please check your CONTINUE_API_KEY.

---

[cubic-dev-ai]

No issues found across 1 file