<link href="/assets/9600c281ef06d8d7784a4ad6595c8740.css" type="text/css" rel="stylesheet">

Upcoming wallabag version 3.0.0 & 2.6.0

MONTHS_OF_THE_YEAR[11] 22, 2022

<p>Hello everyone,</p> <p>The latest version of wallabag is using <a href="https://symfony.com/releases/3.4">Symfony v3.4.49</a> which hasn't been maintained since November 2020 and without security fixes since November 2021.</p> <p><a href="https://github.com/yguedidi">@yguedidi</a> started to work on migrating/updating some parts of wallabag to remove deprecations, update services and many other changes in the code base in order to be able to upgrade Symfony.<br /> Right now, the master of wallabag is running on Symfony v4.4.49 and we'll soon upgrade to Symfony 5.</p> <p>While moving to Symfony 5 we also wanted to raise the minimum PHP version from 7.4 to 8.0.</p> <p>We are now working on moving to <a href="https://github.com/symfony/flex">Symfony Flex</a> which "<em>is so convenient and improves your productivity so much that it's strongly recommended</em>". The main change of Symfony Flex is the directory structure.<br /> It changes completely from the previous directory structure we are currently using:</p> <ul> <li>assets moved in a different directory</li> <li>config files are exploded by packages</li> <li>parameters are now defined in an environment file</li> <li>there are no bundles anymore (we were using AnnotationBundle, ApiBundle, CoreBundle, ImportBundle &amp; UserBundle)</li> <li>templates are now in a single place, like translations &amp; migrations</li> <li>etc.</li> </ul> <p>We were planning to push all these upgrades (Flex &amp; Symfony 5 &amp; PHP 8) to the version 2.6.0.<br /> But the more we are working on that technical upgrade the more we think it will be a complex upgrade for people running a wallabag instance mostly because of the directory structure change.</p> <h3>3.0.0</h3> <p>That's why we decided to put all these technical upgrades into a new breaking change version: <strong>3.0.0</strong>.</p> <ul> <li>For people using wallabag as a service (like those who have a subscription plan on <a href="https://www.wallabag.it/en">https://www.wallabag.it/en</a> (thanks you 🫶)), they won't notice a single change. There won't be functional change on how they use wallabag.</li> <li>For people hosting wallabag, it'll be an upgrade more significant than just running <code>make update</code>.</li> </ul> <p>We would like to put these technical changes into 3.0.0:</p> <ul> <li>Symfony 6</li> <li>PHP 8.1 or higher</li> <li>new directory structure</li> </ul> <p>Of course, we will recommend to everyone to upgrade to 3.0.0 as soon as the version is released but we'll also have a 2.x branch where we might still provide some bug fix for people who don't want to upgrade right now. But keep in mind that as soon as the 3.0 will be released, we'll be more focused on that version than on the older one.</p> <p>Some features planned for 3.0 will be postponed to 4.0 others will be for 3.1.0.</p> <h3>2.6.0</h3> <p>In the coming days (or maybe weeks) we'll release the 2.6.0 which will upgrade Symfony from 3.4 to 4.4.<br /> It'll resolve a lot of bugs for people running wallabag on PHP 8 for example.<br /> The required PHP version will stay the same as before: 7.4 or higher.</p> <p>You can discuss with use about this blog post here: <a href="https://github.com/wallabag/wallabag/discussions/6177">https://github.com/wallabag/wallabag/discussions/6177</a></p>
With wallabag, archive the web freely. wallabag is a self hostable application for saving web pages.
<script src="/system/assets/jquery/jquery-2.x.min.js"></script> <script src="/user/themes/boxify/js/main.js"></script> <script src="https://sidecar.gitter.im/dist/sidecar.v1.js" defer></script> <script src="/user/plugins/highlight/js/highlight.pack.js"></script> <script src="/user/themes/boxify/js/jquery.jscroll.min.js"></script> <script defer> ((window.gitter = {}).chat = {}).options = { room: 'wallabag/wallabag' }; </script> <script> hljs.initHighlightingOnLoad(); </script>