This release follows up on release 2.08 and hopefully stabilizes the test suite even further.
At the same time we are taking a first step towards the next major release by deprecating the use of XML configuration files. The preferred format for configuration files is now YAML. The XML support will be removed in a future major release, for now this is just a deprecation notice and several warnings from the test suite.
When we did the last major release to version 2, see the blog post:
We caused some grievances for one of our users, afterwards we discussed that perhaps the distribution should have been renamed to Workflow2 to better reflect the breaking changes and to make a more clear distinction and separation. However, at the time we did not expect this to be a problem since we wanted to keep the distribution name simple and easy to remember. Instead we will try to communicate breaking changes more clearly in future major releases.
But let's see how this pans out as we are slowly approaching the next major release and what we decide on moving forward.
The challenge with Perl and version numbers is complex and now that the mentioned problems got sorted out, I do not believe we would experience them again and I for one want to avoid renaming the distribution in future major releases.
The release is available on CPAN and GitHub:
Change log for Perl Workflow release 2.09.
2.09 2025-11-23 maintenance release, update not required
-
Deprecation notice of use of XML configuration files, issue #125 and deprecation notices implementation by @ehuelsmann via PR #256.
- YAML configuration files are now the preferred format for configuration of Workflow instances. The XML implementation was based on XML::Simple, which itself has been discouraged for use for several years. The distribution still supports XML configuration files, but this support will be removed in a future unscheduled major release.
Improvements to test suite, PR #275 by @ehuelsmann. This is a follow up on release 2.08, since we spotted the issue in the tests running as part of the CI pipeline on GitHub
Top comments (0)