Whenever that's happened to me (and it's happened a few times), I just bump the version of the .pm file(s) and upload a new distro (with a matching version number) to PAUSE.
I reckon I've seen plenty of others adopt the same approach, and there's no rule that Foo.pm version 1.11 has to be different from Foo.pm version 1.10, apart from the different $VERSION settings, of course.

ASIDE:
There used to be a recommendation (might still apply - dunno, don't care) that version numbers in pm files be specified like:

our $VERSION = '1.10';
$VERSION = eval $VERSION;
[download]

When you do that, the condition $VERSION eq '1.10' becomes untrue, owing to the terminating '0' :

Owner@DESKTOP-88J497T ~
$ perl -e 'our $VERSION = "1.10"; $VERSION = eval $VERSION; print "WTF
+" if $VERSION ne "1.10";'
WTF
Owner@DESKTOP-88J497T ~
$ perl -e 'our $VERSION = "1.11"; $VERSION = eval $VERSION; print "WTF
+" if $VERSION ne "1.11";'

Owner@DESKTOP-88J497T ~
[download]

Needless to say, I therefore don't do that "eval", but I now also avoid specifying a version number that ends in 0 - just in case.
These days, my module would go (eg) from version "1.09" straight to "1.11".

Cheers,
Rob