When cloning it is possible to also publish the cloned entity, but there are some situations where it is preferred to force them as published to prevent mistakes.
For example when cloning custom blocks (from block_content), if the published box is not checked, they go into an unpublished state and cannot be published (there is no form element for custom block publish).
As a workaround the form could just be modified with a form_alter.
(There is a core issue that will allow custom blocks to be published: #2834546)
1. Create a custom block, clone it and leave it unpublished
2. Add the block to something like layout builder
3. View as anonymous, block is not visible
Allow configuration of default published status on a per-entity (?) level.
Active
2.0
Code
We ran into the same issue after Drupal core & module update, this will definitely. It would be helpful to solve for even if not at the per-entity level, at least at the root level for someone who wants to keep the legacy behavior of publish by default.