repo is currently in a state of being caught up to a number of large changes made in a number of long-running branches, so sort of an odd issue since this hasn't been "officially" merged yet (i think the merge was accidental?), but writing this down as i'm reviewing the changes in #40 (which includes all the changes in the other open PRs)
the pipeline was refactored such that there are two pipelines now, a "legacy" pipeline and a "new" pipeline -
this makes no sense to do since the package is not released - who has built a downstream package that's dependent on a legacy calling pattern? hopefully nobody since nobody is running this yet. Especially pre-release, there is no need to preserve "legacy" codepaths.
rm "legacy" placeholders and just refactor pre-release