Answer: The latest version of lxml is 6.1.3, released on 2026-09-02.
Status: Confirmed
Entry: version/lxml
Revision: 1
Digest: sha256:0d46b655a30002ea (changes whenever the content changes)

Timeline:
  Created: 2026-11-12T11:23:43Z
  Last changed: 2026-11-12T11:23:43Z
  Last verified: 2026-11-12T11:33:55Z
  Next check: 2026-11-13T11:33:55Z
  Check interval: Daily
  Expected change: New releases are published at no fixed schedule.

Data:
  Field | Value | Source | As of
  Latest version | 6.1.3 | [1] | 2026-11-12
  Released | Wed, 02 Sep 2026 14:46:05 GMT | [1] | 2026-11-12

Sources:
  [1] PyPI (lxml). "lxml: release information". https://pypi.org/rss/project/lxml/releases.xml
      Role: primary. Accessed: 2026-11-12T11:33:55Z
      Quote: "<title>6.1.3</title>" (Supports: Latest version)
      Quote: "ption>Powerful and Pythonic XML processing library combining libxml2/libxslt with the ElementTree API.</description>
<author>lxml@lxml.de</author>      <pubDate>Wed, 02 Sep 2026 14:46:05 GMT</pubDate>" (Supports: Released)
      Snapshot SHA-256: 497ffce178ae791066f9eebbc2380f7228f9c9e7a6c40b7f53fab0bc43c922d9 (captured 2026-11-12T11:23:43Z)

Verification:
  Method: Read by code directly from the structured data published at [1]; no language model was involved. Every value appears verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-12T11:23:43Z, so the values verified then were kept.
  Cross-check: not-available at 2026-11-12T11:33:55Z. No independent second source is configured for this entry
  Last successful check: 2026-11-12T11:33:55Z
  Last attempt: 2026-11-12T11:33:55Z

Notes and limitations:
  "Latest version" is the newest stable version in the registry; pre-releases are excluded.

Change log:
  Time | Event | Change | Source
  2026-11-12T11:23:43Z | added | Entry created | —
  Changes for this entry as a feed: https://latestn.com/version/lxml/latest

Challenge this entry:
  Open challenges: None
  How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so.
  Form: https://latestn.com/dispute/version/lxml
  POST: https://latestn.com/dispute/version/lxml with claim, evidence_url, and optionally field and contact (form-encoded or JSON)
  GET: https://latestn.com/dispute/version/lxml?claim={what is wrong}&evidence_url={link}

How to cite:
    latestN. (2026). What is the latest version of lxml? Revision 1, last verified 2026-11-12T11:33:55Z. https://latestn.com/version/lxml (accessed 2026-11-12T12:50:34Z).

    @misc{latestN_version_lxml_r1,
      title        = {What is the latest version of lxml?},
      author       = {{latestN}},
      year         = {2026},
      howpublished = {\url{https://latestn.com/version/lxml}},
      note         = {Revision 1; digest sha256:0d46b655a30002ea; last verified 2026-11-12T11:33:55Z; accessed 2026-11-12T12:50:34Z}
    }

URL: https://latestn.com/version/lxml