Who tests the useless survey? Everyone with regression tests. Like dude, everything you talk about has been written “in blood” from years of hosting production systems. If the useless survey is needed, then write a test for it, or a testcase to manually try it. Don’t just upgrade, see that the app is up and push to prod, that’s not testing, that’s asking for trouble.

Okay, let’s be angry at the company and frown a lot at what happened. Gurr, bad company, evil.

And now think of what you’d rather have - a working system, or a reason to be angry? If you have something that integrated with something else, lock it down at a specific version so you control the upgrade and know those versions work 100% of the time together. “Latest” is just asking for trouble - be it in a docker image, in dependencies or elsewhere. It’s absolutely not a “best practice” if it isn’t even a code smell or an outright bug. You could’ve had a slightly outdated version, which won’t be “exploitable” - you wouldn’t have enough time to exploit anything in that time, especially with smaller companies and obscure exploits.

Instead of putting out the fire, you could’ve been now looking into the upgrade, seeing on UAT or Test or whatever that forms aren’t supported, chilling till they are supported or complaining that they aren’t.

Upgrades breaking shit is like programming / devops 101, and a huge reason for technical debt in very old projects. Leaving all that to chance is just irressponsible.

To whoever goes by this comment, downvotes and thinks “yeah it is!” - you are wrong. It’s an endless loop, where a condition to exit it is never met. Recursion is calling on the same function and it slowly getting you the answer. I.e. the task is - ask 15 relatives. To ask the next relative, you first need to ask the one before it. And then you need to ask an even further n+1 relative, till you reach the 15th. So then you meet the condition for the 14th, till you ask person 1 and then you can go for ice cream.

Drill it