Bump lxml from 5.3.0 to 5.4.0
Bumps lxml from 5.3.0 to 5.4.0.
Release notes
Sourced from lxml's releases.
lxml-5.4.0
5.4.0 (2025-04-22)
Bugs fixed
- LP#2107279: Binary wheels use libxml2 2.13.8 and libxslt 1.1.43 to resolve several CVEs. (Binary wheels for Windows continue to use a patched libxml2 2.11.9 and libxslt 1.1.39.) Issue found by Anatoly Katyushin, see https://bugs.launchpad.net/lxml/+bug/2107279
lxml-5.3.2
No release notes provided.
lxml-5.3.1
No release notes provided.
Changelog
Sourced from lxml's changelog.
5.4.0 (2025-04-22)
Bugs fixed
- LP#2107279: Binary wheels use libxml2 2.13.8 and libxslt 1.1.43 to resolve several CVEs. (Binary wheels for Windows continue to use a patched libxml2 2.11.9 and libxslt 1.1.39.) Issue found by Anatoly Katyushin.
5.3.2 (2025-04-05)
This release resolves CVE-2025-24928 as described in https://gitlab.gnome.org/GNOME/libxml2/-/issues/847
Bugs fixed
Binary wheels use libxml2 2.12.10 and libxslt 1.1.42.
Binary wheels for Windows use a patched libxml2 2.11.9 and libxslt 1.1.39.
5.3.1 (2025-02-09)
Bugs fixed
GH#440: Some tests were adapted for libxml2 2.14.0. Patch by Nick Wellnhofer.
LP#2097175:
DTD(external_id="…")erroneously required a byte string as ID value.GH#450:
iterparse()internally triggered the `DeprecationWarning`` added in lxml 5.3.0 when parsing HTML.Other changes
- GH#442: Binary wheels for macOS no longer use the linker flag
-flat_namespace.
Commits
6e76d57Build: Exclude slow Py3.9 wheel builds for s390/ppc and Py3.7 for ARM64.ee10c02Prepare release of lxml 5.4.0.0e4f3c3Prepare release of lxml 5.3.3.b4703fcUpdate changelog.db723bbBuild: Use libxslt 1.1.43 instead of 1.1.42 to resolve some CVEs.a664877Build: Use libxml2 2.13.8 instead of 2.12.x to resolve some CVEs.df4633eRemove appveyor usage.820db89CI: Allow Py3.14 jobs to fail.93ad02adocs: Add a note about C compiler installation to error message (GH-454)16878daAdd some hints to the documentation on how to build lxml (GH-453)- Additional commits viewable in compare view
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)