breaking change in 3.41.15 : merge_message is now a mandatory postional parameter in merge_pull_request function

[metaloid2k21]

After 3.41.15, due to the change introduced in #1437, some of our C/CD automations needed to be adjusted due to the introduction of the merge_message positional parameter.

Is there any version id strategy in place, that could help having a correct dependency management approach in place?

Thank you,
Pedro Almeida

[gonchik]

Hi @metaloid2k21 ,
sorry, missing that message.
I think it's next time we have to thing about positional paratemeters.

if you have some idea or if you needed feel free to send PR or mention to revert back
Cheers,
Gonchik