I'm scared to publish changes to a Power App my team uses every day

The holiday request app has been live for two months now, and this morning it did its job. Three requests came in overnight, the approvals flow pinged the right managers, and nobody emailed me about any of it. That quiet is the whole reason I built it.

At ten my manager asked for a small change: add a half-day option to the request form. I made the edit in Studio, checked it on my screen, and hit publish before my eleven o'clock. By twelve thirty, two people had messaged me that the submit button does nothing. It turned out my publish also shipped a half-finished experiment from last week, a renamed field the form quietly depended on. I never meant to release that.

I spent lunch with my heart racing, digging through version history for the first time while people waited. I found restore, but the notes said the restored version still needs publishing, and I could not tell whether I was about to make things better or ship something even older over the top. I restored, published, and held my breath. It came back. Then I redid the half-day change, very carefully, and published again at six pm when everyone had gone home.

Nobody shouted at me, but my manager forwarded me one of the complaints with just a question mark. That stung more than shouting would have.

What I want is boring: a way to test a change on a copy before anyone sees it, a publish that ships only what I mean to ship, a note that tells me what each version was, and a rollback I have rehearsed once so it is not a panic button. If changes felt safe, I would actually ship the improvement list instead of sitting on it.