summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Bruhin <me@the-compiler.org>2021-01-28 16:11:05 +0100
committerFlorian Bruhin <me@the-compiler.org>2021-01-28 16:11:54 +0100
commitf3db4f21641af5f3924329e0e8b8cd27c50d466d (patch)
tree78e72e61a32c10076534b56d33fedb02155fc9f3
parentbd21ff688d8598905c0ad8fd250f1f54030b7068 (diff)
downloadqutebrowser-f3db4f21641af5f3924329e0e8b8cd27c50d466d.tar.gz
qutebrowser-f3db4f21641af5f3924329e0e8b8cd27c50d466d.zip
Update changelog
-rw-r--r--doc/changelog.asciidoc27
1 files changed, 27 insertions, 0 deletions
diff --git a/doc/changelog.asciidoc b/doc/changelog.asciidoc
index ead1dc330..de818d4b9 100644
--- a/doc/changelog.asciidoc
+++ b/doc/changelog.asciidoc
@@ -15,6 +15,33 @@ breaking changes (such as renamed commands) can happen in minor releases.
// `Fixed` for any bug fixes.
// `Security` to invite users to upgrade in case of vulnerabilities.
+[[v2.0.1]]
+v2.0.1 (unreleased)
+-------------------
+
+Fixed
+~~~~~
+
+- If qutebrowser was installed as a Python egg (similar to a .zip file, via
+ `setup.py install` under certain conditions), a change in v2.0.0 caused it to
+ not start properly. This is now fixed.
+- If qutebrowser was set up (or packaged) in an unclean environment, this could
+ result in a stale `qutebrowser/components/adblock.py` file being picked up. That
+ file is not part of the release anymore, but if an old version is still around,
+ causes qutebrowser to crash. It's now explicitly blocked inside qutebrowser so
+ it gets ignored even if it still exists.
+
+Changed
+~~~~~~~
+
+- The `format_json` userscript now uses sh instead of bash again.
+- The `add-nextcloud-bookmarks`, `add-nextcloud-cookbook`, `readability` and
+ `ripbang` userscripts now use a `python3` rather than plain `python` shebang.
+- When `QTWEBENGINE_CHROMIUM_FLAGS` is set in the environment, this causes flag
+ handling (including workarounds for QtWebEngine crashes) inside qutebrowser to
+ break. This will be handled properly in a future version, but this release now
+ shows a warning on standard output if this is the case.
+
[[v2.0.0]]
v2.0.0 (2021-01-28)
-------------------