You should always acknowledge and report deadlines that have been missed or (better) that you now know will be missed. This applies whether you are the one who caused the delay or not. You can start by telling the person who has caused it:
I see. I needed that Tuesday as you know. Not getting it until Thursday means the deploy will slip into next week.
(You tell them first because once in a while the person will be able to change things so you can make your deadline after all.)
Then you tell the person who is counting on your to meet your deadline (a boss, project manager, or client)
I will not be getting a needed component on schedule. This means we have to reschedule the deploy.
Again this person may be able to make things happen so that your deadline isn't missed. But if not, at least they know in advance and can adjust plans.
If it is your fault, apologizing is appropriate:
I'm sorry, but Task 34 is taking far longer than I had expected. I can now see that we will need to delay the deploy by at least a few days.
Communication is absolutely vital. Owning up to your mistakes when you make them is absolutely vital. Apologizing as part of every communication is a completely different thing, and one you should avoid. Not just because it might make you look bad, but because it dilutes the real apologies when you have to give them. If you have said sorry every day, it doesn't mean much one more time. If you almost never say sorry, it means a lot when you do.