Maintainers can wait for code review but not for publish review?

Review and testing of any code change is the norm these days, however when a release is finished and ready to published, maintainer don't have to review the content of the actual artifacts delivered to users?

What is then the point of performing code review and testing when the actual shipment contents something else than what has been reviewed and tested?

The publish step is the most important in the whole process as that decide the actual content to users.

If Dev don't care what artifacts is published, then why maintain the software in the first place?