summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Bruhin <me@the-compiler.org>2020-06-25 18:05:37 +0200
committerFlorian Bruhin <me@the-compiler.org>2020-06-25 18:05:37 +0200
commitc37093ed258051565620297941b31f2ff50ad8dd (patch)
tree5b6282ebbc7a6469001ab584ad095486a4e098c2
parent66e19b1e0c5f8201586b94a680bfa820179c0510 (diff)
downloadqutebrowser-c37093ed258051565620297941b31f2ff50ad8dd.tar.gz
qutebrowser-c37093ed258051565620297941b31f2ff50ad8dd.zip
Update version in session warning
-rw-r--r--qutebrowser/html/warning-sessions.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/qutebrowser/html/warning-sessions.html b/qutebrowser/html/warning-sessions.html
index 0c6622df6..fadc9908d 100644
--- a/qutebrowser/html/warning-sessions.html
+++ b/qutebrowser/html/warning-sessions.html
@@ -9,7 +9,7 @@ qute://warning/sessions</span> to show it again at a later time.</span>
<p>Since Qt doesn't provide an API to load the history of a tab, qutebrowser relies on a reverse-engineered binary serialization format to load tab history from session files. With Qt 5.15, unfortunately that format changed (due to the underlying Chromium upgrade), in a way which makes it impossible for qutebrowser to load tab history from existing session data.</p>
-<p>At the time of writing (April 2020), a new session format which stores part of the needed binary data in saved sessions is <a href="https://github.com/qutebrowser/qutebrowser/issues/5359">in development</a> and is expected to be released with qutebrowser v1.13.0.</p>
+<p>At the time of writing (April 2020), a new session format which stores part of the needed binary data in saved sessions is <a href="https://github.com/qutebrowser/qutebrowser/issues/5359">in development</a> and is expected to be released with qutebrowser v1.14.0.</p>
<p>As a stop-gap measure:</p>