V5.0+ Testing Channel Changelog

5.0.6-0

Released in testing channel updates on 16th January 2024

1st Stable Release Candidate (RC1)

As can be seen by these changes and those preceeding it in our ongoing 5.0.* testing phase: we are in process of updating our base dependencies. And hopefully fixing all that ‘falls’ in the process. This release is marked RC1 as we now need wider testing to begin our push towards a more production/tested release that we can promote as Stable. Our last of which was 4.6.1-0 (after 4.1.0-0 before it), and our next intended Stable release version will be 5.1.0-0, if our plans pan-out.

Overview

We now run on Python 3.11 and Django 4.2 LTS; and have updated all our Python dependencies to their latest versions, as of each updates implementation. This was the primary, and rather ambitious goal of this current testing phase.

There are inevitably regressions, with such fundamental updates, and one particularly gnarly one has been our replication code: this had many Py2.7isms and we paid for this in the delay getting to this release. Thanks to forum member @niko for their reporting on this regression. It is now expected that we have restored our prior stable version replication function with this release. There will inevitably be improvements to be made but initially we needed what we had in our last stable release: at least.

As usual I would like to thank all testers, developers, & reporters, and specifically @Flox and @Hooverdan for their stellar efforts across the project.

Caveats

With this release we have now adoped a proper secrets management system. As such, the default/predefined/special-case cliapp credentials had to be redefined. This will break all existing replication and is unavoidable with our other ongoing update orientated goals. However replication in this testing phase has been broken for some time now. But for those intending to update to this release who rely-on, or are willing to test replication: you will need to re-establish any existing replication configuration. Just start over to be sure of a clean start.

See our current GitHub Milestone for context:

What’s Changed

Test away and report rapidly as we work against the forces of kipple.

3 Likes