diff options
| author | Yves Orton <demerphq@gmail.com> | 2023-01-06 11:05:00 +0100 |
|---|---|---|
| committer | Yves Orton <demerphq@gmail.com> | 2023-01-06 11:05:03 +0100 |
| commit | 244f1aa1d4bdf801191c586ab2810ccf92e4cda3 (patch) | |
| tree | ec31f2a0430df24841396d88e4ace6032d4b285d /dist | |
| parent | d6a7f649855cd40a6e7d9f8397d3cb877a690999 (diff) | |
| download | perl-244f1aa1d4bdf801191c586ab2810ccf92e4cda3.tar.gz | |
dist/threads - bump version
The way CI works it is easy to merge a patch that will lead to
a cmp_version test fail. If two people modify the same file, bump
it to the same new version, then there will be no conflict nor test
fail, until it is merged at which point it will fail because the
code has changed but the version hasn't.
This is a quickie fixup when I got hit by this today with threads.
Diffstat (limited to 'dist')
| -rw-r--r-- | dist/threads/lib/threads.pm | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/dist/threads/lib/threads.pm b/dist/threads/lib/threads.pm index dcae2f03e6..26e00570a0 100644 --- a/dist/threads/lib/threads.pm +++ b/dist/threads/lib/threads.pm @@ -5,7 +5,7 @@ use 5.008; use strict; use warnings; -our $VERSION = '2.33'; # remember to update version in POD! +our $VERSION = '2.34'; # remember to update version in POD! my $XS_VERSION = $VERSION; $VERSION = eval $VERSION; @@ -134,7 +134,7 @@ threads - Perl interpreter-based threads =head1 VERSION -This document describes threads version 2.33 +This document describes threads version 2.34 =head1 WARNING |