Publish nodes permission

Is this still something that core needs to support? We have 2 well maintained modules mentioned here https://www.drupal.org/project/override_node_options → and https://www.drupal.org/project/publishcontent →

Core also provides content moderation for much finer control over publishing workflows and permissions.

IMHO, yes, this is something core should do. Reading the comments, we've got "yes this is a good idea" from all sorts of folks who are either past or current release managers, product managers, etc. It's fairly absurd that we have granular permissions for delete, but not publish/unpublish. Yes, content moderation provides more advanced publishing workflows. But for something so fundamental to a content management system as publish status, I think core needs to solve this.

Just marked 🐛 Users can edit/delete content but not unpublish it Active duplicate with this, which had 35 followers.
I imagine there are other duplicates lurking in the issue queue for this.
This is a very common need. Further evidence core should provide this out of the box.

Thanks!
-Derek

@dww no worries! Lots of these very old issues have those types of comments that have since gone stale so I'm asking the question as of 2025 with all our new tools :)

Ready for a review, happy to change any of the text around the permission (name/description)

Left a suggestion for a title/description update.

But what would the workflow be if you have access to edit a node but can't change the status? Would it just resave the current status?

If you are another contributor eager to jump in, please allow the previous poster(s) at least 48 hours to respond to feedback first, so they have the opportunity to finish what they started!

But what would the workflow be if you have access to edit a node but can't change the status? Would it just resave the current status?

It would be the exact same as it currently is for a user without administer nodes (stays in the same status).

Ready to go now

Won't this need an upgrade path

@smustgrave no because we aren't changing existing functionality, just adding the ability for users to be granted a new permission to change the status.

I see then everything seems to be working as expected.
Tested with the editor role from the standard install.

Think all feedback has been addressed