Corresponding source code and third-party notices for PySide6-WebEngine / Pdf 6.12.0.140 Windows wheels

PlasticLivesLab

Hello,

We are preparing to distribute a commercial Windows application that includes the official PySide6-WebEngine 6.12.0.140 and PySide6-Pdf 6.12.0.140 wheels.

We intend to comply with the applicable open-source licenses, including LGPL requirements, and provide the necessary corresponding source code and third-party license notices to our users.

However, we have been unable to identify the exact corresponding source release and complete third-party attribution materials for these particular wheel builds.

Packages (SHA256):

PySide6-WebEngine 6.12.0.140:
f9b61b1d457a591ee590a6b80515f25a3e61e2576a2a0a70566380f9d9de4ab0
PySide6-Pdf 6.12.0.140:
4971ba1a0ca15e7c29cfd808e9600aeb46b2305dad01456eb09fa3197166268e

The Qt WebEngine binary reports:

Qt WebEngine: 6.140.0
Chromium: 140.0.7339.225
Security patch level: 152.0.7977.83

We found the publicly available v6.140.0-rc source, but could not establish whether it corresponds exactly to these wheel binaries. In particular, its top-level Chromium version descriptor refers to 140.0.7339.264.

Could you please clarify the following?

Which source archive, tag, or commit corresponds to each of these Windows wheel builds, including relevant patches and build scripts?
Where can we obtain the corresponding Chromium/PDFium source and complete third-party LICENSE, NOTICE, and attribution materials? In particular, are the generated chromium_attributions.qdoc and pdf_attributions.qdoc, or equivalent files, available for these builds?
Does the published v6.140.0-rc source correspond to the official 6.12.0.140 wheel binaries, or is there another appropriate source revision?

We are not requesting a fully reproducible build or complete compiler provenance. We only want to identify the correct materials needed to fulfill the applicable open-source redistribution obligations.

If another Qt channel would be more appropriate for this question, please let us know.

Thank you for your assistance!

SGaist

Hi and welcome to devnet,

I think @friedemannkleint might be able to answer this one.

JKSH

I don't know the exact tag/commit that was used for this release, but this is what I know:

Qt WebEngine (and Qt PDF) have been split from Qt, with an independent release cycle: https://www.qt.io/blog/qt-webengine-will-release-separate
Qt WebEngine/PDF 6.140.0 has not been released yet
Qt for Python has not performed the same split yet; Qt for Python 6.12.0 inadvertently shipped with a pre-release version of Qt WebEngine/PDF

I believe this should be rectified soon