BUG: editing environment variable applies to last "not active" build

since convox v1 editing environment variable was creating new release based on build which is currently promoted , now after migrating to v2 , we observe that editing variable will took latest build as a source, not the promoted one

any ideas? or maybe there is some hidden switch for that?

Kind regards


Hello @mvpl,

I have created an item to investigate this that is currently on our backlog. If this is working as intended for v2 it may be required that we add an option tag for convox env edit to include the specific release.

I will update you when I have any additional information.