Solution: effective means of managing artifacts

Wondering if anyone has found an effective way (e.g. bash script) for managing old pipeline instances on go-server. With a lot of development, we find that active pipelines start to accumulate a large number of versions of artifacts. about to start writing a bash script to manage it, but wondering if anyone has something to start off with as a base.

Our typical Go configuration consists of 1 build pipeline (that builds per commit), and then downstream pipelines for different environments (e.g. DEV, QA, STAGE, PROD). The artifact management script should not delete artifacts from BUILD that have been used in DEV, and can't think off a way to do this without iterating through each pipeline instance of build with lots of API calls.

any ideas on a more effective way of doing this?