using custom_build w/ custom tag + unique helm template data, leads to k8s_yaml orphaned k8s objects

I am doing something like the following

allow_k8s_contexts('mycluster')

gitCommitId = str(local('git describe --match=NeVeRmAtCh --always --abbrev=7 --dirty')).strip()

# generate yaml, all artifacts will have unique name that contains "appid" set below
templated_yaml = local('helm \
    template \
    --namespace my-apps \
    -f .tilt/chartvalues/myappp/stage/values.yaml \
    --set appid=myapp-{} \
    ./.tilt/appdeploy  \
    '.format(gitCommitId))

custom_build(
    ref='myreg.private.com/my/myapp',
    tag=gitCommitId,
    command='./generate-dockerfile-build-tag-only.sh -t {}'.format(gitCommitId),
    deps=['.'],
) 

k8s_yaml(templated_yaml)

If I do a tilt up I get the app deployed OK

If I change something in my local dir, tilt properly builds and deploys the artifacts that are generated. The names of the artifacts change as they now have "appid" in them which is my commit id.

If I do a tilt down, tilt only deletes the most recent set of k8s_yaml it applied.

None of previous sets it applied are cleaned up, the previous sets are orphaned.

Start by tracing the custom_build and k8s_yaml entry points and their resource lifecycle. Reproduce the sequence with tilt up, a local change, and tilt down using uniquely templated Kubernetes object names; done means tilt down removes all previously applied generated objects, not only the newest set.