how do you handle database schema changes? i usually just wing it, but maybe thats a bad idea.

we're starting to hit a point where database schema changes are becoming more frequent and complex, and rolling out changes across multiple services without downtime is proving tricky. are there any patterns or tools you've found particularly effective for managing this, especially in a distributed system? looking for practical advice