It will indeed break job restarts, but this will be the case for the other components as well, because with this PR the default execution context name will be overwritten with the bean name (unless the user has explicitly configured the name property).

Is it not acceptable that job executions started with spring-batch 2.2.x runtime cannot be restarted on spring-batch 3.x runtime?