switch on stdlib-piggyback for all migrations by h-vetinari · Pull Request #2372 · regro/cf-scripts (original) (raw)

Should we add to the version migrator too?

That's a great idea, though I'm kinda on the fence about it. One current failure mode for the piggyback is the output-names are templated (e.g. name: {{ name }}), as we then cannot reasonably slice the recipe into sections. This will cause some small amount of failures for the migrators (kinda unavoidable, though I tend to get rid of such fake variables once I touch a feedstock), but I think we should not encumber the version bot with that? 🤔

Or maybe we can loosen the safety net of the piggyback there...?