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

chore(deps): update dependency mistune to v2 #337

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 6, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mistune <2.0 -> ==2.0.2 age adoption passing confidence

Release Notes

lepture/mistune

v2.0.2

Compare Source

Fix escape_url via https://github.com/lepture/mistune/pull/295

v2.0.1

Compare Source

Fix XSS for image link syntax.

v2.0.0

Compare Source

First release of Mistune v2.


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.

@osfrickler
Copy link
Member

Dropping that dep instead, see #376

@osfrickler osfrickler closed this Jun 24, 2022
@osfrickler osfrickler deleted the renovate/mistune-2.x branch June 24, 2022 11:32
@renovate
Copy link
Contributor Author

renovate bot commented Jun 24, 2022

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 2.x releases. However, if you upgrade to 2.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

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.

2 participants