I'm going through the process of the "Reset Version" function within PAUSE now after correcting the error, testing and creating a new distro (of the same version number). I'm unsure how long this process will take, but I'll record here after it's all done.

I also found the original problem. In most of the test files, I have things like this:

use warnings;
use strict;
 
use lib 't/';
 
use RPiTest qw(check_pin_status);
use RPi::WiringPi;
use RPi::Const qw(:all);
use Test::More;
 
if (! $ENV{RPI_SHIFTREG}){
    plan skip_all => "RPI_SHIFTREG environment variable not set\n";
}
 
if (! $ENV{RPI_MCP3008}){
    plan skip_all => "RPI_MCP3008 environment variable not set\n";
}
 
if (! $ENV{PI_BOARD}){
    $ENV{NO_BOARD} = 1;
    plan skip_all => "Not on a Pi board\n";
}
[download]

That ensures that only my hardware test platform (or any user who has these environment variables set) will have the tests within the specific test file executed.

However, I was testing something briefly with a single test file, and instead of unsetting the env var, I commented out all three "skip_all" lines. After I was done, I forgot to uncomment them.

Because the system I was testing on had those variables set, it would skip over all three if() lines and run the following tests. If I had of ran my tests on a system without those env vars set, I would have hit on the issue prior to release.

Moral of the story... ensure that I test on both my normal test platforms, and a clean system without my test environment variables set... or, test things like this in a proper way, instead of commenting out test file lines arbitrarily.