feat(ci): use supported Perl versions in CI#82
Conversation
perlpunk
left a comment
perlpunk
left a comment
There was a problem hiding this comment.
Which kind of problems do you see with older versions?
We discussed this in the past.
If the module officially supports perl 5.16, then we should be able to run tests for that version.
We should not only rely on cpantesters.
please see the problems in #81 . Maybe older Perl versions can still be tested with changes to the github action configuration. |
|
Devel::Cover now requires perl 5.20. |
|
I'd say, test all versions starting with perl 5.20, that would be the easiest compromise. |
Motivation: Ensure CI workflows run tests against stable, supported Perl versions. Design Choices: Replace ancient, unsupported Perl versions with 5.20+ releases. Update the setup step to conditionally install CI dependencies only on the latest Perl version to prevent build and test runtime failures. Benefits: Ensures backward compatibility is tested on older supported Perl runtimes while keeping CI setup fast, clean, and reliable. Related issue: openSUSE#82
okurz
force-pushed
the
feature/poo203049_hashed_github_action
branch
from
a639801 to
44d715a
Compare
done. Seems to work |
3 participants
Motivation:
Ensure CI workflows run tests against stable, supported Perl versions.
Design Choices:
Replace EOL Perl versions with 5.36, 5.38, 5.40, and latest. Update the
perltidy workflow to use a perl:5.40 container image.
Benefits:
Prevents installation failures on ancient Perl runtimes and verifies codebase
robustness against modern Perl interpreters.