Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency django-jinja to ~2.10.2 #1913

Merged
merged 1 commit into from
Jun 17, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 17, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
django-jinja ~2.10.0 -> ~2.10.2 age adoption passing confidence

Release Notes

niwinz/django-jinja

v2.10.2

Compare Source

Released May 12th, 2022

  • Fix compatibility with Jinja2 3.1 in tests (#​296).

v2.10.1

Compare Source

Released May 12th, 2022

  • Update links in documentation to point to new home of Jinja2 docs (#​295).

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/django-jinja-2.x branch from 11e7928 to 35aa42e Compare June 17, 2022 21:33
@renovate renovate bot force-pushed the renovate/django-jinja-2.x branch from 35aa42e to ae9848b Compare June 17, 2022 23:11
@bryanculver bryanculver merged commit d4f5299 into next Jun 17, 2022
@renovate renovate bot deleted the renovate/django-jinja-2.x branch June 18, 2022 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant