Perl::...ersion(3pm)

✨ NAME ✨

okay so this is the manual page for Perl::Critic::Policy::Compatibility::PodMinimumVersion — a section 3pm page from the User Contributed Perl Documentation, no cap 💅 — and its whole job is: check Perl version declared against POD features used.

---

🦋 DESCRIPTION 🦋

bestie, this policy lives inside the Perl::Critic::Pulp add-on. What it does is check that the POD features you're using don't exceed your target Perl version — the one you declared with stuff like use 5.008.

use 5.005;

=pod

C<< something >>    # bad, double angles needs 5.006

see how that C<< something >> is giving 🚩? yeah.

POD doesn't affect how the code actually runs, so this policy is low severity, and it sits under the compatibility theme (see "POLICY THEMES" in Perl::Critic).

For the actual POD version checks that get applied, go look at Pod::MinimumVersion. The ✨ key idea ✨ is, like, if you're targeting Perl 5.005 you avoid things like double-angles C<< >>, because pod2man in 5.005 simply didn't support them. Now, it might be possible to grab newer versions of the POD translators from CPAN, but whether they even run on an older Perl — and whether you want to require that of your users — is a whole other matter, fr fr.

Adding all those use 5.006-type lines to declare a target Perl can be a bit tedious ngl. That's what the config option below is for — it lets you set a base version you use. And as always, if you genuinely don't care about this sort of thing at all, you can disable the policy from your .perlcriticrc in the usual way (see "CONFIGURATION" in Perl::Critic),

[-Compatibility::PodMinimumVersion]

🌸 RequirePodLinksIncludeText Policy 🌸

So the Documentation::RequirePodLinksIncludeText policy asks you to always use the L<target|display> style. That feature is new in Perl 5.005 and it's gonna get reported by PodMinimumVersion unless you've got use 5.005 or higher, or you set above_version down there 👇.

---

💖 CONFIGURATION 💖

• above_version (version string, default none) — only report stuff about Perl versions above this one. The string is anything the version.pm module understands. So, like, if you always use Perl 5.6 or higher, you'd set:

[Compatibility::PodMinimumVersion]
above_version = 5.006

The effect is that all POD features up to and including Perl 5.6 are allowed, and only things above that get reported (and still only those exceeding any use 5.xxx in the file).

---

🔥 SEE ALSO 🔥

• Perl::Critic::Pulp, Pod::MinimumVersion, Perl::Critic
• Perl::Critic::Policy::Documentation::RequirePodLinksIncludeText, Perl::Critic::Policy::Compatibility::PerlMinimumVersionAndWhy, Perl::Critic::Policy::Modules::PerlMinimumVersion

---

🌈 HOME PAGE 🌈

http://user42.tuxfamily.org/perl-critic-pulp/index.html

---

👑 COPYRIGHT 👑

Copyright 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2019, 2021 Kevin Ryde

Perl-Critic-Pulp is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3, or (at your option) any later version.

Perl-Critic-Pulp is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with Perl-Critic-Pulp. If not, see <http://www.gnu.org/licenses/>.

💀 yeah that's the warranty disclaimer bestie, all caps means Business, don't @ me

---

and that's the whole thing 🫶 this beauty shipped with perl v5.40.1 and was dated 2025-10-21 — iconic, we stan, periodt 💅✨