5.5.2-1
Release in edge and testing channel updates on 1st May 2026.
*Leap 16.0 & Leap 15.6 (multi-arch) & *Tumbleweed/Slowroll (aarch/x86_64).
2nd Stable Release Candidate (RC2)
We have our next installment in the RC move towards Stable. I’ll keep this brief as there has, frankly, been little feedback on the last testing release and its associated announcement for that matter. A big change that has likely been missed by some of our visitors here.
In this release we have, due to over a years preparation, now enabled Poetry managed standalone Python - and at the same time moved all, including the now EOL leap 15.6 target, over to using Python 3.13 to run our code - something that was not packaged at-all in Leap 15.6 - a severe constraint in our ability to enable this update. As such we conditionally still use Py3.11 to host our Poetry only on Leap 15.6, but now use the OS Py3.13 as Poetry host on all other build targets.
Speaking of build-targets, did you notice the Leap 16.0 reference above. We are experimenting with this OS as a future platform but due to having only just incorporated it we have little community feedback on capability as-yet. The name is shared with Leap 15.0 - 15.6, our entire openSUSE history there, but it is quite different in a number of ways. It is, for us, a little closer to Slowroll/Tumbleweed than it is to 15.6 - which was a long running variant to give the upstream folks time to assemble this much newer variant. Our capabilities on this OS are likely more akin to those on SR/TW so keep that in mind when testing - contributing fixes. Also note that we have yet to incorporate our own SELinux policy - something we would welcome assistance with, if you have working knowledge in that area. I would prefer a hand-crafted / though-out policy to one auto created without care however.
As always thanks to all here on the forum who have tried to help with our development, and of course to the core team of @Flox & @Hooverdan both of which have, as usual, contributed to this release - which is actually 2 releases as I forgot to bump the version number at the last minute and we are still tied to GitHub in this regard - more on that to come
.
Also note that, while moving to the newer Poetry and having it manage our now standalone python, we have also added robustness to how we install/update our Poetry. I.e. we now uninstall Poetry and reinstall on each rpm update. This allows for smoother upgrades and host venv arrangements managed by pipx in this case. As it was found that prior installs were gathering ‘dust’ of sorts - and as a result could not support the standalone python move.
5.5.2-0 (no rpm)
What’s Changed
- Update Django Rest Framework plus incidentals #3095 by @phillxnet @FroggyFlox in #3109
- build.sh errors - standalone use #3107 by @phillxnet @Hooverdan96 in #3110
- Upgrade to latest stable Poetry #3112 by @phillxnet in #3113
- Fix remaining utc treatment #3111 by @Hooverdan96 in #3115
- Use Poetry managed standalone python #3081 by @phillxnet @FroggyFlox in #3119
5.5.2-1 (rpm)
What’s Changed
- Bump version to a 5.5.2 base - release 1 #3120 by @phillxnet in #3122
Test away and report rapidly as we work against the forces of kipple.