From me at the-compiler.org Wed Jun 22 15:12:30 2022 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 22 Jun 2022 15:12:30 +0200 Subject: [qutebrowser-announce] Better nightly builds on CI, state of Qt 6 support, and steps towards v3 Message-ID: <20220622131230.ofym2u27i2qup7ht@aragog> Hey! Today I've worked on improving the nightly build support on CI, and nightly builds are now finally available as individual files instead of being zipped into one big one. This means it's now easier for people on macOS and Windows to test the latest changes before they are released, by simply going to the latest nightly build and grabbing a macOS/Windows build under "Artifacts": https://github.com/qutebrowser/qutebrowser/actions/workflows/nightly.yml This now also includes builds of the qt6-v2 branch, and I'd really welcome having some more testers there! qutebrowser developers (and some brave[*] users) have been using it as daily driver since a while, and it's generally regarded to be ready to use. If you are on Linux, there's mkvenv.py support, Flatpak builds and an Archlinux AUR package available too, see the issue for all the details: https://github.com/qutebrowser/qutebrowser/issues/7202 Please give it a spin and open a new issue if you run into any trouble! There still is a lot of work to do to actually integrate this into the master branch and getting qutebrowser v3.0.0 out, but most of the remaining work is stuff behind the scenes now - from an user's perspective, the qt6-v2 branch should be pretty much ready. For the next few weeks, my plan is to get back to merging some PRs, and regularily rebase the qt6-v2 branch on master to get them in there as well. I'll also start teaching Python at the university again in September (until February), so the clock is ticking a bit... I'm hoping that I'll still be able to work on qutebrowser and get this all wrapped up on the side though (only teaching two days a week, plus preparation/admin stuff). [*] The English word, not the browser ;) Florian -- me at the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From me at the-compiler.org Wed Jun 22 15:41:24 2022 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 22 Jun 2022 15:41:24 +0200 Subject: [qutebrowser-announce] qutebrowser v2.5.2 released: More regression and notification fixes! Message-ID: <20220622134124.xcx2vnbky2t3sleo@aragog> Hey, I'm happy to announce that I just released qutebrowser 2.5.2! This is another bugfix release full of... duh bugfixes (and hopefully no new bugs this time, like it happened with the notification fixes in 2.5.1 which actually made notifications less stable instead of more...). Then again, this also squashes a bug which have been around since 2018, so, it must be good! Here is the full changelog: - Packaging-related fixes: * The `install` and `stacktrace` help pages are now included in the docs shipped with qutebrowser when using the recommended packaging workflow. * The Windows installer now more consistently uses the configured Windows colors. * The Windows installer now bases the desktop/start menu icon choices on the existing install, if upgrading. * The macOS release hopefully doesn't cause macOS to (falsely) claim that it "is damaged and can't be opened" anymore. - The notification fixes in v2.5.1 caused new notification crashes (probably more common than the ones being fixed...). Those are now fixed, along with a (rather involved) test case to prevent similar issues in the future. - When a text was not found on a page, the associated message would be shown as rich text (e.g. after `/

`). With this release, this is fixed for search messages, while the 3.0.0 release will change the default for all messages to be plain-text. Note this is NOT a security issue, as only a small subset of HTML is interpreted as rich text by Qt, independently from the website. - When a Greasemonkey script couldn't be loaded (e.g. due to an unreadable file), qutebrowser would crash. It now shows an error instead. - Ever since the v1.2.0 release in 2018, the `content.default_encoding` setting was not applied on start properly (only when it was changed afterwards). This is now fixed. Enjoy! Florian -- me at the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: