Does APEX require a stop/restart for a database release (19c, cloud, OLTP, single node)?

Our SA is accustomed to stopping APEX whenever the DBAs do a routine (dml, ddl) release. In large part, perhaps, because the SA and the customer are traditionally very risk-averse.

Typically, the release just adds columns and inserts rows. My background is all on-premises, non-APEX, so I don't know enough to persuade the person that a full outage is not necessary. IOW I would schedule the maintenance window, quiesce/restrict the instance, run my scripts, etc. And yes, I would insist on a bounce for metadata changes such as parameters or resources.

So, is there anything about APEX that requires a bounce in this scenario? TIA.