Odd that that ended up breaking things. It should only delete the gemspec for a default-type gem, and then it should ensure ONLY the version we are shipping for the particular gem is present, not multiple versions. But I suppose this neglects the case of a non-default gem that ends up with multiple versions due to us missing one in puppet-runtime and being pulled in transitively. The non-puppet-runtime-defined version gem would be gone but it's spec file probably remains. But this error was about a missing spec, so 🤷