Closed 6543 closed 5 days ago
Shouldn't this PR go to main
first and the backported to release/v2.8
?
@xoxys well that's exactly what this pull try to solve. in main, the environment syntax already got removed completely! but it was never deprecated before - so this pull does so for the next release those targeting the release branch
Ah ok sorry, got it 👍 I think thats because the plan was to release 3.0 next.
No the plan was to release v2.8.0 as the legacy environment syntax is currently completly valid in the latest release.
And pipeline congig changes must be depricated before a next release is allowed to let it error out.
Those this pull is needed and ned to be released before next release made from main e.g. 3.0.0
Those a 2.8.0 must be released containing a deprication
This pull does tje deprication
Close #4306
also better detection of secrets legacy syntax