Hello! We recently switched over from metadata format to source format in our source control (Github), and created new CI/CD pipelines in Azure to handle source format builds and releases. Since we made that change though, I've been finding that every Continuous Deployment release to our sandbox orgs is creating a new version of our flows and processes, even though those flows were not actually changed/updated in the release.

Since we have multiple builds a day being released, flow versions are rapidly proliferating and we have started hitting the "too many flow versions" error on our releases due to hitting 50 versions on certain flows.

Previously, our flows did not have an "API Version for Running", but all of the new versions that are automatically created show an API Version for Running of 49.0. I am not sure why they are getting added as 49.0 instead of our current org API version 51.0. I have read this stackexchange thread on the topic, which suggests that perhaps adding the current API version of the target environment to the flow-meta.xml file would resolve the issue, but I am wondering if there is a different solution that wouldn't require us to always use the latest api version for all of flows.