github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[PR #17947] [MERGED] build(deps): bump markdown from 3.8.2 to 3.9 in /backend #47663

New Issue
Closed
opened 2026-04-29 23:00:18 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-29 23:00:18 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/17947
Author: @dependabot[bot]
Created: 10/1/2025
Status: ✅ Merged
Merged: 10/1/2025
Merged by: @tjbck

Base: dev ← Head: dependabot/pip/backend/dev/markdown-3.9

📝 Commits (1)

  • 17af981 build(deps): bump markdown from 3.8.2 to 3.9 in /backend

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 backend/requirements.txt (+1 -1)

📄 Description

Bumps markdown from 3.8.2 to 3.9.

Release notes

Sourced from markdown's releases.

Release 3.9.0

Changed

  • Footnotes are now ordered by the occurrence of their references in the document. A new configuration option for the footnotes extension, USE_DEFINITION_ORDER, has been added to support restoring the previous behavior of ordering footnotes by the occurrence of definitions (#1367).

Fixed

  • Ensure inline processing iterates through elements in document order (#1546).
  • Fix handling of incomplete HTML tags in code spans in Python 3.14 (#1547).
Changelog

Sourced from markdown's changelog.

title: Changelog toc_depth: 2

Python-Markdown Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to the Python Version Specification. See the Contributing Guide for details.

[Unreleased]

Fixed

  • Fix an HTML comment parsing case in some Python versions that can cause an infinite loop (#1554).

[3.9.0] - 2025-09-04

Changed

  • Footnotes are now ordered by the occurrence of their references in the document. A new configuration option for the footnotes extension, USE_DEFINITION_ORDER, has been added to support restoring the previous behavior of ordering footnotes by the occurrence of definitions (#1367).

Fixed

  • Ensure inline processing iterates through elements in document order (#1546).
  • Fix handling of incomplete HTML tags in code spans in Python 3.14 (#1547).
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/17947 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 10/1/2025 **Status:** ✅ Merged **Merged:** 10/1/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `dependabot/pip/backend/dev/markdown-3.9` --- ### 📝 Commits (1) - [`17af981`](https://github.com/open-webui/open-webui/commit/17af98126a76fc71015cbaf531ca1edeff920c50) build(deps): bump markdown from 3.8.2 to 3.9 in /backend ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `backend/requirements.txt` (+1 -1) </details> ### 📄 Description Bumps [markdown](https://github.com/Python-Markdown/markdown) from 3.8.2 to 3.9. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Python-Markdown/markdown/releases">markdown's releases</a>.</em></p> <blockquote> <h2>Release 3.9.0</h2> <h3>Changed</h3> <ul> <li>Footnotes are now ordered by the occurrence of their references in the document. A new configuration option for the footnotes extension, <code>USE_DEFINITION_ORDER</code>, has been added to support restoring the previous behavior of ordering footnotes by the occurrence of definitions (<a href="https://redirect.github.com/Python-Markdown/markdown/issues/1367">#1367</a>).</li> </ul> <h3>Fixed</h3> <ul> <li>Ensure inline processing iterates through elements in document order (<a href="https://redirect.github.com/Python-Markdown/markdown/issues/1546">#1546</a>).</li> <li>Fix handling of incomplete HTML tags in code spans in Python 3.14 (<a href="https://redirect.github.com/Python-Markdown/markdown/issues/1547">#1547</a>).</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Python-Markdown/markdown/blob/master/docs/changelog.md">markdown's changelog</a>.</em></p> <blockquote> <p>title: Changelog toc_depth: 2</p> <h1>Python-Markdown Changelog</h1> <p>All notable changes to this project will be documented in this file.</p> <p>The format is based on <a href="https://keepachangelog.com/en/1.1.0/">Keep a Changelog</a>, and this project adheres to the <a href="https://packaging.python.org/en/latest/specifications/version-specifiers/">Python Version Specification</a>. See the <a href="https://github.com/Python-Markdown/markdown/blob/master/docs/contributing.md">Contributing Guide</a> for details.</p> <h2>[Unreleased]</h2> <h3>Fixed</h3> <ul> <li>Fix an HTML comment parsing case in some Python versions that can cause an infinite loop (<a href="https://redirect.github.com/Python-Markdown/markdown/issues/1554">#1554</a>).</li> </ul> <h2>[3.9.0] - 2025-09-04</h2> <h3>Changed</h3> <ul> <li>Footnotes are now ordered by the occurrence of their references in the document. A new configuration option for the footnotes extension, <code>USE_DEFINITION_ORDER</code>, has been added to support restoring the previous behavior of ordering footnotes by the occurrence of definitions (<a href="https://redirect.github.com/Python-Markdown/markdown/issues/1367">#1367</a>).</li> </ul> <h3>Fixed</h3> <ul> <li>Ensure inline processing iterates through elements in document order (<a href="https://redirect.github.com/Python-Markdown/markdown/issues/1546">#1546</a>).</li> <li>Fix handling of incomplete HTML tags in code spans in Python 3.14 (<a href="https://redirect.github.com/Python-Markdown/markdown/issues/1547">#1547</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Python-Markdown/markdown/commit/f39cf84a24124526c1a0efbe52219fa9950774f6"><code>f39cf84</code></a> Bump version to 3.9</li> <li><a href="https://github.com/Python-Markdown/markdown/commit/07bf2076623be5de9952e1f35bfb8c218b699300"><code>07bf207</code></a> Order footnotes by reference</li> <li><a href="https://github.com/Python-Markdown/markdown/commit/23c301de28e12426408656efdfa153b11d4ff558"><code>23c301d</code></a> Fix failing cases for Python 3.14</li> <li><a href="https://github.com/Python-Markdown/markdown/commit/4669a09894d4a35cd5f5d2106b0da95e48d1a3f9"><code>4669a09</code></a> fix typo</li> <li>See full diff in <a href="https://github.com/Python-Markdown/markdown/compare/3.8.2...3.9.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=markdown&package-manager=pip&previous-version=3.8.2&new-version=3.9)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-29 23:00:18 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#47663
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?