How to deploy config via kubectl kots without fast-fowarding to the latest release?

I had attempted to change an app to include an updated set of resources and tried to deploy it using this command:
kubectl kots set config turbine --config-file /tmp/new-resources.yaml --deploy --merge

The resources got updated according to the new configuration but in addition to that it updated to latest version available of the application unexpectedly.

Is there a way to programatically set new config and deploy that config without jumping app versions? This was on v1.100.3

Thanks for the question, Ryan. It looks like the kots set config command always acts on the latest release, so at the moment, this isn’t possible. set config | Replicated Docs