Policies

Manual

Type::Tiny Stability Policy

Type::Tiny 1.000000+ is considered stable. Any changes to the API that are big enough to require changes to the test suite will be preceded by a six month notice period, with the following exceptions:

• Any changes which are necessary to maintain compatibility with new releases of Moose , Moo , and other software that Type::Tiny needs to integrate with.
• Changes to maintain compatibility with future versions of Perl itself.
• Where a change fixes a contradiction between the implementation and documentation of Type::Tiny.
• Where a feature is explicitly documented as being "experimental" or "unstable".
• Improvements to the text of error messages.

Notice: Planned Changes in Type::Tiny 3

Type::Tiny 3 is expected to be released in the second half of 2026. It is likely to introduce coercions to some common type constraints such as HashRef , ArrayRef , and Str . If your code specifically relies on these types not having coercions, you may need to change your code. (The no_coercions method can give you a copy of any type minus all coercions.)

Experimental and Unstable Type::Tiny Features

The following list is currently non-exhaustive.

• The following type checks result may vary based on your version of Perl and whether Type::Tiny::XS is installed. Their outcome is currently considered undefined, and may change in future versions.
  • Using Object and similar type checks on unblessed regular expression references, the outcome is undefined.
  • On all current versions of Perl, false ( !!0 ) stringifies to the empty string (but using Devel::Peek you can tell the difference between this value and a normal empty string), so Int and subtypes of Int do not consider it to be an integer. If Perl's behaviour ever changes, you might not be able to rely on this outcome. True ( !!1 ) stringifies as "1", so is considered an integer.
  • A glob (not a globref but an actual glob) currently passes the StringLike type constraint but not the Str type constraint.
  • The BoolLike type is intended to extend Bool to cover overloaded boolean objects, but the exact mechanism it uses may change.
• Type::Tiny 's my_methods attribute and the functionality it provides is experimental.
• The parameterizable coercion API is subject to change.
• The interaction of deep coercions and mutable coercions currently results in ill-defined behaviour. This could change at any time.
• Type::Registry 's ability to import MooseX::Types and MouseX::Types type libraries is experimental.
• The signature_for_func and signature_for_method keywords provided by Type::Params may change their behaviour slightly in the future. Once stable, they are expected to be added to Types::Common 's exports.
• The Types::Standard::Dict::combine function.
• These modules are considered part of Type::Tiny's internals, and not covered by the stability policy: Devel::TypeTiny::Perl58Compat , Type::Coercion::FromMoose , Type::Params::Alternatives , Type::Params::Parameter , Type::Params::Signature , Type::Tiny::_HalfOp , Types::Standard::ArrayRef , Types::Standard::CycleTuple , Types::Standard::Dict , Types::Standard::HashRef , Types::Standard::Map , Types::Standard::ScalarRef , Types::Standard::StrMatch , Types::Standard::Tied , and Types::Standard::Tuple .
• The use of some of the modules in the previous list item as exporters of shortcuts for parameterized types is not stable yet.
• Reply::Plugin::TypeTiny is not covered by the stability policy.

Type::Tiny Security Policy

The latest stable release on CPAN is supported for security updates. (By convention, releases with an underscore in their version number are not considered to be stable releases.)

If you are using an older release, you are advised to upgrade.

A list of changes between versions can be found in the Changes file on CPAN with security-related changes tagged "SECURITY" in capital letters.

Reporting a Vulnerability

Please report any issues via GitHub Issues .

If you are concerned that some of the details of your report may lead to an exploit being made public, then keep your issue report vague, and email the details to me directly. My email address can be found on my GitHub profile .

Type::Tiny Versioning Policy

As of 1.000000, this distribution follows a versioning scheme similar to Moo , which is based on a semver -like three component version number, but with the last two components each represented by three decimal digits in the fractional part of the version number. That is, version 1.003002 of the software represents "1.3.2".

Additionally, releases where the second component is an odd number will be considered unstable/trial releases. (These will also include an underscore in the version number as per the usual CPAN convention.)

Perl Version Support

Type::Tiny 0.000_01 to Type::Tiny 0.015_04 required Perl 5.8.1.

Type::Tiny 0.015_05+ and Type::Tiny 1.000000+ requires Perl 5.6.1.

Type::Tiny 2.000000+ will require Perl 5.8.1.

Next Steps

Here's your next step:

• Type::Tiny::Manual::Contributing

  Contributing to Type::Tiny development.