so, can we merge it?

Thanks for the ping @Marusyk . We're looking into the impact on addins, as this is a breaking change to the public API, to decide if we can merge it now for v3.1.0 or if it has to wait for the next major.

@augustoproiete could you explain why is this a breaking change?

@Marusyk It's a binary breaking change that would only affect existing Cake addins. Addins that were compiled with an existing Cake version are referencing a type called DotNetRestoreSettings that does not have the property PublishReadyToRun and thus technically not the same type.

i.e. CakevNext...DotNetRestoreSettings might not be convertible to Cakev3.0...DotNetRestoreSettings

but this is why we have versions, isn't it? I'm sure that Cake add-ins don't compile on the main branch and always use the latest source.
adding an optional parameter is not a breaking change from API perspective