[renovate]

This PR contains the following updates:

Package	Type	Update	Change
minijinja	dependencies	patch	3.0.1 → 3.0.3

---

Release Notes

mitsuhiko/minijinja (minijinja)

v3.0.3

Compare Source

• Re-release of 3.0.2 without code changes. The Python package for 3.0.2 could not be published to PyPI because the 32-bit Linux wheel failed to build on the new Ubuntu 26.04 GitHub Actions runners, so 3.0.3 is the first release with the 3.0.2 changes on PyPI. All other packages are identical to 3.0.2.

v3.0.2

Compare Source

• Macros and variables starting with an underscore are now private and are no longer exported from imported templates in Rust and Go, matching Jinja2. They are not visible as attributes of a module imported with {% import %}, and {% from ... import %} of such a name is a syntax error. State::exports / State.Exports no longer return them either, but they can still be retrieved with lookup. #​970
• Fixed modules imported with {% import %} not being iterable in Go.
• Fixed the indent filter indenting blank lines of CRLF text when blank is false, in Rust and Go. A blank line ended up as " \r" instead of "\r", leaving trailing whitespace. #​972
• Fixed the wordwrap filter ignoring break_long_words when break_on_hyphens is false. The two arguments are independent in Jinja2, so a word longer than width is still broken unless break_long_words is false. #​940
• Fixed chained integer lookups like foo.1.0 failing with a syntax error in Rust and Go. Like in Jinja2, a number right after a dot is now always read as an item index, so foo.1.0 is foo[1][0] instead of foo followed by the float 1.0. #​974
• Fixed \x and octal string escapes above \x7f producing invalid UTF-8 in Go. Like in Rust they now produce the code point, so '\xe9' is é. Go now also understands the \b and \f escapes and surrogate pairs written as two \u escapes, and rejects a lone surrogate like Rust does. #​975
• Added the method argument to the round filter for Jinja2 compatibility in Rust and Go. It takes common (the default), ceil or floor, and both precision and method can now be passed as keyword arguments. Integers are now rounded to a negative precision like in Jinja2, so 15|round(-1) is 20 rather than 15. #​968
• Fixed Python exceptions leaking into later renders in the Python bindings. An exception that MiniJinja did not report, for instance one raised by an iterator after a {% break %}, was raised in place of the next unrelated error. Exceptions are now attached to the error that carries them. Exceptions raised by a loader are also no longer treated as missing templates, so they are no longer ignored by ignore missing or skipped by an include with a list of templates. #​967
• The Python package is now also published as free-threaded wheels for Linux, macOS and Windows: a version-specific wheel for CPython 3.14t and an abi3t (PEP 803) wheel for CPython 3.15+. #​969
• The Python package metadata includes the readme again, so the PyPI page shows a project description.

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • "after 9am on friday,before 6pm on friday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-23 13:49 UTC · Rule: dependency-updates · triggered by merge protections
• 🚫 Left the queue — 2026-10-23 13:57 UTC · at 522f1cabfe0864566f183b93723ddc734dc6be09

This pull request spent 8 minutes 4 seconds in the queue, with no time running CI.

Reason

The pull request conflicts with the base branch

The pull request was held in the queue, conflicting with 1 pull request ahead of it. The conflict became a base branch one after #69 merged.

Hint

You should update or rebase your pull request.

If you want to requeue this pull request, you can post a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-23 13:58 UTC · Rule: dependency-updates · triggered by merge protections
• ✅ Checks passed · on draft merge queue: checking #68 on main (946119b) #71
• ✅ Merged — 2026-10-23 14:02 UTC · at e5c9d2d385760b9ef8bae6696b832ad30e6cc3d4 · merge

This pull request spent 3 minutes 52 seconds in the queue, including 1 second running CI.

Required conditions to merge

• #approved-reviews-by >= 1
  • Update Rust crate minijinja to v3.0.3 #68
• github-review-approved [🛡 GitHub repository ruleset rule main]
  • Update Rust crate minijinja to v3.0.3 #68
• any of [🛡 GitHub repository ruleset rule main]:
  • check-success = @github-actions/Test
  • check-neutral = @github-actions/Test
  • check-skipped = @github-actions/Test