diff options
| author | toofar <toofar@spalge.com> | 2024-03-23 11:14:53 +1300 |
|---|---|---|
| committer | toofar <toofar@spalge.com> | 2024-03-23 11:51:35 +1300 |
| commit | 52106c383b41ea7629399f75059bbcba9abb1ba6 (patch) | |
| tree | 4b56c7d5d00a29694a041847c96a11de683f8227 /doc/changelog.asciidoc | |
| parent | 93b8438ebc418d880fb3f0d4eb5ae86df08488dc (diff) | |
| download | qutebrowser-52106c383b41ea7629399f75059bbcba9abb1ba6.tar.gz qutebrowser-52106c383b41ea7629399f75059bbcba9abb1ba6.zip | |
Show chromium security patch version in :versionfeat/7187_chromium_security_patch_in_version
Webengine added a getter for their chromium patch level back in Qt 6.3,
since they backport security fixes from chromium in the periods between
doing major chromium feature upgrades.
It's pulled from a hardcoded string in the webengine source
`src/core/web_engine_context.cpp` that's manually updated when they
backport something.
The "(plus any distribution patches)" bit in there is because it was
pointed out that some distributions backport their own security patches
or even use webengine from a branch when the hardcoded string only gets
updated at release time, despite patches being backported in the
meantime.
Closes: https://github.com/qutebrowser/qutebrowser/issues/7187
Diffstat (limited to 'doc/changelog.asciidoc')
| -rw-r--r-- | doc/changelog.asciidoc | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/changelog.asciidoc b/doc/changelog.asciidoc index 89e33679e..fce509dd7 100644 --- a/doc/changelog.asciidoc +++ b/doc/changelog.asciidoc @@ -24,6 +24,10 @@ Added - When qutebrowser receives a SIGHUP it will now reload any config.py file in use (same as the `:config-source` command does). (#8108) +- The Chromium security patch version is now shown in the backend string in + --version and :version. This reflects the latest Chromium version that + security fixes have been backported to the base QtWebEngine version from. + (#7187) Changed ~~~~~~~ |